Agile Test Automation
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Agile Test Automation

on

  • 2,163 views

Agile Test Automation with Selenium2 and Concordion

Agile Test Automation with Selenium2 and Concordion

Statistics

Views

Total Views
2,163
Views on SlideShare
2,158
Embed Views
5

Actions

Likes
0
Downloads
17
Comments
0

5 Embeds 5

https://p.yammer.com 1
http://trunk.ly 1
http://paper.li 1
http://www.docseek.net 1
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile Test Automation Presentation Transcript

  • 1. Session 902
    Agile Test Automation
    Werner Keil, Director, Creative Arts & Technologies
  • 2. Agenda
    25 minutes
    • Intro
    • 3. Process
    • 4. Tools
    • 5. Framework
    30 minutes
    Demo
    Q&A
  • 6. Intro
    Main Trend:
    Move away from Waterfall to Lean and Agile
  • 7. Intro
    How does Agile affect
    Software Testing?
  • 8. Agile Values and Principles
    Values
    • Communication
    • 9. Simplicity
    • 10. Feedback
    • 11. Courage
    • 12. Respect
    • 13. Transparency
    • 14. Trust
  • Agile Values and Principles
    Principles
    • Eliminate Waste
    • 15. Build Quality In
    • 16. Create Knowledge
    • 17. Deliver Fast
    • 18. Respect People
    • 19. Optimize the Whole
  • Agile Manifesto
    In 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
  • 20. A
    Salt Lake
    © solarnavigator.net
  • 21. Another
    Salt Lake
    © Gujarat Tourism Bureau
  • 22. Roles
    Roles in an Agile team
    • Product Owner
    • 23. Domain Expert
    • 24. Developer
    • 25. Tester
  • Roles
    Tester’s role in a new Agile world
  • 26. Responsibilities
    • Requirements 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 Testing
  • Responsibilities
    No more QualityPolice!
  • 32. Responsibilities
    Build Quality in
    • Whole 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 Practices
    • Iterative process
    • 38. Continuous integration
    • 39. Refactoring
  • Process
    The Four D’s of Agile Development
    • Discuss
    • 40. Decide
    • 41. Develop
    • 42. Demonstrate
  • Process
  • 43. Tools
    Test Harness
    • JUnit
    • 44. TestNG
    • 45. etc.
  • Tools
    Driver
    • Selenium | WebDriver
    • 46. SoapUI
    • 47. Arquillian
    • 48. etc.
  • Tools
    Functional
    • Concordion
    • 49. FitNesse
    • 50. Cucumber
    • 51. easyB
    • 52. Eclipse Jubula
    • 53. etc.
  • Selenium 2
    Selection Criteria
    • Self Contained
    • 54. Browser Support
    • 55. Scripting in Java
  • Selenium 2
    This won‘t work
    at least
    under
    Windows
  • 56. Concordion
    No acceptance tests written like this...
  • 57. Concordion
    Write them like this instead...
  • 58. Concordion
    Clear tests lead to clear fixture code
  • 59. Concordion
    Active Specification
    • Plain English requirements
    • 60. Acceptance tests in form of real life examples
    • 61. Can be executed against SUT
  • Framework
    Pages
  • 62. Framework
    Personas?
  • 63. Framework
    Personas
    Fictional – 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.
  • 64. Framework
    Testing
    Cloud
  • 65. Demo
    Time 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.