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

Consider adding a tag to disable an individual JavaScript test

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Tooling & Methods

      Thanks to the new BF process that is currently in pilot, there may be some increased need in the near future to be able to easily disable tests. Currently there are some idiomatic ways to exit early, e.g.

      const disabled = true;
      if (disabled) {
          return;
      }

      But these don't work uniformly for all suites. Some require more involved changes (e.g. FSM). In all such cases, the test still "runs", it just doesn't do anything.

      It would be nice to have a simple and uniform way across suites to quickly disable a test until a fix can be made. A proposed solution would be something like a `test_disabled` tag.

            Assignee:
            backlog-server-stm Backlog - Server Tooling and Methods (STM) (Inactive)
            Reporter:
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: