[ZohebShaikh]

As we have a 4 core GitHub action run we can utilise it more efficiently by running all our unit test in parallel.

Currently it take the following amount of time to run unit test

• python3.11: 2m vs now 59s
• python3.12: 2m 1s vs now 1m 28s
• python3.13: 1m 44s vs now 1m 12s

It is consistently less in the future it will be a nice addition to run system test in parallel as well. It will require some more work so will do it in another PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.91%. Comparing base (50fd3dd) to head (0600ca3).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1566   +/-   ##
=======================================
  Coverage   95.90%   95.91%           
=======================================
  Files          44       44           
  Lines        3250     3255    +5     
=======================================
+ Hits         3117     3122    +5     
  Misses        133      133           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ZohebShaikh]

I think when tests are running in a different core sometimes it takes longer for the same test to complete which needs this extra timeout.
Might need to look if this can be optimized any further

[tpoliaw]

Tests now take <10s on my machine 🤯. It is slightly quicker to use -n 8 instead of logical as the time to set up the workers starts taking longer than the tests but as a default it makes sense (and is still faster than running single threaded).

in the future it will be a nice addition to run system test in parallel as well

I think that will be difficult as many of the calls to the server can't be run if another task is running or if the state is not known.