[issue_tracker] Add stress testing tool#10880
Conversation
|
Thanks for trying this! Can you also try performing the stress test on the frontend ui for both regular and batch edit to see if it works still ? |
regisoc
left a comment
There was a problem hiding this comment.
Thanks for this PR! Nice work.
I am not able to test the test plan fully as I have some issues with my VM, but at high numbers of issues/comments, it correlates with errors we have in HBCD. I will try to have my VM in shape for a more thorough pass.
For now, my comments included below.
Minors blocks to change, the global logic makes sense:
- dry-run/confirm: pick one. It will be easier to understand and remove some checks.
- extract both main feature (insert issue and clean issues) into clear functions.
- Do we need to keep track of the attachments?
Tested with 1,000 issues and 1,998 comments. Browse Issues and issue details worked correctly. Batch Edit still failed after all generated data was removed, including with the normal raisinbread issues, so that appears to be a pre-existing issue. |
Brief summary of changes
Testing instructions
dev.sandboxis enabled in the local LORIS configuration.php tools/issue_tracker_stress_test.php --issues=1000 --comments=0,1,5 --run-id=stress-1--confirm.http://localhost:8080/issue_tracker/.stress-1and confirm the generated issues load.php tools/issue_tracker_stress_test.php --cleanup=stress-1 --confirmnpm run lint:php.Link(s) to related issue(s)