burn_in_tags should include indirectly affected tests

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Correctness
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

        1. from_jstest_files_to_their_dependants_map.json
          1.81 MB
        2. generated-burn-in-config-653f6f0e0ae606a657a5dffa.tgz
          678 kB

              Assignee:
              Mikhail Shchatko
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: