mabl strategy - organizing your journeys
•Download as PPTX, PDF•
1 like•160 views
How do you organize your software tests? We offer five strategies for organizing your journeys to keep them aligned with your company's structure.
Recommended
More Related Content
Similar to mabl strategy - organizing your journeys
Similar to mabl strategy - organizing your journeys (20)
Recently uploaded
Recently uploaded (20)
mabl strategy - organizing your journeys
- 2. about mabl ■ uses machine intelligence to help engineers find and fix bugs faster ■ install chrome extension to train journeys (tests) in your browser ■ journeys run in the cloud in parallel. no infrastructure to manage ■ auto-healing saves time spent on fixing broken tests ■ test on multiple browsers: chrome, firefox, and IE 11 ■ new features shipped all the time. 2
- 3. agenda for today’s webinar overview ■ mabl trainer ■ plans ■ journeys ■ mabl link ■ ML - insights 3 functional testing ■ end-to-end journeys ■ smoke tests ■ regression suites get organized ■ align by team ■ user roles ■ feature sets ■ navigation ■ JIRA project 5
- 4. mabl has two parts to consider mabl trainer (chrome extension) ■ install for chrome browser ■ play / record format ■ click through steps to record ■ create assertions, variables, javascript steps and reusable flows 4 mabl in the cloud (execution engine) ■ runs Journeys in parallel ■ no infrastructure to maintain ■ replays in multiple browsers ■ test against any site it can reach
- 5. resources ■ help.mabl.com ■ live chat support ■ slack.mabl.com community 5
- 6. configuring plans ■ name ■ description ■ labels ■ browsers ■ environments 6
- 7. configuring journeys in plans ■ select the journey ■ add any parameters ■ add even more journeys 7
- 8. configuring rest of the plan ■ journeys ■ triggers ■ auto-login ■ credentials ■ save 8
- 9. Integrations ■ Slack ■ JIRA ■ CI / CD tools ▲ Trigger tests via Jenkins, Bamboo, Codeship, CircleCI and others 9
- 10. secure testing with mabl link 10 establish a secure tunnel between your private network and mabl's test infrastructure without opening up your firewall.
- 13. two ways to train in chrome 13 incognito mode ■ don’t have to clear cookies or logout ■ most closely replicates mabl in the cloud ■ no upload / download steps yet normal mode ■ logout first unless using auto-login ■ watch out for cookies ■ mabl captures form auto-fills
- 14. 3 types of journeys ■ end-to-end tests ■ smoke tests ■ regression tests 14
- 15. 3 types of journeys ■ end-to-end tests ■ smoke tests ■ regression tests 15 ■ perform a whole series of actions ■ assert that they completed successfully ■ Clean up / tear down
- 16. 3 types of journeys ■ end-to-end tests ■ smoke tests ■ regression tests 16 ■ fast tests to verify critical actions ■ performed in parallel ■ can be used to block or pass deploys from shipping
- 17. 3 types of journeys ■ end-to-end tests ■ smoke tests ■ regression tests 17 ■ all of them ■ very specific features tested ■ use flows for efficiency
- 18. mabl’s own plans 18 ■ use labels ■ trigger on deployments ■ run regularly
- 19. 19 ■ production monitoring ■ deployment runs them ■ own the results mabl’s own plans
- 21. organize by team 21 ■ group journeys by responsible teams ■ easy to monitor and assert ownership ■ own the results
- 22. organize by user roles 22
- 23. organize by user roles 23
- 24. organize by user roles 24
- 25. ■ creation ■ analytics ■ billing ■ messaging ■ performance 25 organize by feature sets
- 27. takeaways from today’s webinar organize ■ what makes sense for your organization ■ integrate with Jenkins to run the right plans 27 group journeys ■ how they will run ■ when they will run ■ which ones will go together 5 follow up ■ get in touch with us at mabl for additional help
Editor's Notes
- Getting data in and out of mabl. Here are some of the integrations we offer. I’ll talk more about using the CI / CD integrations a little later.
- Spend time here, 1 full minute.
- Move through these slides
- Talk about flows. Use for logging in, long flows of creating elements, and tear down / clean-up steps at the end.
- Spend time here. Talk about parallel running, new container. Use Jenkins or Bamboo native integration. Deployment API. Pre-execution call and Post-execution call to record results. We use a post execution call to stackdriver
- Advice on how to use labels and when to run. Labels: Smoke-test, end-to-end, Prod, Staging, Matthew, other names, mabl-link agent,
- We have this suite of prod monitoring tests. We run on deploys. Developer who works on the features maintains the tests.
- Fun name generator. Thanks Mike Cohn from Mountain goat software.
- These are some of my favorite team names, I found them on reddit. Not our actual team names.
- Think about the types of users you have in your system. How can you make sure that the functions are properly limited and dont’ get broken.