This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
Only consider tests to be manual tests as a last resort. #199
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.
@gsnedders @jgraham
This is one very simple idea for #196 - would this be OK to do? This would result in many tests being reclassified from "manual" to "testharness" or "reftest".
Context: Previously for Chromium we had some logic that would look at the test file itself and look for "testharness.js" or "" to guess if the test was a testharness or reftest, and not import it if didn't look like either of those, and then run it as a testharness or ref test regardless of what the manifest says. But, it would be better to rely on what the manifest says, so I want to remove that logic.
This change is