Closed
Conversation
Collaborator
Author
|
It seems to me that after adding the TODO support on testem todo is correctly reported for the browser launchers, but not for the process launcher with TAP reporter |
Owner
|
Fixed in #253978fbcfea23f202521ab82c1205ca7c488967 by only running browser smoke test with testem. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This branch demonstrates issues with testem todo reporting.
npm exec qunita. ❌ Does not run Firefox
b. ✅ Reports correctly 1 todo and 1 fail
testem cia. ✅ Reports correctly 1 todo and 1 fail from the Firefox launcher
b. ❌ Reports incorrectly 2 fails from the
qunitlaunchertestem ciwithprotocol: "process"intestem.json:a. ✅ Reports correctly 1 todo and 1 fail from the Firefox launcher
b.
qunitlauncher. Logs are not readable