Test to Break Attitude - Poor Concept

If you ask question that what makes a good software tester then most people reply that a good tester should have "Test to Break Attitude". Ex: “softwareqatest” website has mentioned "Test to Break Attitude" as first quality that software test engineer should have.

My point of view is different. For me, it is not the responsibility of software tester to break anything and neither does he break. It is the software developer that has left broken things for software testers to find it. If a tester finds a bug then it does not mean that he has broken anything, it was already broken. A tester just find outs the points and areas which are already broken and then digs deep in it.

Detecting a breakage is not a job all done for a tester? It’s a job half done and maybe it’s just the beginning. Further responsibilities of tester are the find out the conditions under which this break occur and under which does it not occur? And to figure out the exact and simple steps to reproduce this break, which are supported by images, presentations or clips etc. All this will help developers and other stake holders to reproduce the break at their end. Other questions that tester have to find out are: Scope: all areas effected by the break; after finding this break do we need to re-execute some of other test cases or what test cases to re-execute after getting the fix for break; what risks will arise due to break; was it possible to detect this break earlier, if yes then what factors avoided its earlier detection; should the testing process or strategy be modified to detect breaks earlier?

As a software tester, your job may include planning, conducting, and analyzing results in controlled conditions, which are designed to find any kind of breakages.
However, if you like to break then you may try to take up any demolition job.