You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When #24613 was addressed via #25257 which was later rolled back and finally reinstated via #25740, we ended up having to disable tests that exercised test filtering features (in TestNG).
We must understand whether that is a problem with the tests or the feature under test in the context of configuration cache.
We later discovered test filtering was not working with configuration cache at all. Result was:
No tests found for given includes: ...
The text was updated successfully, but these errors were encountered:
abstratt
changed the title
Test NG filtering tests not working with configuration cache
Test filtering in TestNG leads to no tests executing when configuration cache enabled
Jul 27, 2023
TestNG supports filtering via <suite>...</suite> [XML markup](https://testng.org/doc/documentation-main.html#testng-xml). To make this CC-compatible, we are now generating and caching the markup at serialization time, so it remains available during execution (as the objects required to build it are not persistable).
Fixes: #25859
TestNG supports filtering via \<suite\>...\</suite\> [XML markup](https://testng.org/doc/documentation-main.html#testng-xml). To make this CC-compatible, we are now generating and caching the markup at serialization time, so it remains available during execution (as the objects required to build it - the markup writer and builder - are not persistable).
Fixes: #25859
Co-authored-by: Rafael Chaves <rchaves@gradle.com>
When #24613 was addressed via #25257 which was later rolled back and finally reinstated via #25740, we ended up having to disable tests that exercised test filtering features (in TestNG).
We must understand whether that is a problem with the tests or the feature under test in the context of configuration cache.We later discovered test filtering was not working with configuration cache at all. Result was:
No tests found for given includes: ...
The text was updated successfully, but these errors were encountered: