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.

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

E2E test #263

Closed
wants to merge 8 commits into from
Closed

E2E test #263

wants to merge 8 commits into from

Conversation

Mo-Fatah
Copy link

@Mo-Fatah Mo-Fatah commented Apr 12, 2023

Closes #44

┆Issue is synchronized with this Jira Task by Unito

Signed-off-by: mohamed <mohamedabdelfatah2027@gmail.com>
Signed-off-by: mohamed <mohamedabdelfatah2027@gmail.com>
Signed-off-by: mohamed <mohamedabdelfatah2027@gmail.com>
Signed-off-by: mohamed <mohamedabdelfatah2027@gmail.com>
Signed-off-by: mohamed <mohamedabdelfatah2027@gmail.com>
Signed-off-by: mohamed <mohamedabdelfatah2027@gmail.com>
test-e2e: kind docker-build install-cert-manager
kind load docker-image controller:latest
test-e2e: dev-setup
sleep 90
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sleep 90 makes me sad -- ideally we could test in someway for cold start vs. already up-and-running

Copy link
Author

@Mo-Fatah Mo-Fatah Apr 12, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is smelly too. I put it because the dev-install-controller target fails if some of the dev-setup pods aren't running yet. Can you explain more the cold start part?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By cold start he means adding some form of "caching" behaviour. To be honest, I wouldn't like this - I think tests should start from scratch always - I.e always "cold start".

Are you able to test when all the dev-setup pods are running?https://www.ibm.com/docs/en/mvi/1.1.1?topic=environment-checking-kubernetes-services-status

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you able to test when all the dev-setup pods are running?

The current test cases can run only with dev-setup . I could remove the dev-install-controller and the sleep commands. But I think, as this is an initial setup for E2E testing, we will later need the controller installation which requires all the pods from dev-setup to be up and running.

what do you think ?

@codecov
Copy link

codecov bot commented Apr 12, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (857dbed) 84.40% compared to head (696603e) 84.40%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #263   +/-   ##
=======================================
  Coverage   84.40%   84.40%           
=======================================
  Files          13       13           
  Lines        2533     2533           
=======================================
  Hits         2138     2138           
  Misses        278      278           
  Partials      117      117           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@sync-by-unito sync-by-unito bot closed this Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Framework for E2E Test
3 participants