LinkedIn
Twitter
A number of test scenarios refer to properties the test is being applied too, which is created as an enum list of keys.
E.g. Properties ENUMList { propertykey001, propertykey002, propertykey003 }
To remove a property from the list, uses the following: INTERSECT([Properties], Property[Propertykey])
So when a property is deleted the following actions are triggered to clean-up and remove references to the deleted property.
- Remove loan-details
- Remove test results
- Delete the property *
- Lastly update the test-scenarios to remove the now deleted property from the test-scenarios.
Steps 1-3 work fine, the last step [4] does not work. * This may be because it needs to wait for the property to be deleted. I have tried this as a Group of actions as listed above. Also as a BOT see screenshot below.
Please note step [4] does work if you leave the action visible and click on it manually.
The Bot runs without error but the references in the test-scenarios to the now deleted property remains. This is likely to be something simple, hence the question.
Many thanks @Steve for the explanation. The problem is how do I tell the actions in the list which property is being deleted? For now I have created a 'logical-deleted' flag, which is the first action and sets this flag. While the record physically exists, the other actions have something to reference. The UI then filters-out the logically-deleted records so they are not displayed.
Not ideal, but I wasn't sure if there was a de-reference of some description that would work. This solution is using Actions alone, not a Bot.
At present I appear to have hit another snag. A difference in behaviour between the ipad / iphone version, classic desktop mode and the new desktop mode.
It appears a Form Save action is not being triggered in the new desktop mode, but works fine in the other versions. This is stopping me from demonstrating the app in the new desktop mode. See screenshot. I do not know if there is a quick work-around for this. I have spent a couple of days looking at this, before discovering it was a UI behavioural issue. Have you heard of such an issue? If not I'll raise it with support.
