How To Use Regression suite automation tool (RSAT) For Microsoft Dynamics 365 Finance and Operations

[@D365FINANCEANDOPERATIONS]

Timecodes: 0:00 - Introduction 0:21 - What is RSAT 1:28 - Connect RSAT with D365 F&O cloud-hosted environment 2:46 - Create a new project in LCS for RSAT 5:00 - Create a new project in Azure DevOps 6:40 - Create personal access token in Azure DevOps 8:43 - Create a test plan in Azure DevOps 9:12 - Create a test suit in Azure DevOps 9:53 - Connect Azure DevOps with LCS 12:08 - RSAT tool setting 21:00 - Create BPM library in LCS 23:45 - How to Create test cases in D365 F&O 26:16 - Sync test cases with LCS 24:45 - Add test case in Azure DevOps 28:25 - load and Run test cases in the RSAT tool 32:50 - Connect D365 UAT environment with RSAT

[@intelcore2quad88]

Thanks you so much for your video.

[@D365FINANCEANDOPERATIONS]

You are most welcome

[@shanewatson8757]

Very detailed video and to the point. Thank you!

[@tatonjr3742]

Hello, very good video, it helped me configure everything rsat without major problems. I have a problem, when I save the recording of the task in LyfeCycle Services, the BPM library loads but without the names, they all appear with new business process, I do not name them such as create sale order

[@mohammedakbarpasha9066]

Hi...i followed hour steps from the video , but when trying to add the test case into test plan, the test case is coming as type Epic, not as test case, so unable to add it to test plan in azure..please advice how type can come as test case.

[@yassermohamed281]

Thank you, Is there a way that we can do the testing on our one box dev machine without connecting to the LCS ?

[@sforshah]

Retail commerce testing video needed

[@harv46]

Very useful video brother and it helps me configure rsat without any issues. I have a question like how do we identify that these records are created for testing by rsat. Can we differentiate or can you suggest me how to identify it .

[@D365FINANCEANDOPERATIONS]

To identify test records created by RSAT (Regression Suite Automation Tool) in D365 FO, consider using naming conventions, such as prefixing test records with "TEST_." You can also tag test records with a "Test" category, restrict access through user roles, or add a custom flag indicating the record's purpose. Maintaining separate testing and production environments and regularly cleaning up obsolete test data are also effective ways to differentiate and manage test records. These practices help prevent confusion and ensure data integrity.

[@hemantjohari]

Please create video on D365 commerce also, Thanks.

[@meenakshigoyal3534]

how can I contact you for further details/learning?