This project includes my solutions to the evil tester's API challenges. The API is used to manage a To-Do list with simple CRUD (Create, Read, Update, Delete), here is the API documentation.
Here is a diagram that I made that visualises the API:
Although the app is runnable locally, I decided to develop my tests against the public cloud instance (https://apichallenges.herokuapp.com/).
- Simply doing the challenges - Initially I went through the challenges as listed. This helped me to learn more about the API, REST methods, different response codes.
- Going beyond the challenges - Now that I finished the challenges, I can think more about how to implement automated checks and other tests beyond the challenges.
| Tool | Description |
|---|---|
 |
Bruno v1.18.1 (API client) MacOS version - To read and write API requests and responses, write simple asserts e.g. check for 200 OK. |
- Test Data Availability - On the cloud instance, the test data clears itself every 10 minutes so this makes my testing less efficient. Luckily, the API supports the save/restore of session data.
See logged issues on the eviltester repo (this is filtered by the issues that I logged).
- I learned to use the Bruno API client - configure variables, headers, auth, simple asserts, inspecting response.