We currently have in WPT:
./dom/observable/tentative/crashtests/observable-gc.any.js
./dom/observable/tentative/crashtests/observable-takeUntil-toArray.any.js
./fetch/api/crashtests/huge-fetch.any.js
./IndexedDB/crashtests/create-index.any.js
./permissions/crashtests/permissions-query-worker.window.js
./permissions/crashtests/permissions-query.any.js
./streams/readable-byte-streams/crashtests/tee-locked-stream.any.js
./streams/readable-streams/crashtests/garbage-collection.any.js
./streams/writable-streams/crashtests/garbage-collection.any.js
./WebCryptoAPI/import_export/crashtests/importKey-unsettled-promise.https.any.js
These are all picked up as testharness tests, because of self.markup_type being None in:
|
@property |
|
def name_is_crashtest(self) -> bool: |
|
return (self.markup_type is not None and |
|
(self.type_flag == "crash" or "crashtests" in self.dir_path.split(os.path.sep))) |
This is in clear contrast to any testharness-in-HTML file, where the self.markup_type would be "html".
The *.window.js case seems simple: it should be the same as any "normal" testharness case.
The *.any.js one is maybe more complex, if we want the crash tests to run across all the different globals.
We currently have in WPT:
These are all picked up as testharness tests, because of
self.markup_typebeingNonein:wpt/tools/manifest/sourcefile.py
Lines 420 to 423 in 72b780f
This is in clear contrast to any testharness-in-HTML file, where the
self.markup_typewould be "html".The
*.window.jscase seems simple: it should be the same as any "normal" testharness case.The
*.any.jsone is maybe more complex, if we want the crash tests to run across all the different globals.