Solved

UAT Testing

  • 6 March 2024
  • 3 replies
  • 31 views

Badge +2

Hi, can someone tell me after developing the code how to push the code with dependencies into UAT environment to test it. And how they are going to test the code in UAT environment.

icon

Best answer by ChanduMohammad 7 March 2024, 03:38

View original

3 replies

Userlevel 5
Badge +12

Hi @Pushpi 

 

To export your bots and dependencies from the Development Control Room to the UAT Control Room, you can use the Export and Import feature. You can refer to the documentation provided for detailed instructions on how to perform this task.

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/bot-insight/user/cloud-bot-lifecycle-management.html

Once you move the bots and dependencies, the end user or client will test the bots and their functionality end-to-end to ensure they meet their business requirements. If the results are positive, they will provide approval for production deployment. Basically, you or Business Analyst need to prepare a checklist for them to test the scenarios in UAT. Make sure Bot runner account has all the application access before initiating UAT with client or end user. 

Regarding the checklist, this varies from organization to organization. Check with your CoE team if they have one prepared as a template or checkout below columns for creating a new one. Feel free to customize as per your organization needs.

  1. Process Name: Name of the RPA process being tested.
  2. Test Case ID: Unique identifier for the test case.
  3. Test Scenario: Description of the scenario being tested.
  4. Test Steps: Step-by-step instructions for executing the test.
  5. Expected Result: Expected outcome of each step.
  6. Actual Result: Outcome observed during test execution.
  7. Pass/Fail: Indicates whether the test passed or failed.
  8. Comments: Any additional notes or observations.
  9. Priority: Priority level of the test case (e.g., High, Medium, Low).
  10. Assigned To: Person responsible for executing the test.
  11. Status: Current status of the test case (e.g., Not Started, In Progress, Completed).
  12. Environment: Testing environment details (e.g., Development, QA, Production).
  13. Data Input: Input data required for the test case.
  14. Dependencies: Any dependencies needed for executing the test case.
  15. Attachments: Any supporting documents or files.
Badge +2

Thanks for the answer @ChanduMohammad . Even we use that export and import option for deplyoment also right.

Userlevel 5
Badge +12

Hi @Pushpi

If this helps, please mark my answer as Best so it will help others too 

Reply