You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alex Abashev (Jira)" <ji...@apache.org> on 2026/02/16 10:34:00 UTC

[jira] [Updated] (IGNITE-27860) Improvements on IgniteIoCommunicationMessageSerializationTest

     [ https://issues.apache.org/jira/browse/IGNITE-27860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Abashev updated IGNITE-27860:
----------------------------------
    Description: 
The {{IgniteIoCommunicationMessageSerializationTest}} test verifies that fields with specific types are written in a fixed order and read in the same order (only types are stored in the internal collection).

*Current test limitations:*
 # *Fields of the same type ordering* - The test does not catch situations where fields of the same type are in different order during write/read operations. While this may not be critical with generated serializers, it can still cause issues with any remaining manual serialization code.

 # *No byte array validation* - There is no verification of how the object is actually serialized into a byte array, and no NPE checks.

 # *No deserialization correctness* - There is no validation that fields are correctly restored from the byte array and match the originally written values.

 # *No transient field checks* - There is no verification that transient fields are absent from the transmitted message.

*Suggested improvements:*
 * Add round-trip serialization tests with value validation
 * Add checks for proper field ordering (especially for fields of the same type)
 * Add NPE safety checks during serialization/deserialization
 * Add validation that transient fields are not serialized

  was:Use MessageSerializer for CacheContinuousQueryEntry.


> Improvements on IgniteIoCommunicationMessageSerializationTest
> -------------------------------------------------------------
>
>                 Key: IGNITE-27860
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27860
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Alex Abashev
>            Assignee: Alex Abashev
>            Priority: Major
>              Labels: IEP-132, ise
>
> The {{IgniteIoCommunicationMessageSerializationTest}} test verifies that fields with specific types are written in a fixed order and read in the same order (only types are stored in the internal collection).
> *Current test limitations:*
>  # *Fields of the same type ordering* - The test does not catch situations where fields of the same type are in different order during write/read operations. While this may not be critical with generated serializers, it can still cause issues with any remaining manual serialization code.
>  # *No byte array validation* - There is no verification of how the object is actually serialized into a byte array, and no NPE checks.
>  # *No deserialization correctness* - There is no validation that fields are correctly restored from the byte array and match the originally written values.
>  # *No transient field checks* - There is no verification that transient fields are absent from the transmitted message.
> *Suggested improvements:*
>  * Add round-trip serialization tests with value validation
>  * Add checks for proper field ordering (especially for fields of the same type)
>  * Add NPE safety checks during serialization/deserialization
>  * Add validation that transient fields are not serialized



--
This message was sent by Atlassian Jira
(v8.20.10#820010)