-
Notifications
You must be signed in to change notification settings - Fork 3
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
Use Case: Copying Scenario #65
Comments
lvanvugt
added
the
version B
Next to be picked up (but needs probably some detailing)
label
Oct 5, 2020
lvanvugt
pushed a commit
that referenced
this issue
Oct 5, 2020
@martonsagi and @DavidFeldhoff how much work would this be? |
The UI part can be done in an afternoon time. |
I should get it done on a weekend |
lvanvugt
added
version A
To be picked up right away
and removed
version B
Next to be picked up (but needs probably some detailing)
labels
Nov 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following flowchart shows the use case:
Notes
Exceptions
Theoretically it is possible that the new name Copy of already exists in the test codeunit where the scenario copying occurs. In that case an error should be thrown likewise when updating a scenario (see #60).
The text was updated successfully, but these errors were encountered: