There are 9 failures in this upload.
| Failure ID | Test case ID | Test class | Test case | Message |
|---|---|---|---|---|
| 479fd0de-b1c0-4f3d-8284-8827335d29eb | 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) } |
| 0177e03e-f9f6-4536-84bf-b3f0cb4bac05 | 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 'complexMap' of { name: 'Test Map', version: 1, …(3) }, but got { active: true, …(4) } |
| 0ff578ff-3019-4f96-ba98-6e195b3d00d7 | 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 |
| a09b5b54-1c7a-4cf2-9259-20199ed9a4f7 | 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 |
| 1e25a1f9-614a-43b3-931d-473f3486243c | 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 |
| 3ab8a3c0-b096-4f40-936c-7d6975d0d1e0 | 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 |
| 7581b57a-6da7-4b55-a651-adce4246f9f4 | 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 |
| 82e7c51d-fb6d-45b1-8b4c-d97abc4ac18c | 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 |
| b430b7fb-a02b-43ac-8597-1d1b8ddccf26 | b01f1ca4-d9f1-4d24-a0f6-2c4ee86c19fa | Should retrieve a message by serial | rest/message-operations Should retrieve a message by serial | Message not found |