Bug 1910790 [wpt PR 47378] - bluetooth WPT should not assert precise …

…error messages, a=testonly

Automatic update from web-platform-tests
bluetooth WPT should not assert precise error messages

Technically, they shouldn't be asserting error messages at all, as
those are not specced and therefore can differ between implementations. But that makes it difficult to differentiate between different errors
of the same type. So for now, just assert that the error message
includes() the expected text.

Change-Id: Iec06b30da054c5b8e0adec17b3ad7d439dbc4a32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5750331
Reviewed-by: Reilly Grant <reillygchromium.org>
Auto-Submit: Nate Chapin <japhetchromium.org>
Commit-Queue: Reilly Grant <reillygchromium.org>
Cr-Commit-Position: refs/heads/main{#1335142}

--

wpt-commits: 57f56e0a55513698a2d4f15655ca717e7b1c3680
wpt-pr: 47378

UltraBlame original commit: 61310b2e8e75011c0e4f4d13abc3418a37eef2b4

testing/web-platform/tests/bluetooth/resources/bluetooth-test.js

@@ -748,14 +748,18 @@ expected
 message
 )
 {
-assert_equals
+assert_true
 (
 error
 .
 message
+.
+includes
+(
 expected
 .
 message
+)
 '
 Unexpected
 Error