Processing of screenshot results on Compose fails because of the issue with Jackson being not able to create a reader to process JSON results.
This is a workaround to parse those results without help of Jackson.
How is it being implemented?
Instead of parsing the the ComposeScreenshotSuite with the help of Jackson, the manual parsing of AST implemented. This also aligns the parsing process with another implementation flow for legacy view system in ScreenshotsSuiteJsonParser, where the manual AST parsing happens.
I also did some refactoring to improve code structure in ScreenshotsComposeSuiteJsonParser.
How can it be tested?
[ ] Use case 1: Added a test case to check mapping of empty screenshots metadata. New empty-compose-screenshots-metadata.json resource was added for that.
[ ] Use case 2: Added a test case to check mapping of screenshots metadata. New compose-metadata.json resource was added for that.
:pushpin: References
:tophat: What is the goal?
Processing of screenshot results on Compose fails because of the issue with Jackson being not able to create a reader to process JSON results. This is a workaround to parse those results without help of Jackson.
How is it being implemented?
Instead of parsing the the
ComposeScreenshotSuite
with the help of Jackson, the manual parsing of AST implemented. This also aligns the parsing process with another implementation flow for legacy view system inScreenshotsSuiteJsonParser
, where the manual AST parsing happens. I also did some refactoring to improve code structure inScreenshotsComposeSuiteJsonParser
.How can it be tested?
empty-compose-screenshots-metadata.json
resource was added for that.compose-metadata.json
resource was added for that.