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

Adding more tests in vagrant #257

Closed
6 tasks done
parauliya opened this issue Aug 18, 2020 · 0 comments · Fixed by #537
Closed
6 tasks done

Adding more tests in vagrant #257

parauliya opened this issue Aug 18, 2020 · 0 comments · Fixed by #537
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. size/M estimate of the amount of work to address the issue

Comments

@parauliya
Copy link
Contributor

parauliya commented Aug 18, 2020

Add Few scenarios in vagrant tests

Expected Behaviour

Right now vagrant test setup runs only happy workflow. I would like to have following scenarios in vagrant tests:

  • One workflow with one worker where all the actions are successful

  • One workflow with one worker where an action gets failed

  • One workflow with one worker where an action gets timed out

  • Two workflows with one worker where all the actions are successful in both the workflows

  • Two workflows with one worker where one of the workflow fails and other one runs successfully.

  • Two workflows with one worker where one of the workflow timed out and other one runs successfully.

Possible Solution

Add more test cases on vagrant setup

Context

This will help us to test the code in different scenarios so that whenever we are trying to cut a release, we should run these test scenarios

@parauliya parauliya added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 18, 2020
@parauliya parauliya self-assigned this Aug 18, 2020
parauliya pushed a commit to infracloudio/tink that referenced this issue Aug 18, 2020
1. One workflow with one worker where all the actions are successful
2. One workflow with one worker where an action gets failed
3. One workflow with one worker where an action gets timed out
@gianarb gianarb added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. size/M estimate of the amount of work to address the issue labels Aug 18, 2020
parauliya pushed a commit to infracloudio/tink that referenced this issue Aug 18, 2020
1. One workflow with one worker where all the actions are successful
2. One workflow with one worker where an action gets failed
3. One workflow with one worker where an action gets timed out

Signed-off-by: parauliya <[email protected]>
parauliya pushed a commit to infracloudio/tink that referenced this issue Aug 19, 2020
1. One workflow with one worker where all the actions are successful
2. One workflow with one worker where an action gets failed
3. One workflow with one worker where an action gets timed out

Signed-off-by: parauliya <[email protected]>
parauliya pushed a commit to infracloudio/tink that referenced this issue Aug 21, 2020
1. One workflow with one worker where all the actions are successful
2. One workflow with one worker where an action gets failed
3. One workflow with one worker where an action gets timed out

Signed-off-by: parauliya <[email protected]>
parauliya pushed a commit to infracloudio/tink that referenced this issue Aug 21, 2020
1. One workflow with one worker where all the actions are successful
2. One workflow with one worker where an action gets failed
3. One workflow with one worker where an action gets timed out

Signed-off-by: parauliya <[email protected]>
parauliya pushed a commit to infracloudio/tink that referenced this issue Aug 24, 2020
1. One workflow with one worker where all the actions are successful
2. One workflow with one worker where an action gets failed
3. One workflow with one worker where an action gets timed out

Signed-off-by: parauliya <[email protected]>
@tstromberg tstromberg added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 27, 2021
@jacobweinstock jacobweinstock mentioned this issue Sep 3, 2021
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. size/M estimate of the amount of work to address the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants