Selection Resources
Solution Areas
Product Selection Tools
Evaluation Guides
Readiness Overview
Identifying Stakeholders
Managing Expectations
Prepare to be Prepared
AI Services
Testing Automation
Upgrade Services
Project Management
Roadmap Services
Data Migration
Data & Analytics
Licensing Support
Train & Optimize
Local Support
Resources
Avantiico Industry Solutions
Explore by Business Need
Microsoft Business Apps
Avantiico Industry Solutions
Microsoft Platforms
Licensing & Pricing Options
Partner Program
Our Partners
Careers
Avantiico Academy Program
Browse Roles
About Avantiico
Events & Webinars
Microsoft recognized and responded to this difficulty by adding a new tool to their previous investments that allows for automated testing, the Regression Suite Automation Tool (RSAT). By supporting testing automation, the effort of manual testing can be significantly reduced, thereby positioning businesses to take full advantage of new feature releases without the heavy burden resting on their process owners. RSAT significantly reduces the time and cost of user acceptance testing, providing a more efficient approach.
By adding “gestures” and validation steps, you can devise robust and repeatable process scenarios that RSAT will understand and execute.
While recording, right-click the field you want noted in RSAT, select “Task recorder,” then click “Copy.” This “gesture” will create a variable once RSAT generates the parameter files. This method ensures that RSAT settings are configured correctly for optimal results.
“Gesturing” is the use of special Task Recorder functions, such as “Copy and Paste,” which are not viewable in the recording but are understood by RSAT. These functions make note of fields of your choosing and, upon creating the executables and parameter files in RSAT, convert those gestures into variables which can be used to “chain” your test cases together. Utilizing these gestures helps convert them into a suite of automated tests.
Validation steps are also critical when the expected results should be verified as a part of the test case. Where an inventory quantity should be updated and verified from a Sales Order that has been picked, packed and invoiced, it is useful to have such a validation step in your recording file.
Planning test cases by role will allow you to use validations to verify results as well as test your security to prepare for the update or testing of a new security role. Security updates and validation steps are essential components in maintaining a robust testing framework.
Great task recordings follow the business process closely. Business process owners who know these processes well and the use cases involved are critical to the success of an IT effort to automate. A deep collaboration between process owners and technical/functional resources responsible for test automation is essential to a successful automation test suite.
Great task recordings follow the business process closely. Business process owners who know these processes well and the use cases involved are critical to the success of an IT effort to automate. A deep collaboration between process owners and technical/functional resources responsible for test automation is essential to a successful automation test suite.
Once RSAT is connected and operational, it is time to configure your test cases and execute them.
The first step is to Load them into RSAT from DevOps. This will bring all the information about the test case into RSAT, specifically the test recording itself. Once loaded, select the Test Cases you would like to run and Generate the Executable Files. This will generate DLLs, C# code and the Excel parameter files into RSAT’s working directory that you will need to chain your tests together.
The power of Excel formulas can be used and is particularly useful. For instance, you may wish to randomize a field’s value upon entry in which case you may use an Excel formula to do so.
Validations is another great way to use formulas. Capturing a value in one step and adding it into a value captured in a subsequent step can now provide you with a logical step using comparison operators such as “=”, “<” ,” >”, etc.
Should a recording need to be referenced in multiple chained sequences, you need not record the test case more than once. You simply mark it as a “derived” test to allow access to it in other test chains.
Once ready, mark the tests ready to be run and click “Run” from the RSAT console.
Executing your test cases will invoke RSAT to “print to screen” all the test steps from the task recordings as it performs them. You will see the message “Chrome is being controlled by automated test software.” The screen captures are accessed by DevOps to illustrate where and how errors occur along with XML information about any error encountered.
Additionally, in the DevOps environment, you will find a very rich feature set to help you manage errors as well as your test runs.
While executing RSAT through the console is extremely useful for debugging purposes, it also adds performance overhead to the Test Runs. Once you are satisfied with your tests, you may wish to execute them from a command line or invoke the run from Power Automate. RSAT provides several command-line keyword parameters which gives you full control to schedule these test runs after business hours.
Being prepared for One Version of Microsoft’s D365 Finance and Operations has never been more important. Microsoft’s Regression Suite Automation Tool will help you document your business processes, limit the amount of manual testing by business owners and position your business to increase your ROI with every Microsoft update.
Book a free meeting and let us have a look at your opportunities with Microsoft Solutions
Discover how Avantiico helps you improve business processes, provide customers with a seamless experience and transform the way you do business.
Discover how Avantiico helps you improve business processes, provide customers with a seamless experience and transform the way you do business.