5 steps for successful automation with Hiptest
- 2. Basics about Hiptest 5 steps for a successful automation Demo
- 3. Basics about Hiptest 5 steps for a successful automation Demo
- 5. Test management in the cloud
- 7. WHAT WE BELIEVE IN BDD Refactoring Continuous integration
- 9. Developers and testers working together Scenarios Action words Glue
- 10. Good design lead to good automation
- 11. Action words defines your DSL
- 12. Action words are implemented and stored with the application code
- 13. SAMPLE PRESENTATION Not a vanilla example Real life use-case About 200 tests and action words More than 600 CI builds
- 15. Basics about Hiptest 5 steps for a successful automation Demo
- 16. ROADMAP TO CI INTEGRATION 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 17. ROADMAP TO CI INTEGRATION 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 18. STRUCTURING PROJECT Scenarios contain only calls to action words
- 19. it "Organization update" do load_coffee_machine_project create_organization_named_name("Hiptest") check_organization_name_exists("Hiptest") check_organization_has_count_users("2") remove_user_name_from_organization("john") check_organization_has_count_users("1") add_user_email_to_the_organization("john@hiptest.net") check_organization_has_count_users("2") close_browsers end
- 20. STRUCTURING PROJECT Two type of action words: high-level: only call other action words
- 21. leaf: only contain action/result steps
- 22. ROADMAP TO CI INTEGRATION 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 23. USING HIPTEST-PUBLISHER AS A SERVICE
- 24. 0:58
- 25. USING COMMAND LINE > gem install hiptest-publisher > hiptest-publisher --token=123456 --language=javascript
- 26. GETTING A CONFIGURATION FILE
- 28. Do not forget to store that in Git/SVN
- 30. 0:51
- 33. ROADMAP TO CI INTEGRATION 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 34. IMPLEMENTING THE ACTION WORDS Well, that's your job ;)
- 36. And again, keep it in Git/SVN
- 37. ROADMAP TO CI INTEGRATION 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 38. CONFIGURING FOR CI Create a dedicated test run
- 39. ADD THE SCENARIO TO THE TEST RUN
- 40. ROADMAP TO CI INTEGRATION 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 41. UPDATE CI BUILD CONFIG Install hiptest-publisher on CI slave gem install hiptest-publisher
- 42. Fetch tests before execution hiptest-publisher --tests-only --test-run-id=3054 -c hiptest-publisher.config
- 43. Push results after execution hiptest-publisher -c hiptest-publisher.config -p results.xml
- 44. OBSERVE THE RESULTS IN THE TEST RUN
- 45. START AGAIN 1 - Create scenario 2 - Pull code 3 - Implement 4 - Add scenario to test run 5 - Let CI push results
- 46. Basics about Hiptest 5 steps for a successful automation Demo