Using robots to automate your functional testing

Transcript

1. Automated Functional Testing
2. Manual regression testing sucks
3. Manual regression testing across multiple browsers sucks more
4. Automation is complicated
5. Real automation requires coding time analysis testing infrastructure
6. Describe how software should behave in plain business-specific language
7. Behaviour Driven Development
8. Part of agile methodology
9. Feature: User account authentication Scenario: Login with valid password Given I am on the “login” page
 When I enter “bobby” in the “username” field
 And I enter “loveslamp” in the “password” field
 And I click the “Login” button
 Then I should be redirected to the “my-account” page
10. A feature defines a piece of functionality under test
11. Use cases are described by a scenario
12. Steps define context, actions, and assertions
13. Feature: User account authentication Scenario: Login with valid password Given I am on the “login” page
 When I enter “bobby” in the “username” field
 And I enter “loveslamp” in the “password” field
 And I click the “Login” button
 Then I should be redirected to the “my-account” page Context Actions Assertion
14. Define your tests with clear and concise steps that anyone can understand
16. Batteries are not included
17. You have to write code behind each unique step
18. Behat + Selenium + The Cloud
19. Behaviour Driven Development Manifesto Testing
20. Code behind steps should be defined once
21. Steps can describe multiple actions
22. And I enter my card details Select Card Type Enter Card Number Enter Expiry Date Enter CVV }
23. Anyone should be able to write a feature file or scenario
24. Developers and Testers work together to build up a test suite
25. Always test and validate your scenarios