Defect driven Test automation: Test strategy in place to consider candidates for test automation primarily as earlier found and fixed defects in the application. With the thought process that it will give the most bang for the bucks as regression test strategy.
Question: When teams build tests based on reported defects many times the strategy is to build a test for every defect. The concept is when the team picks up a defect, they write a test for the expected behavior and see that fail. Next they write a fix that causes the test to pass. This approach will definitely increase test coverage and will yield an automated test suite that can be used. However how do you know that you have made the best investment in writing automated tests?
My view:In my view, it is an good idea for legacy applications which are stable and having large defects data from past but not as good for new application under development. Do you agree with my viewpoint?