Use Case: Updating Scenario

[lvanvugt]

The following flowchart shows the use case:

Exceptions

• Non-alphabetical or non-numerical characters should not be ported to test function name (see also Use Case: Adding Scenario #38)
• Scenario description should not have unlimited length as AL function names have a max length of 120 characters (see also Use Case: Adding Scenario #38)
  • I suggest to build logic that checks allowed length in Scenario description based on text with "to be removed" non-alphabetical or non-numerical characters

Settings

• Make setting possible that user can set max length to Scenario description himself (see also Use Case: Adding Scenario #38)

[DavidFeldhoff]

@martonsagi I'm done with my changes on this one, but there are some small issues which need to be fixed by you:

• "Are you sure you want to update this scenario?" -> No -> New value stays in textbox (or it's just a refreshing issue as if i reopen the scenario it has the old value again)
• I'm triggered on each keypress. The given/when/thens instead are only triggered if I leave the field. Could you change that to make it more consistent?

[martonsagi]

Value update should be ok now. Keypress triggers have been extended with a reasonable timeout to be triggered again.

[DavidFeldhoff]

@martonsagi it works much smoother now, thanks!
But the first issue I mentioned in my previous post still exists:
Currently:
Change Scenario -> Do you want to update? -> No -> The new value (which wasn't confirmed) remains in the field.
Expected:
Change Scenario -> Do you want to update? -> No -> The old value is placed again in the textbox

[DavidFeldhoff]

I made it explicit here #71