Make sure you are comfortable with the following lessons:
Each team is unique and mabl is a flexible tool, which means each workspace is totally different.
When you understand your individual goals, requirements, and limitations, best practices guide you in applying mabl to your individualized process.
Confidence and communication lead to an efficient team that effectively carries out your automation strategy, which leads to better app coverage, and better app quality as a result! Woohoo!
The good news is, that’s what this lesson is for!
If you would like to get the best version of your workspace up and running as soon as possible, learn about the tools at your disposal and how others have best used them for organizing a workspace.
Once you understand mabl’s components and how they’re meant to be used, it’s time to take a step back and look at your short, medium, and long term goals.
Take your knowledge of mabl functionality, your automation strategy, and bring them together.
Always remember that nothing is meant to last forever -- your strategy will be in a constant state of change.
Iterating as time goes on is the way to achieving the best version of your automation.
The first best practice is to establish what you are going name the various components of mabl that make up your automation strategy.
Below we will cover a brief definition of the concept, and how you should think about using them in your automation.
The process of defining how you will go about naming the components of mabl will help inform how much functionality each will cover, and how each piece fits in your ‘automation puzzle’.
Plan: ‘Blog site’ -- general area of functionality.
Description: ‘Verify search functionality, that each type of blog and webinar can be searched, and that you end up on the correct page each time’ -- tells you what the tests within are supposed to validate.
Test: ‘Search’ -- the individual piece that the test is covering.
Label: ‘Search’ -- tells what functionality is included in this Plan.
Plans hold great power and great responsibility in mabl, they allow you to tailor mabl automation to your needs and goals.
We’ve compiled these core best practices here, but mablers are learning new exciting tips and tricks every day.
(Tune into our Friends of mabl Slack community to learn more -- reach out to email@example.com if you’re not already familiar.)
Establishing a “vision” of your automation strategy will help you identify the specifics of how it will come to fruition.
One key aspect of that is setting clear, actionable goals -- what do you want to accomplish, when, and why?
It’s tough, we know, but try your best to picture the perfect world of automation for your product and team.
Understand what aspects of your application and development environments that will impact automation at scale.
Understand how your team best collaborates with one another to achieve your goals
The scope of what you’re including in a given test, plan, or flow: What you automate first, which members on the team handle it, and how you approach that
Set actionable short-term goals and longer term stretch goals asking yourself and your team:
You can always course-correct as time goes on, but keep in mind that creating and organizing tests in a way that makes it easy to reorganize them if needed is important.
Things change -- management priorities, product development goals, team structures, tech stack -- evaluate your strategy quarterly at the least, make tweaks and changes as needed.
Keep track of what works and what doesn't -- use the comments section on the results page to leave a trail of your thoughts for your teammates.
Ask mabl - reach out to us about your strategy and we will give you our feedback.
What did we learn?