Will be improving how databases are handled in QuickPotato for that the micro benchmarking core needs to be also reworked.
The idea behind this change is that QuickPotato works within one database using a test case name as an identifier.
Because of this change, QuickPotato can better integrate within a corporate setting and will become more friendly to database vendors like Oracle. This change also entails that the database system behind QuickPotato will become less complicated and relies more on SQLalchemy core than in the previous iteration.
Also, this change will help out in when and how data is stored in the benchmarking database because of this the benchmarking object will become less complicated in regards to saving data.
Summarized this issue will improve the following things:
[x] Reduce complexity around databases
[x] No more multiple databases by default (Can still be determined by the user by overwriting the database connection string.)
[x] Better save mechanisms around test evidence.
[x] Improvements to how it is possible to interact with statistical measurements from the benchmark object.
[x] Overall structural improvements to make room for the above changes.
[x] reworked parts contain a new or better doc string.
Commits will be pushed to this repo when the changes are complete.
Will be improving how databases are handled in QuickPotato for that the micro benchmarking core needs to be also reworked. The idea behind this change is that QuickPotato works within one database using a test case name as an identifier.
Because of this change, QuickPotato can better integrate within a corporate setting and will become more friendly to database vendors like Oracle. This change also entails that the database system behind QuickPotato will become less complicated and relies more on SQLalchemy core than in the previous iteration.
Also, this change will help out in when and how data is stored in the benchmarking database because of this the benchmarking object will become less complicated in regards to saving data.
Summarized this issue will improve the following things:
Commits will be pushed to this repo when the changes are complete.