Extremely simple TODO API implemented using a pseudo Uncle Bob's clean architecture, just to exemplify the difference between an API E2E automated test vs a component test.
This simple app follows two basic principles to achieve a cleaner component testing
- dependency inversion: to allow the core domain to define interfaces that will later be implemented to specific external services such as DB operations or external APIs
- dependency injection: to avoid pass any implementation of the exposed interface defined in the previous point, this will simplify the creation of production and testing apps
- POST
/todos{ title: "todo title" } creates a todo - GET
/todosgets all the todos
- any new node will be created with a
ready: false, updatedAt and createdAtfields - notes starting with
w.wil be saved into an additional external system that is used as an example of an external system that is hard to replace with something like a docker image or another test instance