"Because it wasn’t just the instructions that were broken but the results as well." - This line got me! Seems like poor Josh was only expected to show that he is testing without actually testing anything 😅
The funny part is that all of what you wrote is so prevalent in the industry despite the abundance of useful tools. Ultimately, a lot of releases boil down to a legendary developer in the team saying everything looks fine, no matter what happens with the tests.
Also, thanks for the mention, Akos! Much appreciated.
> releases boil down to a legendary developer in the team saying everything looks fine, no matter what happens with the tests.
Perfectly put! I wonder how we got here and how to move away from this. 🤔 I worked in companies (including mine where we shipped a SaaS to a client) where this wasn't a thing. And the solution wasn't magic only tests and a reliable CI/CD pipeline.
"Because it wasn’t just the instructions that were broken but the results as well." - This line got me! Seems like poor Josh was only expected to show that he is testing without actually testing anything 😅
The funny part is that all of what you wrote is so prevalent in the industry despite the abundance of useful tools. Ultimately, a lot of releases boil down to a legendary developer in the team saying everything looks fine, no matter what happens with the tests.
Also, thanks for the mention, Akos! Much appreciated.
> releases boil down to a legendary developer in the team saying everything looks fine, no matter what happens with the tests.
Perfectly put! I wonder how we got here and how to move away from this. 🤔 I worked in companies (including mine where we shipped a SaaS to a client) where this wasn't a thing. And the solution wasn't magic only tests and a reliable CI/CD pipeline.