Use Case: Adding Given-When-Then

[lvanvugt]

The following flowchart shows the use case:

Exceptions

• Non-alpabathic or non-numerical characters should not be ported to helper function names
• Given/When/Then description should not have unlimited length as AL function names have a max length of 120 characters
  • I suggest to build logic that checks allowed length in Given/When/Then description based on text with "to be removed" non-alpabathic or non-numerical characters

Settings

• Make setting possible that user can set max length to Given/When/Then description himself
• Standard each newly created helper function should get an error statement assigned with test " is not yet implemented"; user should be able to turn this of with a setting
• A setting is needed to provide for each helper function type, i.e. Given, When or Then, a syntax allowing, for example, to add a standard term (verb) to the name.
  • Example were Verify is added as prefix to THEN helper function (see also behavior of the ATDD.TestScriptor PowerShell module)

THEN clause: Warehouse shipment line is deleted
function name:  VerifyWarehouseShipmentLineIsDeleted();

[martonsagi]

@DavidFeldhoff
Hi,

Settings object will be sent in a simple key->value format to the backend.

[lvanvugt]

@DavidFeldhoff does it make sense to include #16 here already?

[DavidFeldhoff]

Yes, definitely 👍

[martonsagi]

@DavidFeldhoff
I have added the UI parts to AddingGivenWhenThen branch. You should now reveice nofitication on the Backend when scenario or given/when/then data changes.

[DavidFeldhoff]

@lvanvugt : It's ready to test in the "AddingGivenWhenThen" Branch

[lvanvugt]

All tests seem to run fine. Retest will be done later when everything needs to be tested again.