Agile Test Automation
•Download as PPTX, PDF•
0 likes•1,157 views
This document summarizes an Agile Test Automation session which covered: - The agenda included an introduction to Agile testing process and tools, a demonstration, and Q&A - Agile values like communication and feedback affect testing by making the whole team responsible for quality using test-driven development and continuous integration - Test automation tools discussed included test harnesses like JUnit and Selenium, as well as functional testing tools like Cucumber and Concordion
Report
Share
Agile Test Automation
- 1. Session 902Agile Test AutomationWerner Keil, Director, Creative Arts & Technologies
- 3. Process
- 4. Tools
- 6. IntroMain Trend:Move away from Waterfall to Lean and Agile
- 7. IntroHow does Agile affectSoftware Testing?
- 8. Agile Values and PrinciplesValuesCommunication
- 9. Simplicity
- 10. Feedback
- 11. Courage
- 12. Respect
- 13. Transparency
- 14. TrustAgile Values and PrinciplesPrinciplesEliminate Waste
- 15. Build Quality In
- 16. Create Knowledge
- 17. Deliver Fast
- 18. Respect People
- 19. Optimize the WholeAgile ManifestoIn February 2001, 17 software developers met at a ski resort in Snowbird, Utah, to discuss lightweight development methods. They published the "Manifesto for Agile Software Development"© agilemanifesto.org
- 21. AnotherSalt Lake© Gujarat Tourism Bureau
- 22. RolesRoles in an Agile teamProduct Owner
- 23. Domain Expert
- 24. Developer
- 25. TesterRolesTester’s role in a new Agile world
- 26. ResponsibilitiesRequirements Management and Analysis
- 27. Helping Business with Requirements
- 28. Helping Developers with Test Data preparation and Unit Testing
- 29. Test Execution
- 30. Test Automation
- 31. Exploratory TestingResponsibilitiesNo more QualityPolice!
- 32. ResponsibilitiesBuild Quality inWhole team responsible for quality
- 33. Not just Test Engineers
- 34. TDD
- 35. Tester as Helper
- 36. Aim for zero defect rate
- 37. Though some may call that insane ;-)Technical PracticesIterative process
- 39. RefactoringProcessThe Four D’s of Agile DevelopmentDiscuss
- 40. Decide
- 41. Develop
- 44. TestNG
- 46. SoapUI
- 47. Arquillian
- 49. FitNesse
- 50. Cucumber
- 51. easyB
- 52. Eclipse Jubula
- 53. etc.Selenium 2Selection CriteriaSelf Contained
- 54. Browser Support
- 55. Scripting in JavaSelenium 2This won‘t workat least underWindows
- 56. ConcordionNo acceptance tests written like this...
- 57. ConcordionWrite them like this instead...
- 58. ConcordionClear tests lead to clear fixture code
- 59. ConcordionActive SpecificationPlain English requirements
- 60. Acceptance tests in form of real life examples
- 61. Can be executed against SUTFrameworkPages
- 63. FrameworkPersonasFictional – but realistic – character sketches based on a break-down of the target audience into groups of users that exhibit common characteristics. They are created using knowledge drawn from previous research, for example user groups and surveys that have been carried out with actual users.
- 65. DemoTime for a
- 66. Thank you for attending this session.Please fill out an evaluation form and place it in the box located at the back of the room.