1925462 - Make gtests run per-directory/manifest/identifier

Status: NEW

(Testing :: General, defect, P2)

Description

[:Gijs (he/him)]

Individual gtests tend not to expect each other, especially not in entirely different directories / modules.

It would be nice if there was less interference between them.

Comment 1

[Dave Townsend [:mossop]]

Some justification here is from bug 1920674 comment 4 where a gtest failed in CI because a previous gtest had enabled color management in our graphics system.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jmaher, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

I am not sure how to do this, it seems we would need to support some kind of tag system or manifest system and then get the gtest harness to work with that. I have never worked on gtest, just inherited the component- so my experience with the toolchain is zero.

it appears that we run firefox -unittest with certain envvars set and it seems to discover and run all the tests.

theoretically we could make a manifest with all the tests and have python parse it and then figure out how to send a specific test file to firefox, i.e. firefox -unittest MyTestName, then Firefox would restart between each test file giving some level of separation. I am not sure how to do that, but if someone was familiar with the gtest framework, that would help.

Comment 4

[Dave Townsend [:mossop]]

I think it would be something like..

1. Call mach gtest --list-tests and parse out the list of tests.
2. Chunk based on the first part of the test name (tests are named Foo.Bar).
3. Call mach gtest Foo.* to run each chunk.