Details of upload 0c08ba20-ec94-4f25-b1a5-a254412f2485

Created at
2026-03-06T14:19:29.860Z
Total number of tests
1127
JUnit report XML
View report
GitHub repository
ably/ably-js
Commit SHA
a2b8b23
Pull request base ref
integration/protocol-v6
Pull request head ref
PUB-1197/liveobjects-rest-api
Branch / tag name
2109/merge
Workflow asset retention period
90 days
GitHub action
__ably_test-observability-action
GitHub run ID
22766594271
GitHub run attempt
1
GitHub run number
4052
GitHub job
test-node
GitHub job URL
Not known
Loop iteration
1

Test failures

There are 8 failures in this upload.

Failure ID Test case ID Test class Test case Message
bcf74ef3-b1fb-4cf1-8296-23850ff3072e 5b7a69d0-a7b9-426b-b0b9-42f0d49d59e7 should handle complex object operations workflow with binary protocol rest/objects Rest with Objects plugin should handle complex object operations workflow with binary protocol expected { complexMap: { …(5) }, …(1) } to have deep property 'counter' of 11, but got { Object (objectId) }
60725059-709a-4d01-859f-19fa2bb29208 f78fc8dd-b679-4f7c-a551-aaa6a0734863 should handle complex object operations workflow with text protocol rest/objects Rest with Objects plugin should handle complex object operations workflow with text protocol expected { …(2) } to have deep property 'counter' of 11, but got { Object (objectId) }
148b6702-5f88-44c4-b26b-5343646de1ee f3eaa472-3a97-4301-9bdd-4d8808446097 should handle different data types for expanded objects with binary protocol rest/objects Rest with Objects plugin RestObject.get() should handle different data types for expanded objects with binary protocol Check data for key "emptyBytesKey" is retrieved correctly in expanded object: expected false to be true
63b18d50-330c-4e36-bf05-d8748cbf1c31 eb789cb3-f4d1-4484-b9ec-d193bcddc895 should handle different data types for expanded objects with text protocol rest/objects Rest with Objects plugin RestObject.get() should handle different data types for expanded objects with text protocol Check data for key "emptyBytesKey" is retrieved correctly in expanded object: expected false to be true
aa60d471-19cb-4f92-ad9d-0dd207e306cb 83b908cb-ceac-4948-b89b-89a247797f56 should handle different data types in MAP_SET operation with binary protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_SET operation with binary protocol Check data was set for a key "emptyBytesKey" via MAP_SET: expected false to be true
e3424b6d-5da2-4e49-bac7-f572abb68d3a 9ee9655a-6289-4930-bc3f-54f3f7dccab1 should handle different data types in MAP_SET operation with text protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_SET operation with text protocol Check data was set for a key "emptyBytesKey" via MAP_SET: expected false to be true
38a5c89b-78cc-46fe-960a-43fe89a6d649 c3be6a68-d463-42b0-996f-4ebac3c7070c should handle different data types in MAP_CREATE operation with binary protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_CREATE operation with binary protocol Check data was set for a key "emptyBytesKey" via MAP_CREATE: expected false to be true
d32cdacd-fa7d-4d38-bcf5-5bc26fd6a8c5 ffb6248b-036e-4ed3-b44d-cd2e5ed871cc should handle different data types in MAP_CREATE operation with text protocol rest/objects Rest with Objects plugin RestObject.publish() should handle different data types in MAP_CREATE operation with text protocol Check data was set for a key "emptyBytesKey" via MAP_CREATE: expected false to be true