More Related Content
Similar to Test Automation using UiPath Test Suite - Developer Circle Part-3 - 07262022.pdf (20)
More from Diana Gray, MBA (20)
Recently uploaded (20)
Test Automation using UiPath Test Suite - Developer Circle Part-3 - 07262022.pdf
- 1. Test Automation using UiPath Test Suite – Developer Series Part 3 of 4
- 2. Diana Gray Community Marketing Manager AMER @UiPath Meet today’s team: Atul Trikha RPA Architect, COE Lead & Account Chief Technologist @Peraton Sreenivasa Adathakula Test Automation Lead @Peraton
- 3. About today’s UiPath developer meeting: • AMER Developer Community sessions • Managed by UiPath MVPs in Canada, Latin America & USA • You are encouraged to network with MVPs and share your LinkedIn in the chat box. We want to get to know you • These sessions are for you to engage with us on topics that interest you or that you want to share with the UiPath Developer Community • Please use the chat to place questions until Q&A • If you have any topics that you want us to cover, please email diana.gray@uipath.com
- 6. Date/Time Topic Status July 12, 5PM EDT Test Automation using UiPath Test Suite - Developer Series - Part 1 of 4 Recorded July 19, 5PM EDT Test Automation using UiPath Test Suite - Developer Series - Part 2 of 4 Recorded July 26, 5PM EDT Test Automation using UiPath Test Suite - Developer Series - Part 3 of 4 Happening Aug 2, 5PM EDT Test Automation using UiPath Test Suite - Developer Series - Part 4 of 4 Register now Register for Events at community.uipath.com
- 7. 7 Part 1: Building Blocks, Test Suite Product Overview Part 2: UiPath Test Suite Family of Products Part 3: Deep Dive into Test Suite capabilities Test Automation using UiPath Test Suite 4 Parts Developer Series Part 4: Open Discussion and Wrap up
- 8. 8 Part 3: UiPath Test Suite Deep Dive • Overview of Environment Setup • RPA Testing • Application Testing (Web Application, Windows Application) • API Testing • Code Coverage • Data-Driven Testing • SAP Testing • Mobile Testing Create a simpler, smoother, and more productive testing experience.
- 9. Live Demo
- 10. Q & A
- 11. 16 Test Automation Best Practices • Test cases should be independent of each other. One test case should not depend on another test case’s run. • A test case should have one specific purpose only. Each test workflow should contain only one verification. • Every feature should have a unit test. If exceptions are allowed, create a separate test for each test case. • In a Given-When-Then test case structure, if the Given part is getting too extensive and unmanageable, try to redefine the test case. It could need more granularity or refactoring. • Maintain the test cases and update them after any change request. • Consider establishing a Test Management logic to have a single way of defining test cases. • To increase reusability between individual test projects, as well as between test and RPA projects, try to use libraries and object repositories, whenever possible. • Include the tests in the CI/CD pipeline. • Functional tests as part of your CI pipeline should be run as quickly as possible so as to not delay your build. Therefore, try to execute these tests in parallel on as many robots as possible. • Activity names should reflect the action taken. For non-obvious behaviors, consider using annotations on your activities. • Consider using detailed logging and exception handling to debug the process and avoid false negative results. • Plan for recovery or retry for errors at different stages to avoid failed results. • Consider having a folder structure dedicated to testing and using the same test case naming convention across your projects. • Use assets for variables that are likely to change and used many times. • For scenarios where an application’s state must be validated before proceeding with certain steps in a process, consider applying validation measures. These measures can include using extra activities that wait for the desired application state before other interactions (hardcoded delays are not considered good practice). • Consider using simulated click/ type or send windows messages, whenever possible. • Do not delete, move or rename the test cases outside of Studio. Perform these actions in Studio only. Use Import Test Cases in case there is a test case from another project that should be referenced.
- 13. Setup Details • Signed to Automation Hub Enterprise Trial • UiPath Studio Downloaded and Installed • Studio Connected to Orchestrator • Automation Project (Source Code/Repo) in Git • Test Robot Setup using AWS EC2 VM • Studio Connected to Test Manager • Test Manager Connected to Azure DevOps (ALM) • Azure DevOps CI/CD Connecting UiPath Studio to Orchestrator From The UiPath Assistant Go to Preferences
- 14. Creating Test Automation Project
- 15. Adding UiPath Test Suite Project to Source Control (Git)
- 17. URL Copied white Creating GIT Credentials in DevOps Azure
- 18. Credentials Copied white Creating GIT Credentials in DevOps Azure
- 19. Connecting Studio to Test Manager
- 22. Connecting UiPath Test Manager with Azure DevOps
- 24. Creating Service Connection on Azure DevOps for CICD
- 26. Create Azure DevOps CICD Pipeline
- 29. No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request