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

Integration testing user stories #346

Closed
bryk opened this issue Feb 10, 2016 · 15 comments
Closed

Integration testing user stories #346

bryk opened this issue Feb 10, 2016 · 15 comments

Comments

@bryk
Copy link
Contributor

bryk commented Feb 10, 2016

We're doing integration/e2e testing based on user stories. This issue names and enumerates the stories.

  1. "Simple deploy" -> Deploy 1 replica nginx application using simple deploy form. See that a card for it is created.
  2. "Advanced deploy" -> Deploy multi replica nginx application. Expose port 80 externally. Access the external endpoint. See that details page has N pods listed.
@bryk
Copy link
Contributor Author

bryk commented Feb 10, 2016

CC @floreks @maciaszczykm @cheld +others

Can you add other stories so that we have, like, 3-5 of them?

@floreks
Copy link
Member

floreks commented Feb 10, 2016

"Deploy not existing image" -> Deploy not existing app like test. Check that card has error status notification. Check error msg. Go to details page, events tab. Filter by warnings and check. Go to logs and also check for errors.

@maciaszczykm
Copy link
Member

Few proposals:

  • deploy to newly created namespace - create new namespace, then deploy application into it using deploy form
  • deploy from .yaml file - deploy application using .yaml file, check if details page matches application specification from .yaml file
  • delete application - delete application (can be tested with and without service option)
  • update pods count - update pods count and check if it was updated

@cheld
Copy link
Contributor

cheld commented Feb 10, 2016

  1. "Simple Deploy" ...click link and check if application is running
  2. "Advanced deploy"...deploy guest book, check if application is running. enter one value and see that it is displayed.

This is a minimum sanity check, I would like to see.

What about using a different container than nginx? Some special test container similar tutum/hello-world?

@bryk
Copy link
Contributor Author

bryk commented Feb 10, 2016

Using other image than nginx sounds good to me.

@bryk
Copy link
Contributor Author

bryk commented Feb 15, 2016

Ok, let's move forward with this. I'll propose a plan, but interrupt me if you have other ideas.

@bryk
Copy link
Contributor Author

bryk commented Feb 15, 2016

Let's split the work here.

  1. I'll take "Simple deploy" scenario. Implement it first, trying to fix any issues with our test setup.
    Then
  2. @floreks implements "Deploy not existing image"
  3. @maciaszczykm implements deploy from yaml test
  4. @cheld Can you find somebody to implement "delete" and "update pods count" tests?

What do you think?

@bryk bryk modified the milestone: v1.0 Feb 15, 2016
@cheld
Copy link
Contributor

cheld commented Feb 15, 2016

@digitalfishpond

@cheld
Copy link
Contributor

cheld commented Feb 15, 2016

@batikanu

@cheld
Copy link
Contributor

cheld commented Feb 15, 2016

Please pick

BTW: we have also details-page, events-tab and logs-page

We also wanted to start some manual testing. Maybe better if we do not all the same task the same time...

@bryk
Copy link
Contributor Author

bryk commented Feb 16, 2016

BTW: we have also details-page, events-tab and logs-page

Yes, I know. I picked something to start with.

@bryk
Copy link
Contributor Author

bryk commented Feb 16, 2016

We also wanted to start some manual testing. Maybe better if we do not all the same task the same time...

This should not cause problems. They're separate tasks.

@digitalfishpond
Copy link
Contributor

I will pick update pods count if that's ok with you @batikanu

@maciaszczykm
Copy link
Member

I'm starting to work on delete replication controller intrgration tests.

@bryk
Copy link
Contributor Author

bryk commented Mar 4, 2016

Closing as done.

@bryk bryk closed this as completed Mar 4, 2016
anvithks pushed a commit to anvithks/k8s-dashboard that referenced this issue Sep 27, 2021
[Feature][Fixes kubernetes#327] Added a user guide and FAQs with short demos for the dashboard.
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

No branches or pull requests

5 participants