-
Notifications
You must be signed in to change notification settings - Fork 843
Upcaster testing module #3096
Copy link
Copy link
Open
Labels
Priority 4: WouldLowest priority. Would-be-nice to include issues when time allows it.Lowest priority. Would-be-nice to include issues when time allows it.Status: Under DiscussionUse to signal that the issue in question is being discussed.Use to signal that the issue in question is being discussed.Type: FeatureUse to signal an issue is completely new to the project.Use to signal an issue is completely new to the project.
Milestone
Description
Metadata
Metadata
Assignees
Labels
Priority 4: WouldLowest priority. Would-be-nice to include issues when time allows it.Lowest priority. Would-be-nice to include issues when time allows it.Status: Under DiscussionUse to signal that the issue in question is being discussed.Use to signal that the issue in question is being discussed.Type: FeatureUse to signal an issue is completely new to the project.Use to signal an issue is completely new to the project.
Feature Description
Testing upcaster can be hard, but is made easy with some "boilerplate code."
If all you would have to do is provide the initial format and the desired format, the upcaster can be tested for compatibility.
As the given and expected value are so straightforward, it is easy to provide a testing module for this.
Note that given all the chances underway for Axon Framework 5 around the message conversion process, there is a window of opportunity this issue might become obsolete.
Current Behaviour
There is no upcaster testing module at all.
Wanted Behaviour
An upcaster testing module to simplify, and thus encourage, validation of upcasters.