Atagg 2015 Test automation and effective continuous integration
0 likes415 views
This document discusses test automation and continuous integration in agile development. It notes that early automation, continuously integrated and testable software, and fast feedback help ensure faster delivery and optimize business value. The main challenges are short testing time frames per story and multiple deployments per sprint. Building a test suite with unit, service, and UI tests provides faster feedback and easier refactoring. Collaboration between testers and developers and striking a balance between test levels is important. Continuous integration runs automated tests on every code check-in to test feature integration within sprints. Best practices include early QA involvement, defining test scenarios during backlog refinement, estimating automation effort, and creating automation tests in parallel with development. Benefits include faster test cycles within
Atagg 2015 Test automation and effective continuous integration
- 1. Topic: Test Automation and effective Continuous Integration Presenter: Meghanandini K Tata Consultancy Services Confidential | Copyright © Agile Testing Alliance Global Gathering Brought To You By &
- 2. Testing in AgileTesting in Agile -- IntroductionIntroduction Key aspects QA in Agile • Building quality in • Early automation • Continuously Integrated and testable software • Fast feedback These will in turn help in ensuring a: • Faster delivery into production • Optimize value for business User InterfaceUser Interface ServiceService Unit Test Unit Test UIUI Confidential | Copyright © Agile Testing Alliance Global Gathering Main challenges • Short time frames to complete testing for a story • Multiple deployments within a sprint • System Integration • Interface dependencies • Testing Non functional requirements UIUI ServiceService Unit TestUnit Test
- 3. Building a Test SuiteBuilding a Test Suite GUI Tests Service level tests Exploratory Testing F a s t e r F e B r o a d e r Unit Tests • Faster feedback • Easier refactoring Tools: xUnit tests are used to test the application code. Eg: Junit tests are used to test the Java code. Service level tests • Faster feedback compared to tests at UI level • More stable compared to UI level • Application functionality can be tested rather than just the Confidential | Copyright © Agile Testing Alliance Global Gathering Service level tests Unit Tests/Component Tests e e d b a c k S c o p e • Application functionality can be tested rather than just the component Tools: FitNesse, Cucumber, Concordion, LISA UI level tests • Reduced number of tests • End user interface Tools: QTP, Selenium, Ranorex, Test Complete etc..
- 4. Tests at service levelTests at service level Wiki Page/Feature file Fixture/Step defination Application Code Confidential | Copyright © Agile Testing Alliance Global Gathering Collaboration with development team • Application code details • Feasibility analysis • Creation of fixtures • Continued support for service level automation • CI set up and integration of the test cases with CI tools Collaborate with the team • To ensure feature files are in line with user stories
- 5. Service/UIService/UI teststests –– Striking a balanceStriking a balance • A few points considered while segregating GUI Tests At least a few test cases covering End – 2 – End Functionality with Screen transitions Screen pop-up /Child window related cases Complex scenarios with multiple validations that need to be carried out on the UI Service level Tests Repeat scenarios with different inputs Confidential | Copyright © Agile Testing Alliance Global Gathering • A few challenges for segregation Repeat scenarios with different inputs Business Scenarios & validations Fault Injection & Negative Testing
- 6. App Server CIT Tool Code change/ Defect Fix Source Control (CVS/GIT) Publishes build results Notifies Stake holders if build Build (Ant, Maven)Code Commit Deploy the Build Pull the source and create the build Committing code frequently Continuous feedback mechanisms The reduction of The integration testing can be automated using CIT tool & Service level and UI level automation scripts. The integration testing can be automated using CIT tool & Service level and UI level automation scripts. 1 With every check-in of the code, the automated scripts get triggered and the CIT cases get executed. With every check-in of the code, the automated scripts get triggered and the CIT cases get executed. 2 The integration of the features within a sprint gets tested at this stage. The integration of the features within a sprint gets tested at this stage. 3 In-Sprint: Unit/Service /UI Level Testing integrated with Build Tools/Techniqu es: Jenkins Continuous IntegrationContinuous Integration Confidential | Copyright © Agile Testing Alliance Global Gathering Test Scripts Automated Test cases are created and uploaded in HP ALM Automatically triggered test scripts are executed in the targeted machines Selenium Test Management Tool Notifies Stake holders if build breaks Unit Test Cases Automat ion Framew ork The reduction of repetitive processes, freeing people to do more value work Auto Defect Notification Auto Defect Notification Frequency: Once after every build deployment /Daily Cucumber /FitNesse
- 7. Best Practices and BenefitsBest Practices and Benefits Best Practices: • Early QA involvement . Whole team including QA part of the Backlog Refinement sessions • Along with the acceptance criteria for a user story, high level test scenarios/examples should also defined and discussed as a part of backlog refinement session. This helps in elaborating the user story better. • As a part of Sprint planning , analysis should done for a user story wrt what tests need to run at service level and UI level • Effort estimation should include automation effort • Automation tests should be created parallel to application development Confidential | Copyright © Agile Testing Alliance Global Gathering • Automation tests should be created parallel to application development • Regular sync up calls to discuss automation • Continuous Integration Benefits: • Faster test cycle completion within the sprints
- 8. Thank You! Confidential | Copyright © Agile Testing Alliance Global Gathering