-
Sub-task
-
Resolution: Done
-
Critical
-
4.4.1.AM3
-
devex #123 November 2016, devex #128 February 2017, devex #130 April 2017, devex #139 October 2017
-
16
There are several impediments to the test stability:
- tests dont set up their env individually
- some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel
- is blocked by
-
JBIDE-23491 Integration tests: CleanUpOS3 fails if no connection exists
- Closed
-
JBIDE-23497 Integration tests: StoreConnectionTest isnt working
- Closed
-
JBIDE-23499 Integration tests: ConnectionWizardLinkTest isnt working and has wrong class name
- Closed
-
JBIDE-23502 Integration tests: ConnectionPropertiesTest cannot be run individually in JBT
- Closed
-
JBIDE-23504 Integration tests: OpenNewConnectionShellTest will fail if a connection exists in the workspace
- Closed
-
JBIDE-23506 Integration tests: tests that assert "Show in > Browser" are not working, should be removed
- Closed
-
JBIDE-23509 Integration tests: ProjectNameValidationTest cannot run individually, it requires a connection
- Closed
-
JBIDE-23659 integrationt-tests: LogsTest is failing and cannot run individually
- Closed
- is related to
-
JBIDE-23463 Properties: Build pod has state of exit code 0 instead of correct status completed
- Closed
- relates to
-
JBIDE-23498 Integration tests: should consistently separate v3 from v2
- Closed