You are a QA engineer of the team that develops an application for processing user-generated content that transforms it into JSON-based documents. Later, these documents are processed by a frontend application.
The frontend application expects the data that is well-formed and contains no invalid properties, and one of the ways to achieve that is to run few automated tests on the output.
In this task, you'll have to implement few tests for JSON output that describes rich text.
The pre-generated output is located in jsons-safe and jsons-unsafe directories. The former is meant to contain output that contains no errors (at least our tests say so). On the contrary, the latter reeks of all kinds of errors might occur.
You will find components specifications in COMPONENTS.MD.
In the org.example.internship.data package, you will find classes that you will work with.
All components classes are not much different from the base class, but provide easier access to the component-specific properties. In case you'd like to generate your own component instances for testing purposes, there is a very simple DSL that you can use.
ComponentsReader.kt provides read access to the JSONs in both folders. These data are later used in tests.
In Tests.kt, there are two parameterized tests: test safe components and test unsafe components. You can use the 'safe' test to check whether your checks work well for the output that we have already reviewed.
Values for the parameterized tests are provided from two classes: SafeComponents and UnsafeComponents. Please do not modify them, but implement your solution in the ComponentTestsProvider class, so that it's applied in both cases.
The components field of ComponentTestsProvider contains a list of components to test.
To provide output, create a TestResult object for each of the tests that you perform on the components. Essentially, we expect that your tests take components as input and provide TestResult objects as output.
In the performTests method, please, implement the logic to verify that provided components conform to the specification. We expect that the task can be solved only by injecting your code to this method. However, if you feel like there is a more elegant solution, you are free to implement it however you like.
Please keep in mind that the specs might change over time, as well as other components appear, so we would appreciate a solution that is future-proof.