Skip to content
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

Load test runner using Nightwatch scripts #3962

Open
reallymello opened this issue Nov 28, 2023 · 1 comment
Open

Load test runner using Nightwatch scripts #3962

reallymello opened this issue Nov 28, 2023 · 1 comment

Comments

@reallymello
Copy link
Contributor

Description

I would love to leverage some of our existing functional Nightwatch testing scripts at load and have the results compiled into a load test report. This is something Artillery.io is doing with modified Playwright scripts as a different way of generating load than creating batches of API requests.

Using a UI script in the performance test would put a more accurate load on the system under test and would allow us to report on actual user experience navigating the system under test. It would save a tremendous time over decomposing the page requests into JMeter or Artillery requests which could also deviate over time with reality as the site changes.

Suggested solution

I feel that Nightwatch has the architecture in order to support this already in that it can run test scripts in parallel. What I propose we add is the ability to

  • Specify which scripts to run
  • How long to continuously run the scripts
  • How many users / threads should run the scripts over that time period
  • Optionally, ability to have phases to ramp up and down user load and run different scripts at different phases
  • Output a performance test report averaging the normal step timings with perhaps the browser metrics from the .getPerformanceMetrics method

Alternatives / Workarounds

Copy and paste existing tests multiple times and run them in parallel with a custom reporter that would provide me average times over the runs of the same tests

Additional Information

No response

Copy link

Thank you for setting this as an enhancement. One of the product folk will triage this again to help see when we can fit this in an upcoming sprint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant