As a dev I want to make sure that the repo is capable of handling a large amount of data,
Test the repository with automated requests. The goal is to validate that the repo is usable, even if there is a huge database underneath. The output of this issue is TRUE/FALSE. This is not a benchmark; we do not want a comparable CPS or any other number as a result.
repeatable, scripted tests
many reads, fewer writes
test directly using the OData REST API. Later (out of scope) add a web API service in the middle.
determine the threshold: how many requests can we serve in a stable way?
As a dev I want to make sure that the repo is capable of handling a large amount of data,
Test the repository with automated requests. The goal is to validate that the repo is usable, even if there is a huge database underneath. The output of this issue is TRUE/FALSE. This is not a benchmark; we do not want a comparable CPS or any other number as a result.