A happy new year to all the readers out there, and yet another new decade with the 20s, and wish you all be happy, peaceful and healthier than ever before to take up challenges that are waiting for you in this decade. I started blogging a decade back and when I reflect on this irregular hobby, I feel great about it as time passes away so fast and this blog is of 10 years old now:)
Okay, I know, you know about Pyramid; but what is "Test Pyramid" then :)
You would be getting to know about the Test Pyramid only if you are serious about the Test Automation and how much you can actually do the test coverage with your automated testing for the developed software.
If a developer is writing the tests by himself for the piece of code/software that he has built: those are the unit tests as part of the Unit Testing. And if he is thinking about doing some sort of automated tests for testing the integrations with other services, then that would be the integration testing or services testing. If he is looking for even broader testing scope of the overall system, then that would be the End to Eng System Integration Testing. Even after all these, sometimes, he has to manually test the system to how it is working and those are nothing but the Manual Testing.
With the above in mind, Let's see what is the Test Pyramid and how it would look like in the below picture, and keep in mind that the time spent and the costs involved are more from bottom to top, and the tip of the peak at the pyramid comes with the manual testing(that we have not discussed above while providing the context).
So, what is your take on how much we can cover from the test pyramid? It is completely up to you and your engineering team on what are your priorities and how you wanted to see the return for the time and cost that you have spent on all the layers of your test pyramid.
Reference articles:
https://martinfowler.com/articles/practical-test-pyramid.html#TheTestPyramid
Okay, I know, you know about Pyramid; but what is "Test Pyramid" then :)
You would be getting to know about the Test Pyramid only if you are serious about the Test Automation and how much you can actually do the test coverage with your automated testing for the developed software.
If a developer is writing the tests by himself for the piece of code/software that he has built: those are the unit tests as part of the Unit Testing. And if he is thinking about doing some sort of automated tests for testing the integrations with other services, then that would be the integration testing or services testing. If he is looking for even broader testing scope of the overall system, then that would be the End to Eng System Integration Testing. Even after all these, sometimes, he has to manually test the system to how it is working and those are nothing but the Manual Testing.
With the above in mind, Let's see what is the Test Pyramid and how it would look like in the below picture, and keep in mind that the time spent and the costs involved are more from bottom to top, and the tip of the peak at the pyramid comes with the manual testing(that we have not discussed above while providing the context).
So, what is your take on how much we can cover from the test pyramid? It is completely up to you and your engineering team on what are your priorities and how you wanted to see the return for the time and cost that you have spent on all the layers of your test pyramid.
Reference articles:
https://martinfowler.com/articles/practical-test-pyramid.html#TheTestPyramid
No comments:
Post a Comment