This document discusses test automation within a Scrum process. It begins by providing background on the author and defining test automation. It then discusses how to start with automation, including using frameworks and learning programming skills. It describes how to plan test automation in a Scrum process, including when to automate, criteria for choosing what to automate, and how to plan the automation work. The document then discusses automating test cases, executing automation scripts, and delivering the automation work in a Scrum process. Finally, it briefly discusses some newer trends in test automation.

1. Test Automation within a
Scrum Process
KUSHAN SHALINDRA AMARASIRI

2. About Me
 QA Experience : Nearly 10 years
 Automation Experience : Nearly 7 Years
 Organizations : IFS, OPRO, MIT, Mubasher, Pearson, Virtusa, Eyepax
 Tools : ITE (MIT), QTP, Selenium 1 and 2 (C# and Java), Robot
Framework, TechWiz, SOAP UI, Appium, MonkeyTalk

3. What is test automation?
• Test automation is not limited to QA.
• It is automating repeatable test cases using a tool
• Automation is not just Selenium
• Not all test cases can be automated.

4. How to start with automation?
 Do not just do with Selenium IDE.
 Selenium IDE is not an industry requirement.
 You should know C++, C#, Java or Python
 Know Object Oriented Concepts.
 Read about the tool you are studying
 Use a good tutorial site (Example guru99)
 Start automating some real scenarios

5. Scrum Process & Test Automation
Test
Automation
Scripting
Plan Test
Automation
Scripting
Plan Test
Automation
Execution Deliver Scripts

6. Plan Test Automation : Can all the
projects be automated ?
• “No”
• Short term projects
• Projects which has only less production life cycles
• Exploitary testing
• Different technology platforms.
• Skill issue

7. Plan Test Automation : Criteria go for
test automation
 Time
 Number of release cycles
 Skill
 Technology
 Manual test case count

8. Planning Test Automation :
Procedure
 Look at the technical skills of the team.
 Look at the QA budget.
 Select a right test automation tool.
 Select the scripting language.
 Select a good automation framework.

9. Data Driven Framework
 Data driven testing is an action through which a set of test input and/or
output values are read from data files
 QTP facilitates Data Driven testing
 Selenium does not given out of the box solution.
 Data driven testing using Selenium
 http://www.ontestautomation.com/data-driven-testing-in-selenium-webdriver-
using-excel/
 http://software-testing-tutorials-automation.blogspot.com/2014/07/create-data-
driven-framework-for.html

10. Keyword Driven Testing
 In keyword driven test framework, all the operations and instructions are
written in some external file like excel worksheet.

11. Keyword Driven Testing

12. Modularity Frameworks
 The test script modularity framework requires the creation of small,
independent scripts that represent modules, sections, and functions of the
application-under-test.

13. Hybrid Frameworks
 Keyword Driven + Data Driven
 Modularity + Data Driven

14. Automation Test Tools

15. Automation Framework
 Automation is beneficial if it is done in a framework.
 It is structure which promotes
 Configurable
 Reportability
 Scalability
 Extendibility
 Re-usability

16. Automation Test Framework Types
 Data Driven Test Frameworks
 Keyword Driven
 Modularity
 Hybrid Frameworks

17. Java Automation Framework

18. Priority of automating test cases
 Smoke Test
 Build Verification Test
 Regression test
 Positive (Happy path) scenarios
 Negative scenarios

19. Is functional testing only test
automation?
 No
 Unit testing
 Web services testing
 Security testing
 Mobile testing
 Performance testing ->No

20. Scrum Process & Test Automation
Test
Automation
Scripting
Plan Test
Automation
Scripting
Plan Test
Automation
Execution Deliver Scripts

21. Plan Test Automation Scripting :
Procedure
 In the sprint planning session plan for automation activity.
 For each QA activity if we can do automation include it in the User Story.
 Have acceptance criteria established for each user story.
 Better to have a separate user story for automation.

22. Scrum Process & Test Automation
Test
Automation
Scripting
Plan Test
Automation
Scripting
Plan Test
Automation
Execution Deliver Scripts

23. Automation Scripting : Procedure
 Start with creating a page objects and methods.
 Create the test scripts utilizing the page objects.
 Execute and see whether the script is working towards the test case
intended.
 Discuss the automation activity and its progress in daily scrum.
 Make sure it satisfies the acceptance criteria of the user story.
 Review the completed script.

24. Scrum Process & Test Automation
Test
Automation
Scripting
Plan Test
Automation
Scripting
Plan Test
Automation
Execution Deliver Scripts

25. Automation Script Execution:
Procedure
 Demo the script to the scrum team.
 Start execution of the script against the functionality.
 If we have a regression suite include it in the suite.
 Execute the regression suite.
 Share the results with the scrum team.
 Make the report available for the entire scrum team.

26. Scrum Process & Test Automation
Test
Automation
Scripting
Plan Test
Automation
Scripting
Plan Test
Automation
Execution Deliver Scripts

27. Deliver Scripts: Procedure
 If we have a regression suite include it in the suite.
 Deliver the script to the client – if there is an agreement
 Have the scripts included in the continues integration server.
 Make the report available for the entire scrum team.

28. Continues Integration

29. Hybrid automation frameworks

30. Breaking the Selenium boundaries

31. Selenium and ZED Attack Proxy

32. Selenium and WhiteStack
 C# Framework
 Automates with Windows functionality
 Can be used as a mix with Selenium and WhiteStack

33. Executing Selenium Scripts with QC
 Quality Center -> HP Proprietary test management tool
 Executes manual as well as QTP scripts
 OTA API provides lot of functionality
 Can integrate Selenium test execution in QC it self.

34. Selenium ~ QC Integration

35. Extending Automation Framework

36. Can we create a global one
framework???
 Yes
 With all the integration in API level

37. New Trends
 Extent Report – Advance Reporting Capability for Selenium Test
http://extentreports.relevantcodes.com/
https://www.youtube.com/watch?v=zSjwgjVl4P4
 Early Grey – IOS Automation Tool done by Google
http://venturebeat.com/2016/02/16/google-just-open-sourced-a-tool-for-
testing-ios-apps/
 Internet of Things (IOT)
 Sauce Labs - 2016 Test Automation Trends
Trenhttps://saucelabs.com/resources/webinars/test-automation-trends-for-
2016-and-beyond

38. Contact Me
 LinkedIn - https://lk.linkedin.com/in/kushana
 Email – lkkushan@yahoo.com
 Mobile - +94768026773

39. Thank you and Questions