September 6, 2015 at 20:45Traditional testing will die soon
- Transfer
- Recovery mode
Routine tasks in software development are automated through Continuous Delivery and DevOps. Developers are taking more and more responsibility. I was wondering what the role of traditional testing and testers will be if you look a little ahead.
This question has bothered me since I looked at the testing pyramid, a concept invented by Mike Kohn in his book “Succeeding with Agile” . Its essence is that you should have 70-80% unit tests, then 10% integration tests, then 5% system tests and finally 5% GUI tests.
Percentage variation may vary. The whole point is that you should have a lot more low-level unit tests than high-level tests via the GUI.
If you look at it a little deeper, it becomes possible only if the tester also has programming skills. By looking at the source code, he will be able to understand the role of unit testing in lowering risks in relation to end-to-end (inextricable) testing.
Teams are now moving towards Acceptance Test Driven Development (ATDD). Where, again, programming plays a role.
Whenever I hear the success story of a test pyramid, there is always a key success factor in it. Either the programmers did all the testing, or the testers learned how to program in order to test.
People get rid of manual work as seen in the LeSS queuing theory. In the process, they move away from the role of the tester completely. This is becoming quite common in many startups these days.
In my opinion, moving forward, both roles will gain the ability to program as a prerequisite for development. The only difference will be that test engineers put testing first, and development second. They will spend a good portion of their time programming in the form of writing scripts and code for automated scripts.
Test engineers are destined to become product experts, quality advisors and risk analysts.
In custody:
Gone are the days when manual testing was enough, and the test cycle could take months. Testers need to become good programmers in order to move forward. Just being familiar with programming is no longer enough. They must be able to learn and develop the latest automation frameworks and work with scripting technologies to be competitive.
This question has bothered me since I looked at the testing pyramid, a concept invented by Mike Kohn in his book “Succeeding with Agile” . Its essence is that you should have 70-80% unit tests, then 10% integration tests, then 5% system tests and finally 5% GUI tests.
Percentage variation may vary. The whole point is that you should have a lot more low-level unit tests than high-level tests via the GUI.
If you look at it a little deeper, it becomes possible only if the tester also has programming skills. By looking at the source code, he will be able to understand the role of unit testing in lowering risks in relation to end-to-end (inextricable) testing.
Teams are now moving towards Acceptance Test Driven Development (ATDD). Where, again, programming plays a role.
Whenever I hear the success story of a test pyramid, there is always a key success factor in it. Either the programmers did all the testing, or the testers learned how to program in order to test.
People get rid of manual work as seen in the LeSS queuing theory. In the process, they move away from the role of the tester completely. This is becoming quite common in many startups these days.
In my opinion, moving forward, both roles will gain the ability to program as a prerequisite for development. The only difference will be that test engineers put testing first, and development second. They will spend a good portion of their time programming in the form of writing scripts and code for automated scripts.
Test engineers are destined to become product experts, quality advisors and risk analysts.
In custody:
Gone are the days when manual testing was enough, and the test cycle could take months. Testers need to become good programmers in order to move forward. Just being familiar with programming is no longer enough. They must be able to learn and develop the latest automation frameworks and work with scripting technologies to be competitive.
