From eb2eea2e0b2791aa9ca921f12da24a3e6e3ff0e1 Mon Sep 17 00:00:00 2001
From: Chris Hill-Scott <me@quis.cc>
Date: Wed, 18 Oct 2017 11:15:09 +0100
Subject: [PATCH] Use more processors when running tests

Back on my old 2013 Macbook Pro, 2 was the optimum number of cores for the fastest test runs. Which is why I chose `-n2` when I originally introduced this flag (see 9ced677ec7547ae23aea589983aa13c1d50d4fec).

Now I have a faster Macbook (same as every other developer), which has more cores to take advantage of.

We also use 4 cores when running the API tests.

Cores | Time taken to run tests
--- | ---
1 | 28.31s
2 | 18.15s
3 | 14.33s
4 | 12.32s
5 | 12.98s
6 | 13.49s
8 | 15.37s
---
 scripts/run_tests.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/run_tests.sh b/scripts/run_tests.sh
index 0813f2b2e..8aacb2824 100755
--- a/scripts/run_tests.sh
+++ b/scripts/run_tests.sh
@@ -35,5 +35,5 @@ npm test
 display_result $? 2 "Front end code style check"
 
 ## Code coverage
-py.test -n2 --cov=app --cov-report=term-missing tests/ --junitxml=test_results.xml --strict
+py.test -n4 --cov=app --cov-report=term-missing tests/ --junitxml=test_results.xml --strict
 display_result $? 3 "Code coverage"