Contents Now Platform App Engine Previous Topic Next Topic Parallel testing Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Parallel testing Reduce testing time by running multiple tests and test suites in parallel. Design tests to run in parallel by avoiding resource conflicts and data dependencies. Parallel testing limit Parallel testing enables users to run multiple automated tests simultaneously. This process continues until the number of currently running tests consume up to half of the available system resources of an instance. The actual number of parallel tests that a non-production instance can support depends on the system resources that the instance has when it is provisioned. The parallel testing limit ensures that an instance always has system resources available for other non-testing tasks. Test waiting queue When the system reaches the parallel testing limit, it reschedules tests to run later by placing them in a test waiting queue. Each test in the waiting queue has a schedule the next time the test runs. Design considerationsRun multiple tests and test suites in parallel to reduce testing time. Avoid resource conflicts and data dependencies by designing parallel running tests. Prevent resource conflicts between parallel tests Prevent resource conflicts by running tests that create their own data. Tests that run with existing data prevent other tests that need the same data from running in parallel.Note: If you have two or more tests with resource conflicts, see Mark tests as mutually exclusive to create a mutual exclusion rule that prevents the tests from running in parallel. On this page Send Feedback Previous Topic Next Topic
Parallel testing Reduce testing time by running multiple tests and test suites in parallel. Design tests to run in parallel by avoiding resource conflicts and data dependencies. Parallel testing limit Parallel testing enables users to run multiple automated tests simultaneously. This process continues until the number of currently running tests consume up to half of the available system resources of an instance. The actual number of parallel tests that a non-production instance can support depends on the system resources that the instance has when it is provisioned. The parallel testing limit ensures that an instance always has system resources available for other non-testing tasks. Test waiting queue When the system reaches the parallel testing limit, it reschedules tests to run later by placing them in a test waiting queue. Each test in the waiting queue has a schedule the next time the test runs. Design considerationsRun multiple tests and test suites in parallel to reduce testing time. Avoid resource conflicts and data dependencies by designing parallel running tests. Prevent resource conflicts between parallel tests Prevent resource conflicts by running tests that create their own data. Tests that run with existing data prevent other tests that need the same data from running in parallel.Note: If you have two or more tests with resource conflicts, see Mark tests as mutually exclusive to create a mutual exclusion rule that prevents the tests from running in parallel.
Parallel testing Reduce testing time by running multiple tests and test suites in parallel. Design tests to run in parallel by avoiding resource conflicts and data dependencies. Parallel testing limit Parallel testing enables users to run multiple automated tests simultaneously. This process continues until the number of currently running tests consume up to half of the available system resources of an instance. The actual number of parallel tests that a non-production instance can support depends on the system resources that the instance has when it is provisioned. The parallel testing limit ensures that an instance always has system resources available for other non-testing tasks. Test waiting queue When the system reaches the parallel testing limit, it reschedules tests to run later by placing them in a test waiting queue. Each test in the waiting queue has a schedule the next time the test runs. Design considerationsRun multiple tests and test suites in parallel to reduce testing time. Avoid resource conflicts and data dependencies by designing parallel running tests. Prevent resource conflicts between parallel tests Prevent resource conflicts by running tests that create their own data. Tests that run with existing data prevent other tests that need the same data from running in parallel.Note: If you have two or more tests with resource conflicts, see Mark tests as mutually exclusive to create a mutual exclusion rule that prevents the tests from running in parallel.
