To solve this problem, you can try running the modules in parallel with -T %number%. If there are 81 tests in a module and the tests are run in 80 threads, then there will be only one thread per test. Meanwhile, each module will wait for the tests of the previous module to finish. If there are fewer tests in the module than the number of threads, then the number of tests running in parallel will be equal to the number of tests in the module.įor example, if we run tests in 80 threads, then a module with 10 tests will only use 10 threads. That’s why we usually run tests in TeamCity in 80–150 threads, depending on the build type.Īs the number of modules increases, it becomes progressively more difficult to manage the number of threads used to run tests. If we would run them all, then we would have to wait for the results of the tests for over two months. Having a large number of tests made it impossible to run them sequentially. The problem of managing the number of threads
0 Comments
Leave a Reply. |