Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82200

burn_in_tags should include indirectly affected tests

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • 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

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

            Assignee:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: