Will testers disappear from the earth like dinosaurs? _ Agile Testing

With the rapid popularization and popularization of agile development, whether Agile software development still needs test Engineer's problem is mentioned by more and more people, the industry also holds two different views.
I think: with the further promotion of agile development, from the perspective of future trends, the role and status of testers are being marginalized, even in the future testers may disappear from the earth like dinosaurs.
(Don't spray, read the following, Ha ^_^)
Let's look at the ratio of testers to developers.
Microsoft's tester and developer ratio is typically 1:1, while Google's testers and developers are 1:10.
Why are the differences between the two companies so great? The main reason is that two companies have different definitions of the scope of the tester's work with the developer. At Microsoft, unit testing is done by testers (Sdet), equivalent to Sdet writing a set of code to test the product code written by a developer, with no less effort than a developer. And Google's unit testing and functional testing are generally done by developers themselves, testers mainly provide automated test tool support, mainly for performance testing, load testing, security testing, and these are automated tools to complete, naturally require less testers.
To see the development of software testing
The pioneer of software testing, Dr. Bill Hetzel (on behalf of the "the Complete Guide to Software testing") gave software a test of the definition: "Evaluate the characteristics or capabilities of a program and system and determine whether it achieves the desired results." Software testing is the purpose of any behavior. "His core point is that the test method is to try to verify that the software functions are executed in accordance with the prior design, with positive thinking, to verify the correctness of all the functional points of the software system." Software testing Industry regards this approach as the first method of software testing (testing is the validation of software that can work).
This approach was later challenged and challenged by Glenford J. Myers (on behalf of the Art of Software testing). Myers that testing should not be aimed at verifying that software is working, but rather that the software is faulty first, and then using reverse thinking to find as many errors as possible. He also argues from the perspective of human psychology, if the "validation software is working" as the purpose of testing, is very detrimental to testers to find software errors. He then proposed his definition of software testing in 1979: "Testing is the process of executing a program or system to detect errors." "is defined. Myers that a successful test must be a test to find bugs, or else it would be worthless, and give the three important points that are relevant to the test:
The test is to prove that the procedure is wrong, not to prove the procedure error-free;
A good test case is that it finds errors that have not been discovered so far;
A successful test is the detection of errors that have not been discovered so far;
This is the second method of software testing (testing is to verify that the software is faulty).
Myers proposed the concept of "testing for falsification", which overturned the mistaken understanding of "testing the software correctly", and pointed out the direction for the development of software testing, and the theory and method of software testing had been developed greatly after that.
......

Turn from: http://www.51testing.com/html/61/n-875961.html