Motivation
We added #54 in order to be able to set concurrency however we don't perform any tests to ensure that this concurrency option is saved (similar to how we do it for the authentication tests) or how it performs when different levels of concurrency are set. We should try with concurrency levels of 1,8 and maybe others to see if there are areas where it can fail. (I guess 0 as well? defensive coding for this semaphore?)
Motivation
We added #54 in order to be able to set concurrency however we don't perform any tests to ensure that this concurrency option is saved (similar to how we do it for the authentication tests) or how it performs when different levels of concurrency are set. We should try with concurrency levels of 1,8 and maybe others to see if there are areas where it can fail. (I guess 0 as well? defensive coding for this semaphore?)