The pipeline definitely can become bulky when we keep adding all the test to the pipeline without retrospecting the goal of adding those tests or time taken to run those tests on the pipeline.
We as a team took step by step approach to add each test and monitor the failures and feedback loops. And it also depends on the size of changes being made, minimizing the size of the change is also very important.
Shifting left should help and empower the team with faster feedbacks, allowing testers to focus more on exploratory testing and helping the team to shift right.
I understand this question in two different contexts.
If you are talking about the context of pre-deploy pipeline tests that I mentioned during my talk then my answer would be
As we were new to this concept we were experimenting and learning so we decided to have some
tests on pre-deploy pipeline and some tests(static code analysis and unit tests) on the post-deploy
pipeline(integration, API, consumer-driven contract tests, end to end test)
If you are talking about post pipeline tests then yea thereās still lot more testing needs to be done like exploratory and monitoring.
I hope I didnāt make assumptions here for what you were trying to ask
Lucky enough there was no resistance in implementing the pipeline and adapting the new way of working from any of the team members because we all were interested in this. But there was more resistance for making testers involved in decision making, deciding on process,visibility of goal and collaboration.