Improving performance testing #8567
andreslucena
started this conversation in
General
Replies: 1 comment 1 reply
-
Considering the nature of the tests that needs to be performed, I am thinking a custom testing folder inside each library, that would load some very specific tests would be useful. This kind of the test suite can be ran against the develop branch, on a scheduled basis (like every night after 19:00 ). https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#schedule Maybe that particular test suite may benefit of : https://github.com/piotrmurach/rspec-benchmark implementation. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm opening this discussion to brainstorm some ideas regarding performance testing.
In the last few weeks we're seeing more PRs related to performance (like #8503 and #8509). Both of these issues have a few things in common: they don't have specs, and they're issues that are only caught when you have a lot of rows in some particulars tables in your database. How could we improve testing in these cases?
In a comment (#8503 (comment)) I left some quick thoughts, but I think this deserves its own discussion with the community and to hear about experiences/ideas/etc.
Beta Was this translation helpful? Give feedback.
All reactions