Traditional testing will die soon
Routine tasks in software development are automated through the Continuous Delivery and DevOps applications. Developers are taking on more and more responsibility. I wondered what would be the role of traditional testing and testers if you look a little ahead.
This question has been bothering 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% of unit tests, then 10% of integration tests, then 5% of system tests, and finally 5% of 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 through the GUI.
If you look at it a little deeper, it becomes possible only if the tester also has programming skills. By viewing the source code, he will be able to understand the role of unit testing in reducing risks with respect to end-to-end testing.
Now the teams are moving towards Acceptance Test Driven Development (ATDD). Where, again, plays the role of programming.
Whenever I hear the success story of the pyramid of testing, it always has a key success factor. It was either the programmers did all the testing, or the testers learned programming to test.
People get rid of handicraft as seen in LeSS queuing theory . In the process, they depart 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 opportunity for programming as a prerequisite for development. The difference will only be that the test engineers will put the testing in the forefront, and the development on the second. They will spend a good deal of their time programming in the form of writing scripts and code for automated scripts.
Test engineers are destined to become product experts, quality advisers and risk analysts.
In custody:
Gone are the days when manual testing was sufficient, 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 been bothering 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% of unit tests, then 10% of integration tests, then 5% of system tests, and finally 5% of 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 through the GUI.
If you look at it a little deeper, it becomes possible only if the tester also has programming skills. By viewing the source code, he will be able to understand the role of unit testing in reducing risks with respect to end-to-end testing.
Now the teams are moving towards Acceptance Test Driven Development (ATDD). Where, again, plays the role of programming.
Whenever I hear the success story of the pyramid of testing, it always has a key success factor. It was either the programmers did all the testing, or the testers learned programming to test.
People get rid of handicraft as seen in LeSS queuing theory . In the process, they depart 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 opportunity for programming as a prerequisite for development. The difference will only be that the test engineers will put the testing in the forefront, and the development on the second. They will spend a good deal of their time programming in the form of writing scripts and code for automated scripts.
Test engineers are destined to become product experts, quality advisers and risk analysts.
In custody:
Gone are the days when manual testing was sufficient, 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.
Source: https://habr.com/ru/post/266309/
All Articles