TEST_RUN takes in a regular expression. After the recent refactoring, this no longer works. This is because we create a kind cluster with a name based off of the TEST_RUN. If there any special characters (e.g. from regular expressions), this fails.
If we add a new text that's a prefix or suffix of the same test, that test will be ran twice on GitHub. For example, if we have TestA and TestAVariant, then when GitHub runs TestA, it will run both tests within that runner and then it will run TestAVariant again in a separate runner. This is because Go takes in a regular expression when filtering tests and TestA matches both tests. We fix this by adding symbols for start and end of string, e.g. we run TestA with ^TestA$ to ensure it only runs TestA.
This fixes two issues:
TEST_RUN
takes in a regular expression. After the recent refactoring, this no longer works. This is because we create a kind cluster with a name based off of the TEST_RUN. If there any special characters (e.g. from regular expressions), this fails.TestA
andTestAVariant
, then when GitHub runsTestA
, it will run both tests within that runner and then it will runTestAVariant
again in a separate runner. This is because Go takes in a regular expression when filtering tests andTestA
matches both tests. We fix this by adding symbols for start and end of string, e.g. we runTestA
with^TestA$
to ensure it only runsTestA
.