Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Provide tests for Camel Che stack and their plugins #14780

Closed
apupier opened this issue Oct 4, 2019 · 15 comments
Closed

Provide tests for Camel Che stack and their plugins #14780

apupier opened this issue Oct 4, 2019 · 15 comments
Assignees
@apupier
Labels
area/qe area/samples kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system. status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage.
Milestone
Backlog - QE

Comments

@apupier
Copy link
Contributor

apupier commented Oct 4, 2019 •
edited
Loading

test with following cases are important:

  • Start Camel Che stack
  • can have completion on Camel java files
  • can have completion on Camel URIs
  • can launch the build task successfully

nice to have:

  • validation on Camel URI
  • outline of Camel elements
  • navigation between "direct" Camel component in 2 different files opened
@apupier apupier added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Oct 4, 2019
@apupier apupier mentioned this issue Oct 4, 2019
Closed
23 tasks
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 4, 2019
@rhopp
Copy link
Contributor

rhopp commented Oct 4, 2019

@apupier Do you think you would be able to contrubute those tests? We can guide you and help you create them ;-)

If not, please try to provide more detailed instructions (or screencast ;-) )

@rhopp rhopp added area/languages Issues related to Language extensions or plugins integration. severity/P2 Has a minor but important impact to the usage or development of the system. team/che-qe and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 4, 2019
@apupier
Copy link
Contributor Author

apupier commented Oct 8, 2019

Do you think you would be able to contrubute those tests? We can guide you and help you create them ;-)

interested in providing them.
I noticed 2 places for tests:
https://github.com/eclipse/che/tree/master/selenium/che-selenium-test/src/test/java/org/eclipse/che/selenium
https://github.com/eclipse/che/tree/master/e2e/tests

Not sure from which one I should start with.

How to launch these tests? What is the recommended way to develop tests?

@rhopp
Copy link
Contributor

rhopp commented Oct 9, 2019 •
edited
Loading

https://github.com/eclipse/che/tree/master/e2e/ is the correct place.

You can create another spec.ts file for the devfile/stack you want as this one: https://github.com/eclipse/che/blob/master/e2e/tests/e2e/JavaVertx.spec.ts

Instructions of how to run the tests are in the readme file: https://github.com/eclipse/che/blob/master/e2e/README.md

If you need any info, feel free to contact us in our eclipse mattermost channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe

@rhopp rhopp added this to the Backlog - QE milestone Dec 4, 2019
@apupier
Copy link
Contributor Author

apupier commented Apr 7, 2020

interested in providing them.

already a long time on standby. I fear I won't have time to work on that in near future

@rhopp rhopp added the area/qe label May 11, 2020
@rhopp
Copy link
Contributor

rhopp commented Sep 16, 2020

Seems like to implement this (mostly the last step - can launch the build task successfully) we need a running Camel K instance. This is already being discussed in #17015 and #15391, so I'm putting this issue on-hold until #17015 and #15391 are resolved.

@rhopp rhopp added the status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage. label Sep 16, 2020
@apupier
Copy link
Contributor Author

apupier commented Sep 16, 2020

in the test infrastructure we can add a Camel K instance.

We are doing it for VS Code Camel K test for instance: https://github.com/camel-tooling/vscode-camelk/blob/3a49334ab30ea338d4c497bcd0d0995b84928a38/.travis.yml#L26-L46

The other issues are currently blocked for a very long-time due to Che limitations. I don't think that we should wait for them. To use the stack currently, the requirement is that there is a Camel K isntance deployed somewhere and accessible. it sounds like a reqyuirement that needs to be fulfilled by the test infrastructure.

@rhopp
Copy link
Contributor

rhopp commented Sep 16, 2020

Out of curiosity - what's the compute requirements (ram/cpu) for running camel K instance needed for tests?

@apupier
Copy link
Contributor Author

apupier commented Sep 16, 2020

Out of curiosity - what's the compute requirements (ram/cpu) for running camel K instance needed for tests?

i don't have this information.
it is running fine on Travis which has 7.5Gb https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system . it includes a minikube instance and Camel K deployed on it (and the VS Code instance). I think most of the place is taken by minikube. If you already have a container it should be really small.

@che-bot
Copy link
Contributor

che-bot commented Mar 17, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 17, 2021
@ericwill
Copy link
Contributor

cc @Ohrimenko1988

@ericwill ericwill removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 17, 2021
@apupier
Copy link
Contributor Author

apupier commented Jul 23, 2021 •
edited
Loading

Plugin tests seem to have been moved too https://github.com/eclipse/che/tree/main/tests/e2e/tests/plugins and https://github.com/eclipse/che/blob/main/tests/e2e/tests/devfiles

@apupier apupier self-assigned this Jul 23, 2021
apupier added a commit to apupier/che that referenced this issue Jul 23, 2021
@apupier
feat: provide minimal test for Camel on SpringBoot stack
03fcb2d 
eclipse-che#14780

- check start of workspace
- check Camel and java language server initialized by checking
completion
- check build task

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@apupier apupier mentioned this issue Jul 23, 2021
Closed
9 tasks
apupier added a commit to apupier/che that referenced this issue Jul 28, 2021
@apupier
feat: provide minimal test for Camel on SpringBoot stack
2a64960 
eclipse-che#14780

- check start of workspace
- check Camel and java language server initialized by checking
completion
- check build task

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@che-bot
Copy link
Contributor

che-bot commented Jan 19, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2022
@che-bot che-bot closed this as completed Jan 26, 2022
@svor svor reopened this Jan 27, 2022
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2022
@che-bot
Copy link
Contributor

che-bot commented Jul 26, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2022
@svor
Copy link
Contributor

svor commented Jul 26, 2022

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2022
@l0rd l0rd added area/samples and removed area/languages Issues related to Language extensions or plugins integration. labels Jan 30, 2023
@nallikaea
Copy link
Contributor

Outdated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@apupier apupier

Labels
area/qe area/samples kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system. status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage.
Projects
None yet
Milestone
Backlog - QE
Development

No branches or pull requests
8 participants
@nickboldt @l0rd @apupier @rhopp @svor @ericwill @che-bot @nallikaea