Developers should always be proactive to testing. Remember that the purpose of testing is to ensure that the end goal is achieved. If a bug is found, don't fret. Take it as something positive: the earlier it's found, the sooner you can get it fixed. You can then assess on which features to add to improve the application. The problem only occurs when unknown errors surface in the future due to the bugs that were not found. The stronger your test plan and the more accurate it is, the more reliable your application will be. And that's one great reason to bring on the hackers (the authorized ones---a.k.a. the Penetration Testers), or your QA team.
I created a very simple System Test Plan Reference Diagram which can be used as a quick reference guide tool when drafting system tests. Save the Figure 2.0 image below or download it from here. (^^,)
Figure 1.0
I created a very simple System Test Plan Reference Diagram which can be used as a quick reference guide tool when drafting system tests. Save the Figure 2.0 image below or download it from here. (^^,)
Figure 1.0
more info here
Hope you'll find it useful. (^__^)