Is your feature request related to a problem? Please describe.
Right now there are some things that make tests really slow to run
Having WinPIXEventRuntime loaded
Shaders that have many strings
Taking a PIX capture
None of these things are needed if the test succeeds, so why pay for them?
Describe the solution you'd like
I think there should be an option, which is the default that does the following:
doesn't load win pix
compiles out strings
doesn't take a pix capture
If a test does fail, then we should run it again with all of the above options reenabled. It will mean that failing tests will take slightly longer but it will mean that passing tests will be significantly faster.
Additional context
The SectionHierarchy - ByteWriter tests go from taking 50 seconds to 4 seconds when strings are compiled out. That is a huge saving. It also means that if this test were to fail with these proposed changes, it will take 54 seconds to run if it fails rather than 50 which ain't much. But will save 46 seconds on every passing run
KStocky
commented
1 month ago
Is your feature request related to a problem? Please describe.
Right now there are some things that make tests really slow to run
None of these things are needed if the test succeeds, so why pay for them?
Describe the solution you'd like
I think there should be an option, which is the default that does the following:
If a test does fail, then we should run it again with all of the above options reenabled. It will mean that failing tests will take slightly longer but it will mean that passing tests will be significantly faster.
Additional context The SectionHierarchy - ByteWriter tests go from taking 50 seconds to 4 seconds when strings are compiled out. That is a huge saving. It also means that if this test were to fail with these proposed changes, it will take 54 seconds to run if it fails rather than 50 which ain't much. But will save 46 seconds on every passing run