[jbosstools-issues] [JBoss JIRA] (JBIDE-25142) Stabilization of integration tests for OpenShift

[Josef Kopriva (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-25142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josef Kopriva updated JBIDE-25142:
----------------------------------
    Description: 
Generally speaking there are 2 general rules of thumb that we need to aim for when fixing the tests:
* We should have integration tests that are *larger usecases*: integration tests are time consuming to run, especially when compared to unit tests. It's therefore preferable to have *a few large* integration tests than many small integration tests
* Integration tests should be *runnable individually*: the existing code base is requiring to run the tests in a specific sequence (ex. test Y is expecting an OpenShift resource - that test X creates - to exist). That's a major burden: one would have to run the whole lengthy suite to just create a new test for a new feature that was implemented
* During stabilization try to reuse projects/apps/resources as much as it is possible to reduce time for building applications, so this needs to rewrite classes

This jira tries to fix the remaining ITests for OpenShift (that are currently not included in stable suite) while aiming at the goals above:
{code:java}
// General
OCBinaryLocationTest.class,

// Connection
CreateNewConnectionTest.class,
StoreConnectionTest.class, 
	
// Project
LinkToCreateNewProjectTest.class,

// Application wizard handling
OpenNewApplicationWizardTest.class,
OpenNewApplicationWizardWithNoProjectTest.class,
BuilderImageApplicationWizardHandlingTest.class,
	
// Creation of a new application
CreateApplicationFromTemplateTest.class,
CreateApplicationOnBuilderImageTest.class,
DeploymentTest.class,
	
// Application handling
DeleteResourceTest.class,
OSExplorerResourceTest.class,
TriggerBuildTest.class, 
ImportApplicationTest.class,
PortForwardingTest.class, 
LogsTest.class, 
EditResourcesTest.class,
HandleCustomTemplateTest.class,
ImportApplicationWizardTest.class,

// Advanced application testing
DeployDockerImageTest.class,
CreateResourcesTest.class,
ScalingTest.class, 

//Server adapter
ServerAdapterWizardHandlingTest.class,
CreateServerAdapterTest.class,
ServerAdapterFromResourceTest.class,
PublishChangesTest.class,
DebuggingEAPAppTest.class,
{code}


Test should be stable on all major platforms: Win, Linux and MacOS.


  was:
Generally speaking there are 2 general rules of thumb that we need to aim for when fixing the tests:
* We should have integration tests that are *larger usecases*: integration tests are time consuming to run, especially when compared to unit tests. It's therefore preferable to have *a few large* integration tests than many small integration tests
* Integration tests should be *runnable individually*: the existing code base is requiring to run the tests in a specific sequence (ex. test Y is expecting an OpenShift resource - that test X creates - to exist). That's a major burden: one would have to run the whole lengthy suite to just create a new test for a new feature that was implemented

This jira tries to fix the remaining ITests for OpenShift (that are currently not included in stable suite) while aiming at the goals above:
{code:java}
// General
OCBinaryLocationTest.class,

// Connection
CreateNewConnectionTest.class,
StoreConnectionTest.class, 
	
// Project
LinkToCreateNewProjectTest.class,

// Application wizard handling
OpenNewApplicationWizardTest.class,
OpenNewApplicationWizardWithNoProjectTest.class,
BuilderImageApplicationWizardHandlingTest.class,
	
// Creation of a new application
CreateApplicationFromTemplateTest.class,
CreateApplicationOnBuilderImageTest.class,
DeploymentTest.class,
	
// Application handling
DeleteResourceTest.class,
OSExplorerResourceTest.class,
TriggerBuildTest.class, 
ImportApplicationTest.class,
PortForwardingTest.class, 
LogsTest.class, 
EditResourcesTest.class,
HandleCustomTemplateTest.class,
ImportApplicationWizardTest.class,

// Advanced application testing
DeployDockerImageTest.class,
CreateResourcesTest.class,
ScalingTest.class, 

//Server adapter
ServerAdapterWizardHandlingTest.class,
CreateServerAdapterTest.class,
ServerAdapterFromResourceTest.class,
PublishChangesTest.class,
DebuggingEAPAppTest.class,
{code}


Test should be stable on all major platforms: Win, Linux and MacOS.




> Stabilization of integration tests for OpenShift
> ------------------------------------------------
>
>                 Key: JBIDE-25142
>                 URL: https://issues.jboss.org/browse/JBIDE-25142
>             Project: Tools (JBoss Tools)
>          Issue Type: Epic
>          Components: integration-tests, openshift
>    Affects Versions: 4.5.1.AM3
>            Reporter: Josef Kopriva
>            Assignee: Josef Kopriva
>              Labels: integration_tests, openshift_v3
>             Fix For: 4.5.x
>
>
> Generally speaking there are 2 general rules of thumb that we need to aim for when fixing the tests:
> * We should have integration tests that are *larger usecases*: integration tests are time consuming to run, especially when compared to unit tests. It's therefore preferable to have *a few large* integration tests than many small integration tests
> * Integration tests should be *runnable individually*: the existing code base is requiring to run the tests in a specific sequence (ex. test Y is expecting an OpenShift resource - that test X creates - to exist). That's a major burden: one would have to run the whole lengthy suite to just create a new test for a new feature that was implemented
> * During stabilization try to reuse projects/apps/resources as much as it is possible to reduce time for building applications, so this needs to rewrite classes
> This jira tries to fix the remaining ITests for OpenShift (that are currently not included in stable suite) while aiming at the goals above:
> {code:java}
> // General
> OCBinaryLocationTest.class,
> // Connection
> CreateNewConnectionTest.class,
> StoreConnectionTest.class, 
> 	
> // Project
> LinkToCreateNewProjectTest.class,
> // Application wizard handling
> OpenNewApplicationWizardTest.class,
> OpenNewApplicationWizardWithNoProjectTest.class,
> BuilderImageApplicationWizardHandlingTest.class,
> 	
> // Creation of a new application
> CreateApplicationFromTemplateTest.class,
> CreateApplicationOnBuilderImageTest.class,
> DeploymentTest.class,
> 	
> // Application handling
> DeleteResourceTest.class,
> OSExplorerResourceTest.class,
> TriggerBuildTest.class, 
> ImportApplicationTest.class,
> PortForwardingTest.class, 
> LogsTest.class, 
> EditResourcesTest.class,
> HandleCustomTemplateTest.class,
> ImportApplicationWizardTest.class,
> // Advanced application testing
> DeployDockerImageTest.class,
> CreateResourcesTest.class,
> ScalingTest.class, 
> //Server adapter
> ServerAdapterWizardHandlingTest.class,
> CreateServerAdapterTest.class,
> ServerAdapterFromResourceTest.class,
> PublishChangesTest.class,
> DebuggingEAPAppTest.class,
> {code}
> Test should be stable on all major platforms: Win, Linux and MacOS.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)