...
- Env(s) must have one set of data to write script against and to test against, preferably using the dataset same data used by the PTF, i.e., UChicago.
- In this environment(s), when modules and DB schemas need to be updated, as well as the Perf dataset needs to be migrated: who will do it? how manually or automatically?
- How to get data for script and where to test their JMeter scripts (existing or new) when there are schema changes?
...
1. Teams may use FOLIO-SNAPSHOT-LOAD to test their script. This environment is rebuilt nightly, so any schema changes will be updated, and the data in this env will be migrated as well. The data is from reference and sample data, so they should have been updated if there were any changes to the schema.
2. Specifically, we are proposing the following for teams to develop and test their script:
- Teams could either grab existing data from the FOLIO-SNAPSHOT-LOAD or create a script to generate their own data and apply them to the FOLIO-SNAPSHOT-LOAD database. If using existing data in this environment, create a script to load them or inform PTF to grab it.
New (New data will be ephemeral, short lived, automatically wiped out. Teams can always have a clean env to play with the next day) - These data generating scripts should be checked into Github and referenced in the JIRA once the script is tested.
- PTF will use these scripts to generate and add this data on top of its big database.
- For any reference data in this env that the JMeter script, when exercised, will touch, PTF would grab the data from its sources and add them on top of PTF's database
...
Adequately addresses the 3 criteria above
Cons: Teams need to write one more script (3 total: JMeter script, restore database state script, and data generating script) to submit to send PTF.