The solution uses tags = ["exclusive"] which prevents concurrent test runs, but there's no way for someone working through to know this option exists. This caused me some confusion while working through the lab. I suspected the tests were running in parallel, but it wasn't immediately obvious to me how to prevent that when calling sh_test. This commit adds a hint pointing towards the tags documentation, which explains how to control test run behaviour.
The solution uses
tags = ["exclusive"]which prevents concurrent test runs, but there's no way for someone working through to know this option exists. This caused me some confusion while working through the lab. I suspected the tests were running in parallel, but it wasn't immediately obvious to me how to prevent that when callingsh_test. This commit adds a hint pointing towards the tags documentation, which explains how to control test run behaviour.