-
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: Removing Scenario #39
Comments
If the Scenario has handler functions these should be deleted (after a confirmation of the user) as well, I guess? I'll implement it like this at first. |
Agree. |
@DavidFeldhoff no commits related to this issue? |
Sorry, haven't linked that appropriately. Will fix that later |
fixed in commit |
..Forgot the removal of HandlerFunctions - I hope I can add that this evening |
hm.. already implemented that as well in the commit above, but I'm using there the gotodefinition provider of my al-codeactions there, so I added that as dependency. |
@DavidFeldhoff tested and OK |
@DavidFeldhoff: reopened as the settings have not been added yet. |
Hi Luc, feel free to test this one, it's ready and works as well with the settings. |
Tested and added some extra scenarios -> OK |
Reopened due to #80. |
Closed as #80 cannot be reproduced. |
The following flowchart shows the use case:
Exceptions
Settings
Notes
Test Scenarios
in atdd-test-scenarios-and-results.xlsx
The text was updated successfully, but these errors were encountered: