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

Expand QA test for Start Instance Anywhere #10382

Closed
korthout opened this issue Sep 16, 2022 · 0 comments · Fixed by #10383
Closed

Expand QA test for Start Instance Anywhere #10382

korthout opened this issue Sep 16, 2022 · 0 comments · Fixed by #10383
Assignees
Labels
kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0

Comments

@korthout
Copy link
Member

Description

This is the follow-up of

The process instance creation with start instructions (or Start Instance Anywhere) feature already has an end-to-end integration test, introduced with

However, we identified that additional assertions can be made to improve this test. Specifically:

We could extend the test cases to verify that all given instructions are applied. It is not about verifying the logic exhaustively but to confirm that all command arguments are passed from the client to the broker.

A similar test was expanded for process instance modification

@korthout korthout added the kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. label Sep 16, 2022
@korthout korthout self-assigned this Sep 16, 2022
@Zelldon Zelldon added the version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0 label Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants