testfixer opened a new pull request #6435: Make tests more stable by using 
JSONAssert equals
URL: https://github.com/apache/pulsar/pull/6435
 
 
   Similar to the change you already merged for AvroSchemaTest.java(#6247):
   `jsonSchema.getSchemaInfo().getSchema()` in 
`pulsar-client/src/test/java/org/apache/pulsar/client/impl/schema/JSONSchemaTest.java`
 returns a JSON object. `schemaJson` compares with hard-coded JSON String. 
However, the order of entries in `schemaJson` is not guaranteed. Similarly, 
test `testKeyValueSchemaInfoToString` in 
`pulsar-client/src/test/java/org/apache/pulsar/client/impl/schema/KeyValueSchemaInfoTest.java`
 returns a JSON object. `havePrimitiveType` compares with hard-coded JSON 
String, and the order of entries in `havePrimitiveType` is not guaranteed.
   
   
   This PR proposes to use JSONAssert and modify the corresponding JSON test 
assertions so that the test is more stable.
   
   ### Motivation
   
   Using JSONAssert and modifying the corresponding JSON test assertions so 
that the test is more stable.
   
   ### Modifications
   
   Adding `assertJSONEqual` method and replacing `assertEquals` with it in 
tests `testAllowNullSchema`, `testNotAllowNullSchema` and 
`testKeyValueSchemaInfoToString`.
   
   ### Verifying this change
   
   - [x] Make sure that the change passes the CI checks.
   
   *(Please pick either of the following options)*
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   ### Does this pull request potentially affect one of the following parts:
   
   *If `yes` was chosen, please highlight the changes*
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API: (no)
     - The schema: (don't know)
     - The default values of configurations: (no)
     - The wire protocol: (no)
     - The rest endpoints: ( no)
     - The admin cli options: ( no)
     - Anything that affects deployment: (no)
   
   ### Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented)
     - If a feature is not applicable for documentation, explain why?
     - If a feature is not documented yet in this PR, please create a followup 
issue for adding the documentation

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to