-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Correctness
-
Fully Compatible
Currently, burn_in_tags only run js tests that have been explicitly modified in the patch.
On the other hand, if the patch affects a base FSM test, brun_in_tags will only run that base FSM and will not test all the FSM test derived from that one.
We have a similar issue also with js library modifications, in fact when a patch impacts a js test library, burn_in_tags will not execute any tests that use/include that library.
To improve js dependency discovery, we could potentially use the ES modules introduced in PM-3399
- related to
-
SERVER-85790 Innocuous change in jstests/libs/optimizer_utils.js causes consistent system failures
- Closed
-
SERVER-85858 Revert burn_in_test's inclusion of transitively-affected tests
- Closed