Skip to main content

Good Tester and Bad Tester – Difference with Example

So many times we are heard about Good tester’s means what are the qualities of a good tester but we never know about bad testers. That is why I am writing this article so that people who are comes under the category of bad testers can know what they are and if they want to become good tester than how they convert himself in to the category of good tester to make the application reliable and bug free and how they increase the product and project quality.

Difference between Bad Tester and Good Tester
             Bad Tester
                Good Tester       
1
Bad Testers are working in a company not to learn new things but just for time pass and whatever money they are getting from companies they are satisfied from it.
Good testers are working in a company to learn new things and by learning they improve his and her growth and as well as companies growth also.
2
A bad tester does not notice little things mean they ignore little things.
Good testers even notice little or small things that others miss or ignore.
3
Bad testers do not find the root cause of the bug.
Apart from the bug good testers also find out the root cause of the bug too.
4
Bad testers always test the application with given requirements mean whatever written in requirements these testers only tests that part of application.
Good testers also test the application with given requirements but apart from requirements they also tests that part of application which is not mentioned in requirements so that they increase the product or you can say project quality.
5
Example of bad testers: Suppose they test the application and they saw that user is able to login from signup functionality in reality they knew that it is wrong means it is a bug but they never report it to the development team because it is not mentioned in the requirements that they have to check that parts also so they ignore this bug.
Example of Good testers: Suppose they test the application and they saw that apart from sign in functionality user is also able to login from signup functionality they knew it is bug and they also know that it is not mentioned in requirements that we have to check this functionality also but still they report that bugs to the development team because they feel that it is our duty to make the application bug free and user friendly.
6
Bad testers always test the application by keeping his and her point in mind not the end users point.
Good testers always test the application by keeping end user in mind.

Now your turn
Hope you got the point and this post also helps you to compare yourself whether you are comes under the category of good tester or bad tester.

Comments

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...
31 comments
Read more

What Is Functional Testing Explain It with Example?

Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application. Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not. Functional testing  is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations. Functional and Non Functional Test Cases Functional test cases target business goals and non functional test cases target performance, resource...
29 comments
Read more