Automates "start workspace using IntelliJ IDEA Editors" test

[olkornii]

What does this PR do?

Automates "start workspace using IntelliJ IDEA Editors" test

What issues does this PR fix or reference?

Jira issue: https://issues.redhat.com/browse/CRW-9410

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix or new feature
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[dmytro-ndp]

The XPath '/html/body/h1' of the title looks too common, as it doesn't contain any workspace- or editor-specific information to distinguish it from other regular HTML page.

What do you think about an XPath which checks for the presence of HTML code like h1>Workspace (workspace name) is running</h1>?

[olkornii]

'/html/body/h1' XPath is exactly an XPath of HTML code "h1>Workspace (workspace name) is running</h1". There is a check for exact text: https://github.com/eclipse-che/che/pull/23765/changes#diff-732c71179bfd939d6b555b70a9ce4b4f28264ba1f6bedc94a9b2756d48a2fe42R118

[dmytro-ndp]

@olkornii: taking into account that the test script contains 104 separate test runs, it would be useful not to stop test execution if one of the tests fails, but rather continue running follow up test and then collect test failures to display at the end.
There is a setting "bail: false", which can help.

[dmytro-ndp]

@olkornii: FYI: StartWorkspaceUsingIntellijIdeEditor test runs against online and airgap DS 3.27.0-RC.03.16 have passed.

Good job!

[olkornii]

@olkornii: taking into account that the test script contains 104 separate test runs, it would be useful not to stop test execution if one of the tests fails, but rather continue running follow up test and then collect test failures to display at the end. There is a setting "bail: false", which can help.

there is a parameter: "MOCHA_BAIL=false". It is what we need. Works as expected.

[dmytro-ndp]

polling is the default delay between tries in milliseconds between tries

TS_SELENIUM_START_WORKSPACE_TIMEOUT is not suitable here

[dmytro-ndp]

see comment https://github.com/eclipse-che/che/pull/23765/changes#r3006654444

[dmytro-ndp]

When bail: false, if testWorkspaceStartup fails after opening a new tab but before the workspace name is captured, getWorkspaceName() returns 'undefined' and teardown skips deletion.

This leaves an orphaned running workspace. With 117+ test combinations and bail: false, multiple orphans could accumulate and exhaust cluster resources or cause cascading failures.

Consider using kubernetesCommandLineToolsExecutor in teardown to clean up by workspace name prefix or label as a fallback.

Suggested change

	}
	} else {
	// fallback: delete DevWorkspace by CLI when name wasn't captured
	Logger.warn('Workspace name was not captured. Attempting cleanup via CLI.');
	kubernetesCommandLineToolsExecutor.deleteDevWorkspace();
	}

[dmytro-ndp]

It's interesting to see test failures when the parameter "MOCHA_BAIL=false" is set.

To simulate this situation, you can set a non-existent Git URL in the gitRepoUrlsToCheck variable, and a non-existent sample name.