Open
Bug 1513584
Opened 5 years ago
Updated 2 years ago
jstests.py should not do anything with wpt tests if specific non-wpt tests are requested
Categories
(Testing :: web-platform-tests, enhancement)
Testing
web-platform-tests
Tracking
(Not tracked)
NEW
People
(Reporter: sfink, Unassigned)
Details
My usual invocation is ./jstests.py $JS non262, but now that seems to be loading in all of the wpt tests in addition to things under the non262/ directory. I would probably prefer something like having a virtual wpt "directory", so I could do eg ./jstests.py $JS non262 wpt and have them both run. (I'm fine with running everything, including wpt, by default.) Also, it's not just about which tests to run or not run; I would prefer not to wait the added time for all of the manifests to be parsed or whatever it's doing. (Describing my feature request in a somewhat more principled way: the first component of test path fragments given on the command line are test collections. All directories are test collections, as is wpt. And I wouldn't mind if *not* all directories were automatically test collections, eg lib/.)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•