What are the best things you've seen implemented to encourage shifting left, to improve the process in overall quality?
What advice would you give to someone who is keen to engage other team members/disciplines but faces a culture where that is discouraged?
Where do you see exploratory testing within the continuous testing cycle?
What's your opinion on the strengths and weaknesses of testing in production versus shifting left? Or how do you see the two working together?
How would you describe 'Shift Right' best practices and pro's and con's?
Is there an over-obsession with shift left? And how might the idea of shift right be sold to the team so it's not an either/or situation?
Have you come across many teams who choose to only apply shift left or right testing techniques? And what are the outcomes by only applying half of the process?
What kind of review techniques are common in shift left or shift right?
Who are the best people to be following for help and to learn about shifting left or right?
What is a practical example of a tester specifically 'shifting right'?
What is the recommendation from you to shift left or right where the user requirements keep on changing before the production release?
How best do you motivate teams to shift left or shift right?
How shifting right fits into an agile project where things move at a fast pace?
Is test automation the only way to shift left or right?
Why should we be shifting left or right?
What tools can you recommend for capturing user journeys in production?
ChapteWhat is the best success story that you know of where shift left or right was done awesomely with great results?r Title
Software Testing is frequently considered the bottleneck in the traditional development process. When you see a graph of the time teams spend in testing, it looks like a bell curve, with the highest point right at the end, when you'd rather release software than spend more time testing it.
The Shift Left/Shift Right movements, are much more than mere buzzwords, seek to "smooth out" the big testing hump that blocks releases, moving testing resources earlier and later in the SDLC. This gives you a more stable, predictable, and confident release process, and removes a lot of the mystery and uncertainty from the process of delivering value to your customers.
This AMA was kindly sponsored by Sauce Labs
.Sauce Labs lets you automate your web and mobile app tests on a variety of different browsers, operating systems and devices, all on the world’s largest continuous testing cloud. It's a snap to make sure your code runs smoothly everywhere. Try the 14 day free trial!
Senior Director of Technology Strategy
Senior Director of Technology Strategy at Sauce Labs, where he uses experience from 20+ years in test to manage strategic technical alliances. Within the CTO Office, Marcus works with partners to build robust, customer-centric solutions around test automation, release management, and the entire SDLC. He started using Selenium/WebDriver in 2007, contributes to the Selenium project, and chairs the Selenium Conference Organizing Committee.