-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Splitting stress tests #16374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splitting stress tests #16374
Conversation
PR Compliance Guide 🔍Below is a summary of compliance checks for this PR:
Compliance status legend🟢 - Fully Compliant🟡 - Partial Compliant 🔴 - Not Compliant ⚪ - Requires Further Human Verification 🏷️ - Compliance label |
PR Code Suggestions ✨Explore these optional code suggestions:
|
CI Feedback 🧐(Feedback updated until commit a40d7ef)A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
Failures are not related to the PR. The test is failing because it is looking for the nightly build of the Grid. |
User description
This takes apart the Stress test to run them on their basic configuration, with only one browser (Chrome), and avoiding the remote configuration because the class itself starts a Grid on the
BeforeEach
.PR Type
Tests
Description
Split stress tests into separate test suite configuration
Remove stress tests from large-tests and medium-tests suites
Configure stress tests to run only with Chrome browser
Avoid remote configuration conflicts with Grid setup
Diagram Walkthrough
File Walkthrough
BUILD.bazel
Separate stress test suite configuration
java/test/org/openqa/selenium/grid/router/BUILD.bazel
STRESS_TESTS
array containingStressTest.java
stress-tests
test suite with Chrome-only configurationStressTest.java
fromLARGE_TESTS
arraymedium-tests
exclusion list to includeSTRESS_TESTS