-
Notifications
You must be signed in to change notification settings - Fork 217
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
MGMT-19258: Split KubeAPI and non KubeAPI subsystem tests
We are dealing with an issue where some tests have not been executed since they were created, this is because they lack the [kube-api] tag in the test name. It's not ideal to need to specify this tag in each test as it is easily missed and the consequences of this are not good. I have decided to solve this by placing the KubeAPI and non KubeAPI tests into different packages `github.com/openshift/assisted-service/subsystem` for non KubeAPI tests 'github.com/openshift/assisted-service/subsystem/kubeapi' for KubeAPI tests Now every test within the respective package will be executed, irrespective of how it has been tagged. In order to get to this point, some refactoring of common code between tests was required. The common code has been placed in a package called `utils_test` Some of the existing utils code has been moved here also in order to support sharing of this code. This is quite a big change in terms of volume, but the principles are simple. functions, consts and vars between tests have been moved to the new namespace and exported. References to `package private` members that have been moved to the new namespace have been updated to point to the correct place. Some tests were found to be failing after they started to run, not unexpected. As these are non trivial to fix and somewhat unrelated to this fix for how we run the tests, these tests have been disabled by marking them with `PDescribe` for now. These tests will be dealt with in MGMT-19596
- Loading branch information
1 parent
6cdfd59
commit 49cde10
Showing
30 changed files
with
3,259 additions
and
2,941 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.