Thanks for the Page Scripting Tool

The current page scripting tool is very valuable, so first I would like to thank the team of Microsoft for the initial implementation.

I would like to suggest three additional features that hopefully can help Microsoft partners increasing their efficiency within the development process.

Proposal 1: New action “create automatic test”

Feature: Ability to create an automatic test from the recorded page scripting. If the ability to seamlessly create the automatic test is not available, the ability to convert the yaml file to AL code would be more work, but would still be a big step forward.

Background/use: Business analysts (employees who deal with requirements/tests but do not code) would be able to support the expansion of automated tests without the need to involve developers.

Proposal 2: New action/option "restore changes in the database"

Feature: Possibility to restore the changes related to the executed play backs. To have the possibility, e.g. at the end of the recording or in a general setting, whether the changes in the database should be reset (technical implementation by recording the table changes and then restoring the original values).

Background/use: When a test case makes changes to tables, which is usually the case, it may no longer be possible to run the test on the same company to achieve the original goal and it may be necessary to work with multiple companies. This function would make working more convenient if the same data constellation is needed.

Proposal 3: Possibility to save recoreded scripts permanently

Function: Save multiple recordings in a structured way to be able to access them even after closing the client and to run different tests separately.

Background/use: Currently, recordings need to be imported manually to run them. There is no simple workflow for multiple tests.