Online ONLY - Testing Ask Me Anything - Whole Team Testing - Lisa Crispin
Description changed:
ONLINE ONLY
We have a new Ask Me Anything live webinar on Tuesday 9th April at 8 pm UK time. This time we're talking about Whole Team Testing.
mabl are sponsoring this AMA. mabl is the most reliable codeless UI testing service available, enabling continuous testing with an auto-healing automation framework and maintenance-free test infrastructure. Using proprietary machine learning models to automatically identify application issues, including javascript errors, visual regressions, broken links, increased latency, and more, mabl brings traditional UI testing to the modern age.
Find out more about mabl.
Our host Vernon Richards will be joined by Lisa Crispin to answer all your questions.
One of the cornerstones of agile development is the whole-team focus on building quality into the software. On high-performing teams, everyone takes responsibility for testing, regardless of their official role or self-identified specialities. The DevOps movement has built on this, putting even more focus on delivery teams collaborating with Operations and other teams to build testable infrastructure and enabling continuous delivery.
In this AMA, Lisa will answer questions about how whole-team testing works in practice. If you’re wondering how in the world you get non-testers interested in doing work that they’ve purposely avoided in the past, or interested in newer practices that involve more of the delivery team, such as pair and mob testing, please join in with your questions.
Once you've registered you could ask Lisa any question you might have, here are a few more examples:
When I try to get developers to do testing, they say it’s not their job. What can I do about that?
Other people on my cross-functional team say they want to learn how to do testing. How can I help them learn skills? What skills should I start with?
I’m on a separate test automation team. It’s difficult to automate tests for (name some reason, such as, there are no unique identifiers in the UI). How can I get developers to make the code more testable?
We have a new Ask Me Anything live webinar on Tuesday 9th April at 8 pm UK time. This time we're talking about Whole Team Testing.
mabl are sponsoring this AMA. mabl is the most reliable codeless UI testing service available, enabling continuous testing with an auto-healing automation framework and maintenance-free test infrastructure. Using proprietary machine learning models to automatically identify application issues, including javascript errors, visual regressions, broken links, increased latency, and more, mabl brings traditional UI testing to the modern age.
Find out more about mabl.
Our host Vernon Richards will be joined by Lisa Crispin to answer all your questions.
One of the cornerstones of agile development is the whole-team focus on building quality into the software. On high-performing teams, everyone takes responsibility for testing, regardless of their official role or self-identified specialities. The DevOps movement has built on this, putting even more focus on delivery teams collaborating with Operations and other teams to build testable infrastructure and enabling continuous delivery.
In this AMA, Lisa will answer questions about how whole-team testing works in practice. If you’re wondering how in the world you get non-testers interested in doing work that they’ve purposely avoided in the past, or interested in newer practices that involve more of the delivery team, such as pair and mob testing, please join in with your questions.
Once you've registered you could ask Lisa any question you might have, here are a few more examples:
When I try to get developers to do testing, they say it’s not their job. What can I do about that?
Other people on my cross-functional team say they want to learn how to do testing. How can I help them learn skills? What skills should I start with?
I’m on a separate test automation team. It’s difficult to automate tests for (name some reason, such as, there are no unique identifiers in the UI). How can I get developers to make the code more testable?
