This file serves to provide directions to repositories which have currently implemented component testing, as well as useful resources so that anyone intending to start using this library will have several references to draw from. These references will be provided roughly in order of usefulness.
In this repository a walkthrough document has been created which details how component testing was added to this repository. This documentation details the process of adding component testing to dp-topic-api and should be very transferrable, although each project will have its own nuances.
This repository also details the mechanism by which component testing is added to the CI pipeline of an application.
In this repository component testing has been implemented for a service using auth, identity and mongo database. This should provide useful example implementation as, like the topic API, the project structure was generated from the same repository generation tool and therefore should have the same kind of structure as any new service.
This project shows how an older service had to be restructured to allow for dependency injection for component testing to be added. This is mostly detailed in this commit
An initial component test has been added to Florence. It would be worthwhile looking into this repository if you are working on any similar UI services.
Godog is the test runner used for the scenarios, and it is worthwhile understanding the basics of how the framework functions.