test: check for AbortController existence

Running tests comparitively on older versions of Node.js that do not have AbortController can be a pain. Only add the AbortController to knownGlobals if it actually exists. Signed-off-by: James M Snell <[email protected]> PR-URL: #35616 Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Rich Trott <[email protected]>
nodejs · Oct 15, 2020 · 6751b6d · 6751b6d
1 parent f59d4e0
commit 6751b6d
Showing 1 changed file with 9 additions and 1 deletion.
diff --git a/test/common/index.js b/test/common/index.js
@@ -253,7 +253,6 @@ function platformTimeout(ms) {
 }
 
 let knownGlobals = [
-  AbortController,
   clearImmediate,
   clearInterval,
   clearTimeout,
@@ -264,6 +263,15 @@ let knownGlobals = [
   queueMicrotask,
 ];
 
+// TODO(@jasnell): This check can be temporary. AbortController is
+// not currently supported in either Node.js 12 or 10, making it
+// difficult to run tests comparitively on those versions. Once
+// all supported versions have AbortController as a global, this
+// check can be removed and AbortController can be added to the
+// knownGlobals list above.
+if (global.AbortController)
+  knownGlobals.push(global.AbortController);
+
 if (global.gc) {
   knownGlobals.push(global.gc);
 }