Small bug we've come across when writing our tests, please see https://gist.github.com/MatthewSteeples/d47f2ea58f63cdab1e24 for repro code.
Basically we have some "base" test classes which define data contexts and have certain requirements. We don't then want to have to re-define these requirements on the classes that derive from these classes.
Eg in the example above, I would expect TestDerivedClass require both ATS and SQL as a capability
Hi, thanks for sharing this. It looks like the RequiresCapability feature is working correctly in this situation. After testing the code sample you've provided, I can see both capabilities being applied to the test inside the Processing Queue.
However, there is another issue here that is creating some problems and is likely the cause of what you've encountered.
It seems that the engine isn't correctly updating the capability requirements of tests that are already in the processing queue. This means that if you adjust the capabilities for a test that has already been executed, you may need to change its name (and back again) or reset the engine before the execution task is correctly updated with the new capability.