-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[WIP] [BREAKING CHANGE] Spec: Combine the "Test" and "Suite" concepts
This is to accomodate node-tap and tape, which allow for child tests to be associated directly with other assertion-holding tests (as opposed to having tests only contain assertions, and suites contain only tests and other suites). Ref #126. It also allows for future compatibility with TAP 14, which currently has no concept of test groups or test suites, but is considering the addition of "sub tests". Ref TestAnything/testanything.github.io#36. Also: - Define "Adapter" and "Producer" terms. - Refer mostly to producers and reporters, instead of frameworks, runners, or adapters. - Remove mention that the spec is for reporting information about JavaScript test frameworks, it can report information about any kind of test that can be represented in its structure of JSON messages. Instead, do clarify that the spec defines a JavaScript-based API of producers and reporters. Thought dump: In aggregation, simplify status to failed/passed only, if something has only todo or skipped children, don't propagate this like we did with suites, but cast it down to only failed/passed, as we did with "run" before. This is because, with the "suite" concept gone, we can't assume that test parents only contained other tests, they may have their own assertions. As such, a parent with only two skipped children doesn't mean the parent can therefore be marked as skipped, rather it will be marked as passed, assuming no errors/failures reported. This affects the adapters for QUnit/Mocha/Jasmine, but when frameworks implement this themselves, they can of course have know if an entire suite was known to have been explicitly skipped in which case it can mark that accordingly.
- Loading branch information
Showing
11 changed files
with
488 additions
and
624 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.