- Read-only: It only gets data, and does not allow us to change data. Makes it simpler!
- Time-constrained on API level: You can tell dates as input and it does freeze time for test automation purposes. You don't have to play with concepts of today() and now().
- Limited and understandable UI level edits to data: There are some things we can change from GUI that impact the API but they are fairly straightforward.
- Capturing and reviewing for correctness for the combination that we previously documented as receiving the 500 response for that bug
- Ensuring we could see latest data after the most recent changes
- Having easily configurable control over dates and times we had not needed in our tests before
- Making some of the tests approval files smaller in size as long as they did not lose the idea of what we were testing with them
Great chance of pairing on API #ExploratoryTesting with my trainee as there was a major change on the logic behind the API. Got to experience the ideas of tests we throw away, tests we want to keep for later but for reasons other than we start with, and relying on past tests.— Maaret Pyhäjärvi (@maaretp) July 21, 2020