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

smoke.py could use some work

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.1.3
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • Quint Iteration 3.1.2, Quint Iteration 3

      Split out the passthrough tests into separate suites. This allows the generated report.json file to record the success/failure of each individual test.

      Support parallel execution of C++ unit tests, dbtests, and jstests: (--jobs=N)

      1. C++ unit tests will "just work"
      2. dbtests require separate dbpaths
      3. jstests should dispatch to independent MongoDB deployments

      Support grouping different kinds of tests (e.g. C++ unit tests, dbtests, and jstests) so that they can be run together. This allows for customizability in specifying what tests to execute when changes are made to a particular part of the code.

      Support including and excluding jstests from suites by using tags. For example, a "no-sharding" tag that appears in the file would prevent it from being run as a part of the sharding jsCore passthrough.

      /**
 * This test should not be run in sharding because <reason>.
 *   @tags: [ no-sharding,  # SERVER-XXX
 *          ]
 */

      Support running a set of tests multiple times, or until some test fails. (--repeat=N)
      Support randomizing the order in which tests execute. (--shuffle)

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            richard.kreuter Richard Kreuter (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: