Starting Test Automation In Your Project - Webinar by 99X Technology
Download as PPTX, PDF•2 likes•375 views
This document provides guidance on starting test automation in a project. It discusses why automation is important, how to select scenarios to automate, how to choose a testing tool, how to create a proof of concept, how to implement an automation framework, and how to stabilize automated tests. Key steps include selecting high value scenarios, analyzing testing tools, creating sample automated tests with different tools, finalizing an automation framework, integrating tests with continuous integration, and ensuring tests are stable across environments.
Starting Test Automation In Your Project - Webinar by 99X Technology
- 1. StartingTest Automation InYour Project By Kasun Ratnayake Test Automation Lead at 99XTechnology
- 2. Who is this guy? ■ Having 9 years of industry experience ■ Started my career as a developer ■ Doing automation since 2012 ■ All of the companies I have worked/Consulted, I have started or introduced test automation ■ Have worked with many automation tools including – Selenium – QTP – Telerik – CodedUI
- 3. Why Automation? ■ It’s hard to find bugs when the same person is testing the same scenario repeatedly every two weeks(for releases) ■ ROI ■ Increases test coverage ■ Reduced execution time ■ Reusability ■ Reliability Do I have to automate 100% of the application? Do all projects require test automation?
- 4. Selecting scenarios ■ What to Automate : – Scenarios that are included in regression testing – Scenarios that Involve complex and time consuming actions – Scenarios that need to be tested within cross platforms – Scenarios that are time consuming to test manually – Scenarios that use multiple data values for the same actions ■ Scenarios that you should not automate : – Scenarios that are only executed one time – Tests that need to be done very quickly – Scenarios that have low ROI
- 5. Scenarios with low ROI
- 6. Selecting a tool ■ Compatibility with current tool stack ■ The development technology of the application to be tested ■ An automation tool that is well established ■ The tool should accommodate the functionalities of the application ■ Does the team have skilled resources? ■ Community support ■ Support from the vendor ■ Reporting capability ■ Extensibility of the tool
- 7. Tool analysis Functionality Selenium Telerik Coded UI Cross browser functionality 1 1 1 Free 1 0 0 Silverlight support 0 1 0 Windows applications support 0 1 1 Nuget support 1 0 1 Automatic Object Repo Creation 0 1 1 Mobile application support 0 1 0 Record and play back 1 1 1 Total 4 6 5
- 8. Creating a POC ■ Select scenarios that cover the most complex functionalities ■ Select scenarios that are using all the 3rd party controls in the application ■ Make sure to test all the capabilities available in the automation tool against the application ■ Make sure everybody in the automation team participates for the POC ■ Do not worry about formalities ■ Make a sketch of the framework just to verify that it works ■ Verify the results ■ Repeat this process for all the selected tools or start implementation right away
- 9. Implementation ■ Finalize the framework first ■ Start with the Framework ■ Create 4-5 scenarios with the framework ■ The round trip – Add it to a continuous integration framework – Create a test environment – Schedule the tests – Analyze the reports ■ Create the rest of the scripts ■ Test should be created in a way that they are independent from each other
- 10. Creating test data and environments ■ Test Data – Test data should be isolated from the test – Data driven testing technique is very useful to create iterations and run the same test with different data and validate different outcomes – Data hookup points should be configurable ■ Test Environments – Should be similar to the production environment – Environment should be something other than the development environment – Test assemblies should be deployed the test environment automatically – Test-runs should only happen on the test environment – Test environment should be configured in a way that any stakeholder can access the test results at any given moment
- 11. Stabilizing tests ■ The most important thing when creating a new automation suite ■ Some tests can pass on the development environment and fail in the test environment ■ Always close the browser and reopen when running complex scenarios for a considerable amount of time ■ Do not combine two tests. ■ Always reuse code everywhere possible so test maintenances would not be a hectic task ■ Automation tool updates should be configured to happen smoothly
- 12. Summary ■ Selecting scenarios ■ Selecting a tool ■ Creating a POC ■ Implementation ■ Creating test data ■ Creating test environments ■ Stabilizing the tests
- 13. Thank you
Editor's Notes
- #2: This is an introductory session to a series of webinars This is not a technical session This would be very helpful to individuals who are planning to start automation in their projects
- #4: Humans make mistakes but lets keep that out for a second When a test suite gets bigger is it vice to employee new resources? Or to automate atleast a part of the test? Increases: when you test for some scenario do you test it for all the possible outcomes? No but the automation can do that Execution time is massively saved plus the execution will be happen under non working hours Automation test is Robust and reliable
- #5: First you have to select the automatable scenarios Regression: scenarios that you execute in every release Complex scenarios are hard to automate but when its done the ROI is very high When a scenario have to be tested in different test data in iterations
- #6: Normal web page with a table Scenario: you can filer, you can change the order of the rows When you filter you don’t exactly know how many rows should be there To test this manually it will take under 5 seconds right? But to automate this kind of a scenario? Things to consider how many rows in the table which row that I’m going to select and change order which row im going to place it to? What happens in a occasion there are no data? Or 2 rows or 1? after adjusting whether its on the adusted row - take order of one column and store then change t take the row order again and verify hectic job eh? lets say it takes 8 hors to automate and to do this manually its 5seconds how many times you have to run this to get a slight ROI? 720 times so why wasting 12 hours for this type of scenario
- #7: Commercial tool or a open source one?
- #9: If there are any in-house build controls use them with the POC Formalities- data driven testing, object isolation Sketch – create at least one class of the planned framework and make sure the integrations work Select special scenarios that indlused, right clicks, drag and drops, image comparisons
- #10: Framework is the key to a stable automation suite Its better to sit down with an architect and design the framework Implement and finish the framework first Take the scenarios that you used for the POC and implement it inside the framework Round trip is the most important thing Better if you can find a mechanism to do automatic deployment of the automation code to the test environment Always use naming conventions and comments in your code- if you leave the project the others should be able to continue with the automation project with ease
- #11: Golden rule no 1 – test data, so the data can be altered in any moment that the user prefers and this not include new releases of the automation code Iterations – login example Should be able to change data inputs ex: from excel sheets, xml files, text files etc…
- #12: Browser cache can mess up automation tests Make sure all the supporting assembles are installed and deployed in the test environment Always make sure that any test can be isolated and run at any given moment (developer bug fix example) Coping the login code to every test can end up bad if a feature like remember me is added later to the tests Automation tool updates should not cause any new deployments of the solution : eg: nuget pakages