You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin then creates a test class BookResponseDocumentation with a static method yielding a list of FieldDescriptors for each field in BookResponse.
If such a class already exists, the plugin verifies if each field in BookResponse is present in BookResponseDocumentation and provides the functionality to update if necessary.
Step 2
Given this BookResponseDocumentation class, the plugin uses its static method in the responseFields() method.
The text was updated successfully, but these errors were encountered:
Context
If a response POJO changes, then all documentation tests using that object have to be updated. This yields a lot of manual work.
Idea
Implement an inspector to check which response POJOs are updated, which tests should thus be updated, and which effectively updates them.
Proposed solution
Step 1
Suppose we have a response POJO, say,
BookResponse
:The plugin then creates a test class
BookResponseDocumentation
with a static method yielding a list of FieldDescriptors for each field inBookResponse
.If such a class already exists, the plugin verifies if each field in
BookResponse
is present inBookResponseDocumentation
and provides the functionality to update if necessary.Step 2
Given this
BookResponseDocumentation
class, the plugin uses its static method in theresponseFields()
method.The text was updated successfully, but these errors were encountered: