-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement C/C++ devfile test #18009
Implement C/C++ devfile test #18009
Conversation
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) ℹ️ |
[crw-ci-test] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) ℹ️ |
168540e
to
b23ba2a
Compare
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
tests/e2e/tests/devfiles/Go.spec.ts
Outdated
commonLsTests.errorHighlighting(fileName, 'error;\n', 42); | ||
// commonLsTests.codeNavigation(fileName, 42, 10, 'flag.go'); // codenavigation is inconsistent https://github.com/eclipse/che/issues/16929 | ||
// commonLsTests.codeNavigationGoTo(fileName, 42, 10, 'flag.go'); // codenavigation is inconsistent https://github.com/eclipse/che/issues/16929 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can it be fixed and uncommented by you're new functionality?
tests/e2e/testsLibrary/LsTests.ts
Outdated
|
||
export function codeNavigation(openedFile: string, line: number, char: number, codeNavigationClassName: string) { | ||
test('Codenavigation', async () => { | ||
export function codeNavigationGoTo(openedFile: string, line: number, char: number, codeNavigationClassName: string, keyCombination: string = Key.chord(Key.CONTROL, Key.F12)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if GoTo
is adding any value here - the codeNavigation
already says that you should be navigated somewhere. Maybe it would be worth adding if it should redirect you to implementation
, definition
, references
...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to prepare it for the two approaches: codeNavigationGoTo
and codeNavigationPeek
as is explained in this issue: #17995
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, so what about renaming this method to codeNavigationGoToImplementation
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessarily, because based on what key combination we send, we can go do Definition, Implementation, References, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GoTo - we expect it to open a new file
Peek - we expect it to show the in-editor peek window
tests/e2e/tests/devfiles/Go.spec.ts
Outdated
@@ -46,7 +46,7 @@ suite(`${workspaceStack} test`, async () => { | |||
projectManager.openFile(fileFolderPath, fileName); | |||
}); | |||
|
|||
suite('Test golang example', async () => { | |||
suite.skip('Test golang example', async () => { // test always fails, because the task does not show a notification about return code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about skipping this test. In 7.19.x the notification was removed in all stacks so we would need to switch to another approach. I prefer to leave it unskipped.
issue for fix: #17973 (comment)
upstream PR with the change: eclipse-theia/theia#8331
blocker for implementing the fix: #17978
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but if it will be unskipped, it will be causing test failures
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, but then it means that it should be skipped in all the devfile tests - I don't see much value in skipping that just in one of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will test it on latest che and skip where necessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert the skipping of test for command in Go. Others are just minor items.
b23ba2a
to
c7854b0
Compare
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
c7854b0
to
25f9681
Compare
I've split the current PR into only C/C++ implementation and improvements that can be found here master...ScrewTSW:local_optimizing_devfile_tests |
Signed-off-by: Tibor Dancs <tdancs@redhat.com>
25f9681
to
16b6adb
Compare
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
What does this PR do?
What issues does this PR fix or reference?
#17709
How to test this PR?
npm i
and verify that all packages install without errorstsc
and verify that no errors are presentTS_SELENIUM_BASE_URL
TS_SELENIUM_MULTIUSER=true
NODE_TLS_REJECT_UNAUTHORIZED=0
TS_SELENIUM_LOG_LEVEL="TRACE"
TS_SELENIUM_USERNAME
TS_SELENIUM_PASSWORD
npm run test-java-vertx
to execute the smoke test devfile and verify that the tests are working correctly or run entire suite usingnpm run test-all-devfiles
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.