Use Case: Removing Feature

[lvanvugt]

The following flowchart shows the use case:

Note

At this moment there is a one-to-one relation between a feature and a test codeunit. ATDD.TestScriptor cannot handle multiple features in one test codeunit. The consequence is that removing a feature is as simple as removing a whole codeunit

Exceptions

Settings

• Make setting possible that user can disable confirm on removing test codeunit

[lvanvugt]

UI part needs to be finished.

[martonsagi]

@DavidFeldhoff I changed the UI parts, but somehow the backend does not find the Scenario function to be deleted and I get undefined errors back. Maybe it's my test project, can you check it?

Previously, I sent the NewValue instead of OldValue, but I still get the error after fixes.

[DavidFeldhoff]

I'll have a look at it tomorrow, thank you.

[DavidFeldhoff]

@martonsagi I tested it with your bc-department project, but I couldn't reproduce the errors. Can you please give me some more detailed repro steps to figure out the issue?

[lvanvugt]

This seems not to work.

When deleting a feature:

1. I do not get a dialog asking me whether I want to delete the feature
2. The line(s) relating to the feature is/are not removed from the ATDD.TestScriptor page, but
3. The codeunit file remains

See test scenarios

No.	Feature	Scenario
0098	Removing Feature	Remove Feature
0099	Removing Feature	Remove Feature step 2a

in atdd-test-scenarios-and-results.xlsx

[DavidFeldhoff]

Works with 784ed01.
If a feature is inside multiple files, then it checks if a file consists of only this one feature. If that's the case, then the whole file will be deleted.
If the file consists only partially of the feature, then only the test methods of that feature will be deleted.

[lvanvugt]

It seems not to do what you describe, @DavidFeldhoff, i.e. delete the codeunit file when this contains only one feature.

[DavidFeldhoff]

What you're doing there is that you remove a scenario - not the feature itself.
If you'd open the feature pane and then hit the trash-button there, then this file would be deleted.
That's how it is implemented now. Would you like it to change?

[lvanvugt]

I must have been sleeping. Will have a look again. Thanx and apology.

[DavidFeldhoff]

See here how it should work

[lvanvugt]

Tested and not (fully) OK

• No dialog asking the user whether the Feature should be removed
• In case of multiple features in one codeunit no dialogs asking to move helper functions
• Feature tag in OnRun is not removed when multiple features in one test codeunit

[DavidFeldhoff]

This should be fixed now. @lvanvugt: Time for testing ;)

[lvanvugt]

Hope to find some time this weekend to test it. This is loaded including the start of the project for the 2nd edition of my book. ;-)

[lvanvugt]

We're getting close.

2 out of 3 scenarios do work.

When deleting a FEATURE that's spread over multiple (2) codeunits, they are not removed. See scenario 0106, that fails.

• "Same Feature" is removed from Features pane in ATTD.TestScriptor page, so this is OK
• But the related files are not removed and the test scenarios in it are still displayed in the TestScriptor pane

No.	Feature	Scenario
0098	Removing Feature	Remove Feature (only one in one codeunit)
0099	Removing Feature	Remove Feature (only one in one codeunit) step 2
0103	Removing Feature	Remove Feature (two in one codeunit)
0104	Removing Feature	Remove Feature (two in one codeunit) step 2
0105	Removing Feature	Remove Feature (two in two codeunits)
0106	Removing Feature	Remove Feature (two in two codeunits) step 2

in atdd-test-scenarios-and-results.xlsx

[lvanvugt]

Retested, together with David (important requirement ;-) it is working!