In your opinion any difference between Shift-Left and Expand-Left?

🙋 Questions
,
1

There is a lot of talking about Shift-Left strategies and discussions about what is mean. And I feel many mix up Shift-Left with Exand-Left.
Would be intressting to hear if my thought are what others thoughts as well.

For me:
Expand-Left - that is our quest as a tester be more involved ealier in the whole process, even during the idea phase and part of the architect discussions. The earlier test gets involved the earlier testability of the idea can be brought into the discussion. And also testablity of the architect descision that is on the table. That way thing that is choosen to be developed have passed some sort of test gateway. And test should be involved in all stage of the whole system lifecycle.
That for me is the Expand-Left part that is crucial.

Shift-Left - that is making the V-model become a I-model. Which means testing should be moved as close to the development team as possible, even the end-user of the system should be close to the team to do acceptance test. And provide information about variance of input parameters and what sort of outcome for the different setups of parameters. That way the whole system is unit, system, integration and acceptance tested at the same time. Also with Shift-Left approach test cases should always be discussed if that could be done as a unit test.
That is for me Shift-Left appraoch.

What is your opinion?
Is there a difference in Expand-Left and Shift-Left or is it the same?

3 Likes
2

According to some definitions, including the ones you provided, there is a difference - one is broader than the other, but fundamentally, they pursue the same goals and are based on the same main ideas. They partly overlap, and in practice, the distinctions may blur because people may mix some stuff while shifting left. Your question seems more like a matter of terminology, which might be different across different sources. I wouldn’t focus on searching for differences in these terms but rather concentrate on the main ideas and benefits, and how they can be implemented, etc :wink:

1 Like
3

I perceive Shi(f)t-Left for often being about removing testers from teams and companies. Automation should be a sufficient replacements for people who are looking for problems.
It some people lable the same content with “everyone owns quality”.

I’m in a tester in a Scrum team and participate in all meetings. Refinement, planning, daily, retro, review. I’m looking for problems in all parts. Processes, designs and specifications, code, configuration, executable, etc.
Some would call that “expand left”.