Do we have anyways to run the same tests multiple times in parallel ? Node and TS binding
We are trying to perform load test on MS Dynamics CRM including client side performance.
And We have only NeoLoad version 8 which don't have real browser protocol.
Traces are really helpful in this case and looking to see if I can trigger same test again parallelly with some options.
Something similar to invocation count in testng
Thanks <#1054804523652231198>
This thread is trying to answer question "The thread does not contain any question to answer."
Also forgot about this - https://github.com/scalewright/scalewright#readme
I haven't had time to try it out yet but plan to
@nagarjunask for load testing with Playwright specifically check this out: https://www.artillery.io/docs/reference/engines/playwright
Related Ask AI answer for "What is the process to run tests in parallel using Playwright?".
Sure, you can run the same tests multiple times in parallel with Playwright. Here's how:
You can set workers: 1
in the config file or use --workers=1
in the command line. This runs tests sequentially, with only one worker active at a time.
// playwright.config.ts
module.exports = {
workers: 1
};
For independent tests in a single file, use test.describe.configure()
. Set mode: 'parallel'
to run all tests in the suite in separate worker processes.
test.describe.configure({ mode: 'parallel' })('my suite', () => {
// Your tests here
});
In playwright.config.ts
, set fullyParallel: true
for all test files or specific projects. Be mindful of inter-dependent tests that need to run serially. Annotate these as "serial". If a serial test fails, all subsequent tests are skipped.
// playwright.config.ts
module.exports = {
projects: [
{
name: 'Project 1',
fullyParallel: true
},
{
name: 'Project 2',
fullyParallel: false
}
]
};
When not using parallelism, Playwright runs test files alphabetically. You can control the order by prefixing filenames with numbers. Alternatively, define tests in helper functions across multiple files. Call these functions in a specific order to control execution. However, this method is discouraged and supported as a best-effort only.
For more details, check out Maximizing Test Efficiency with Parallelism in Playwright.
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].