[Feature]: Add expect().toBeInconclusive() and provide that count along with Pass, Fail

[BlitzkriegSoftware]

🚀 Feature Proposal

Other testing frameworks have an inconclusive() result type which is useful in the scenarios listed in the next section.

Feature Details:

• Add to expect method .toBeInconclusive(reason) (where reason is a string containing why) which should be emitted as part of testing.

  • My .02 is that reason should be a required field e.g. not Falsy or nil
  • This method would only be triggered if expect(expression) evaluates to False e.g., test is not run-able

• In test summaries, include the count of inconclusive along with Pass, Fail

• In theory inconclusive tests would not contribute to code coverage, although, that is an area to consider

Motivation

Inconclusive scenarios:

1. Partially completed tests created as part of TDD (etc.)
2. Unable to meet test preconditions due to hardware/environment issues (test might pass otherwise)

Example

// UC 1:
expect(false).toBeInconclusive('Test not finished');

// UC 2: Test is un-run-able
//    Fetch the number of CPU Cores
const numCores = require('os').cpus().length ?? 0;
//    If evaluation is false, the test is inconclusive
expect(numCores < 2).toBeInconclusive('At least two CPU cores are required');

Pitch

1. It brings jest compatible with other platforms
2. It provides useful functionality for development teams