Correct assertion messages and improve coverage

Following a recent normative change to the Resizable ArrayBuffer proposal [1], the term "out of bounds" no longer applies to "length-tracking" TypedArrays whose underlying ArrayBuffer has been resized to match their byte offset. Reflect this in the tests by renaming the condition from "out of bounds" to "on boundary" and by adding new assertions for true "out of bounds" conditions. [1] tc39/proposal-resizablearraybuffer#70
tc39 · Sep 23, 2021 · e6b6451 · e6b6451
1 parent 1b72bcd
commit e6b6451
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/test/built-ins/TypedArray/prototype/byteLength/BigInt/resizable-array-buffer-auto.js b/test/built-ins/TypedArray/prototype/byteLength/BigInt/resizable-array-buffer-auto.js
@@ -42,5 +42,12 @@ testWithBigIntTypedArrayConstructors(function(TA) {
     expected = 0;
   } catch (_) {}
 
+  assert.sameValue(array.byteLength, expected, "following shrink (on boundary)");
+
+  try {
+    ab.resize(0);
+    expected = 0;
+  } catch (_) {}
+
   assert.sameValue(array.byteLength, expected, "following shrink (out of bounds)");
 });
diff --git a/test/built-ins/TypedArray/prototype/length/BigInt/resizable-array-buffer-auto.js b/test/built-ins/TypedArray/prototype/length/BigInt/resizable-array-buffer-auto.js
@@ -42,5 +42,12 @@ testWithBigIntTypedArrayConstructors(function(TA) {
     expected = 0;
   } catch (_) {}
 
+  assert.sameValue(array.length, expected, "following shrink (on boundary)");
+
+  try {
+    ab.resize(0);
+    expected = 0;
+  } catch (_) {}
+
   assert.sameValue(array.length, expected, "following shrink (out of bounds)");
 });