▸case-01 I am writing a Python unit test using pytest for a service that uploads files to AWS S3 using boto3. I want to intercept S3 API calls locally so tests do not hit live AWS infrastructure. What is the recommended fixture or library setup for mocking AWS S3 calls in pytest? | pass→pass | 18,793 | 19,719 | +5% | 1 | 1 | 0% | 2,373 | 3,519 | +48% | 0 | 0 | — |
▸case-02 In my Jest configuration file `jest.config.js`, I want to enforce strict code coverage rules so that any pull request fails if line coverage falls below 80%. What configuration property should I set? | pass→pass | 9,317 | 8,804 | -6% | 1 | 1 | 0% | 791 | 1,016 | +28% | 0 | 0 | — |
▸case-03 I want to evaluate the quality of my test suite by introducing intentional bugs into JS code and verifying that tests fail. What tool and command set up mutation testing for JavaScript/TypeScript projects? | pass→pass | 15,588 | 15,303 | -2% | 1 | 1 | 0% | 1,925 | 2,205 | +15% | 0 | 0 | — |
▸case-04 We are running Pytest in a GitHub Actions workflow with dynamic CPU core allocation. Developers currently hardcode `pytest -n 4` in the CI script, which underutilizes larger runners and crashes smaller ones. What flag tells pytest-xdist to automatically match the worker count to the available CPU cores on the host? | pass→pass | 10,371 | 10,627 | +2% | 1 | 1 | 0% | 901 | 1,187 | +32% | 0 | 0 | — |
▸case-05 In our Pytest suite, certain integration tests modify shared database tables and fail when run concurrently on different workers. Developers want to isolate these specific tests to always execute sequentially on the same worker process while letting the rest of the suite run in parallel. What marker decorator handles this in pytest-xdist? | pass→pass | 10,661 | 11,369 | +7% | 1 | 1 | 0% | 1,083 | 1,492 | +38% | 0 | 0 | — |
▸case-06 When running Pytest across multiple parallel worker processes with pytest-xdist, tests collide because they all attempt to connect to a database named `test_db`. Instead of creating fixed static databases, how should each worker dynamically determine its unique database name inside a pytest fixture? | pass→pass | 15,926 | 20,413 | +28% | 1 | 1 | 0% | 2,178 | 3,435 | +58% | 0 | 0 | — |
▸case-07 Our Jest test suite crashes with Out Of Memory errors on CI containers because Jest defaults to spawning worker threads for every detected CPU core. We want to restrict Jest to use at most 50% of available CPU cores in CI without hardcoding a fixed integer. Which command line flag or configuration option achieves this? | pass→pass | 11,002 | 12,539 | +14% | 1 | 1 | 0% | 1,094 | 1,615 | +48% | 0 | 0 | — |
▸case-08 A developer is encountering race conditions in Jest tests when run in parallel mode. To debug the exact execution order, they want to disable worker pools entirely and run all test files sequentially in the main process. What flag forces Jest to execute sequentially in a single process? | pass→pass | 8,157 | 8,820 | +8% | 1 | 1 | 0% | 528 | 1,035 | +96% | 0 | 0 | — |
▸case-09 In Playwright Test (`playwright.config.ts`), by default tests within a single file run sequentially. We have independent unit-style browser tests inside individual spec files that we want Playwright to run concurrently within each file. Which configuration property enables full parallelism inside test files? | pass→pass | 8,486 | 9,717 | +15% | 1 | 1 | 0% | 674 | 1,154 | +71% | 0 | 0 | — |
▸case-10 When running Playwright tests concurrently across 4 workers, API mock server ports collide if hardcoded to port 8080. How can a Playwright test fixture dynamically compute a distinct port number per parallel worker process? | fail→fail | 18,942 | 19,239 | +2% | 1 | 1 | 0% | 2,738 | 3,058 | +12% | 0 | 0 | — |
▸case-11 Our team uses Cypress in a multi-container CI setup. We want Cypress to automatically balance test spec files across multiple distinct CI machines running simultaneously. What flag must be passed to `cypress run` alongside the record key? | pass→pass | 8,332 | 8,331 | -0% | 1 | 1 | 0% | 564 | 899 | +59% | 0 | 0 | — |
▸case-12 When running `go test ./...`, Go defaults to running test packages in parallel using GOMAXPROCS. We want to explicitly restrict the test runner execution to run at most 2 package/test threads concurrently. Which flag passed to `go test` controls this upper bound? | fail→pass | 10,696 | 9,274 | -13% | 1 | 1 | 0% | 1,070 | 1,134 | +6% | 0 | 0 | — |
▸case-13 In Go, adding `-parallel` to `go test` only runs separate packages in parallel unless individual unit test functions explicitly opt in to parallel execution within the same package. What method call inside a Go test function signals to the runner that the test can be run concurrently? | pass→pass | 8,039 | 9,766 | +21% | 1 | 1 | 0% | 577 | 1,191 | +106% | 0 | 0 | — |
▸case-14 Standard `cargo test` runs unit tests as threads in a single process, causing issues with global state and environment variable mutations. What drop-in test runner alternative for Rust executes each test in its own dedicated process for enhanced parallel isolation? | pass→pass | 12,801 | 13,317 | +4% | 1 | 1 | 0% | 1,378 | 1,770 | +28% | 0 | 0 | — |
▸case-15 We have a large Pytest suite where tests within the same module rely on shared class-level setup fixtures. Running with `--dist=load` causes worker switching midway through a module, re-running expensive setup. Which pytest-xdist distribution mode guarantees that all tests in a single class or module run on the same worker? | pass→pass | 9,364 | 15,054 | +61% | 1 | 1 | 0% | 1,836 | 2,274 | +24% | 0 | 0 | — |
▸case-16 We want to split our Jest test execution across 4 matrix jobs in GitHub Actions without installing custom third-party splitters. What native CLI flag allows Jest to execute only the 2nd partition of a 4-part split suite? | pass→pass | 4,282 | 9,254 | +116% | 1 | 1 | 0% | 725 | 1,061 | +46% | 0 | 0 | — |
▸case-17 In pytest-xdist, we want to ensure all test functions residing in the same file are grouped together and dispatched to a single worker process. Which `--dist` option explicitly enforces file-level grouping? | pass→pass | 4,990 | 9,011 | +81% | 1 | 1 | 0% | 870 | 988 | +14% | 0 | 0 | — |
▸case-18 In `vitest.config.ts`, heavy native C++ modules crash when executed inside Node worker threads due to shared memory conflicts. How do we configure Vitest parallel execution to use child processes (forks) instead of worker threads? | pass→pass | 14,189 | 12,937 | -9% | 1 | 1 | 0% | 1,659 | 1,518 | -8% | 0 | 0 | — |
▸case-19 We have 1000 Playwright end-to-end tests and want to distribute execution across 5 separate CI machines. What command line flag tells Playwright runner process 1 to execute only its assigned 1/5th share of spec files? | pass→pass | 7,986 | 3,671 | -54% | 1 | 1 | 0% | 546 | 973 | +78% | 0 | 0 | — |
▸case-20 During local development, a developer wants pytest-xdist to continuously run tests in subprocesses, pause when tests pass, and re-run only the failing tests whenever a file is saved. What command line option enables this continuous loop mode? | pass→pass | 9,835 | 4,759 | -52% | 1 | 1 | 0% | 871 | 1,121 | +29% | 0 | 0 | — |
▸case-21 When running parallel test workers against PostgreSQL, running migrations from scratch for each worker's database is slow. What PostgreSQL database creation syntax allows a worker test setup script to instantly clone a pre-migrated schema database? | pass→pass | 8,246 | 14,807 | +80% | 1 | 1 | 0% | 1,438 | 1,839 | +28% | 0 | 0 | — |
▸case-22 In a Pytest suite where some test files complete in milliseconds and others take minutes, standard `--dist=load` distribution leaves worker processes idle waiting for long files. Which pytest-xdist scheduling mode dynamically redistributes pending unexecuted tests from busy workers to idle workers? | fail→pass | 28,583 | 15,460 | -46% | 1 | 1 | 0% | 4,989 | 2,247 | -55% | 0 | 0 | — |