All IT Courses 50% Off
QA Tutorials

10 Myths of Software Testing

The following Myths of software Testing are:

Myth 1-Testing is very expensive

Reality- Sometimes it is believed and said that, pay less for the testing during the software development and we should pay more for the maintenance or may be correction later. Early testing can save both time and cost in many aspects. However reducing the cost without testing may result in improper design of a software application rendering the product useless.

Myth 2-Testing is not Time consuming

Reality- During the SDLC phases, testing is a time-consuming process but worth it. However diagnosing and fixing the errors recognising during the proper testing is a time-consuming but productive activity.

Myth 3-Fully developed products are tested

Reality- There is no doubt that testing depends on the source code but reviewing requirements and developing test cases is independent from the developed code. However iterative or incremental approach as a development life cycle model may reduce the dependency of testing on the fully developed software. Testing the software at early stages saves time and cost of project. 

Myth 4-Complete Testing is possible

RealityIt is an issue when the client or tester thinks that complete testing is possible. It is possible that each one the paths are tested by the team but occurrence of complete testing isn’t possible. There might be some scenarios that are not executed by the test team or the client during the software development life cycle and may be executed once the projects have been deployed. The software cannot be tested with all possible values of input and output in practical because of the time constraint. Hence we use standard techniques and methods for testing. 

Myth 5-Tested software is Bug-Free

RealityThis is common myth that clients, project managers, and the management team believes. No one can claim with absolute certainty that a software application is 100% bug free even if a tester with superb testing skills has tested the application. The software testing shows the presence of the defects and not their absence. 

Myth 6-Missed defects are due to Testers

RealityIt is not the right approach to blame testers for bugs that remain in the application even after testing has been performed. This myth relates to time, cost and requirements for changing the constraints. The test strategy can also end in bugs being missed by the testing team. The testers are most of the times considered as bottlenecks. But the management and team leaders have to take the appropriate initiative to appreciate the effort of testers. 

Myth 7- Only the testers are responsible for the quality of product

Reality- it is very common misinterpretation that only testers or the testing team should be responsible for the quality of the product. Testers responsibilities include the identification of bugs to the stake holders and then it is their decision whether it will fix the bug or may release the software. Releasing the software at the time puts more pressure on the testers as they are blamed for any error.

Myth 8- Testers Automation should be used wherever possible to reduce Time.

Reality- It is true that Test automation reduces the testing Time, but it is not possible to start test Automation at any time during software Development. Test Automation will be started when the software has been manually tested and is constant to some extent. Test automation can never be used if requirements will keep changing.

Myth 9-Anyone can Test software Application

Reality-People outside IT industry think and even believe that anyone can test software and testing is not a creative job. However testers know alright that this is  often a myth. Thinking alternative scenarios, try to crash software with intent to know potential bugs is not possible for the person who developed it.

Myth 10- Finding bugs is the task of testing team alone

Reality- Finding the bugs in software is a task of the testers but at the same time there are domain experts of the particular software. Developers are not only responsible for the specific component or area that is assigned to them for development, but also test them.

Facebook Comments

9 Comments

  1. 10 Myths of Software Testing:
    1. Testing is very expensive
    2. Testing is not Time consuming
    3. Fully developed products are tested
    4. Complete Testing is possible
    5. Tested software is Bug-Free
    6. Missed defects are due to Testers
    7. Only the testers are responsible for the quality of product
    8. Testers Automation should be used wherever possible to reduce Time.
    9. Anyone can Test software Application
    10. Finding bugs is the task of testing team alone.

  2. Myths of software Testing are:
    Myth 1-Testing is very expensive:
    Reality- Sometimes it is believed and said that, pay less for the testing during the software development and we should pay more for the maintenance or may be correction later. Early testing can save both time and cost in many aspects. However reducing the cost without testing may result in improper design of a software application rendering the product useless.
    Myth 2-Testing is not Time consuming:
    Reality- During the SDLC phases, testing is a time-consuming process but worth it. However diagnosing and fixing the errors recognising during the proper testing is a time-consuming but productive activity
    Myth 3-Fully developed products are tested
    .Reality- There is no doubt that testing depends on the source code but reviewing requirements and developing test cases is independent from the developed code. However iterative or incremental approach as a development life cycle model may reduce the dependency of testing on the fully developed software. Testing the software at early stages saves time and cost of project.
    Myth 4-Complete Testing is possible
    Reality– It is an issue when the client or tester thinks that complete testing is possible. It is possible that each one the paths are tested by the team but occurrence of complete testing isn’t possible. There might be some scenarios that are not executed by the test team or the client during the software development life cycle and may be executed once the projects have been deployed. The software cannot be tested with all possible values of input and output in practical because of the time constraint. Hence we use standard techniques and methods for testing.
    Myth 5-Tested software is Bug-Free:
    Reality– This is common myth that clients, project managers, and the management team believes. No one can claim with absolute certainty that a software application is 100% bug free even if a tester with superb testing skills has tested the application. The software testing shows the presence of the defects and not their absence.
    Myth 6-Missed defects are due to Testers:
    Reality– It is not the right approach to blame testers for bugs that remain in the application even after testing has been performed. This myth relates to time, cost and requirements for changing the constraints. The test strategy can also end in bugs being missed by the testing team. The testers are most of the times considered as bottlenecks. But the management and team leaders have to take the appropriate initiative to appreciate the effort of testers.
    Myth 7- Only the testers are responsible for the quality of product:
    Reality- it is very common misinterpretation that only testers or the testing team should be responsible for the quality of the product. Testers responsibilities include the identification of bugs to the stake holders and then it is their decision whether it will fix the bug or may release the software. Releasing the software at the time puts more pressure on the testers as they are blamed for any error.
    Myth 8- Testers Automation should be used wherever possible to reduce Time:
    Reality- It is true that Test automation reduces the testing Time, but it is not possible to start test Automation at any time during software Development. Test Automation will be started when the software has been manually tested and is constant to some extent. Test automation can never be used if requirements will keep changing.
    Myth 9-Anyone can Test software Application:
    Reality-People outside IT industry think and even believe that anyone can test software and testing is not a creative job. However testers know alright that this is often a myth. Thinking alternative scenarios, try to crash software with intent to know potential bugs is not possible for the person who developed it.
    Myth 10- Finding bugs is the task of testing team alone:
    Reality- Finding the bugs in software is a task of the testers but at the same time there are domain experts of the particular software. Developers are not only responsible for the specific component or area that is assigned to them for development, but also test them.

  3. Myth 1-Testing is very expensive
    Myth 2-Testing is not Time consuming
    Myth 3-Fully developed products are tested
    Myth 4-Complete Testing is possible
    Myth 5-Tested software is Bug-Free
    Myth 6-Missed defects are due to Testers
    Myth 7- Only the testers are responsible for the quality of product
    Myth 8- Testers Automation should be used wherever possible to reduce Time.
    Myth 9-Anyone can Test software Application
    Myth 10- Finding bugs is the task of testing team alone

  4. 10 Myths of Software Testing
    Myth 1-Testing is very expensive
    Reality: Testing saves time and cost. Without testing the software will not be in good condition
    Myth 2-Testing is not Time consuming
    Reality: In SDLC phase the testing time consumes but worth
    Myth 3-Fully developed products are tested
    Reality: Testing depends on the code but creating test data, documentation is done , creating test cases is independent. Testing the software at early stage saves time and cost of the project
    Myth 4-Complete Testing is possible
    Reality: Testing with all possible values is not possible, standard techniques is used to overcome
    Myth 5-Tested software is Bug-Free
    Reality: No one can certify the software is 100% bug free. The possible defects are found using standard testing techniques.
    Myth 6-Missed defects are due to Testers
    Reality: Missed defect may be due to time, cost and changes in requirement constrains. Since testing team have the software at final hand it framed so.
    Myth 7- Only the testers are responsible for the quality of product
    Reality: Testers find the bug and inform to the stack holder during testing, it depends on them to fix it or to release. Time plays a main role.
    Myth 8- Testers Automation should be used wherever possible to reduce Time
    Reality: Test automation reduces time but without manual testing automation cannot be started. Automation testing is not possible for constant change in requirement.
    Myth 9-Anyone can Test software Application
    Myth 10- Finding bugs is the task of testing team alone
    Reality: Finding bugs is the task of testing team but developer is responsible for the specific component or area that is assigned to them for development and to test.

  5. Myths of software testing
    1. It is very expensive
    2. it is not time consuming
    3. only fully developed products are tested
    4. complete testing is possible
    5. software is bug free
    6. missed defects are due to testers
    7. only testers are responsible for the quality of the product
    8. testers automation should be used wherever possible to reduce time
    9. anyone can test software application
    10. Finding bugs is the task of testing team alone

  6. This document discusses 10 myths of Software Testing and tries to provide a reality for those myths.

    Myth 1-Testing is very expensive
    Reality- it is belief that testing should cost less during software development. Early testing can save both time and cost in many
    aspects. Reducing cost without testing may result in improper design of software application rendering the product
    useless.

    Myth 2-Testing is not Time consuming
    Reality- During the SDLC phases, testing is a time-consuming process but worth it. However diagnosing and fixing the errors
    during testing is a time-consuming but productive activity.

    Myth 3-Fully developed products are tested
    Reality- There is no doubt that testing depends on the source code but reviewing requirements and developing test cases is
    independent from the developed code. However iterative or incremental approach as a development life cycle model
    may reduce the dependency of testing on the fully developed software. Testing the software at early stages saves time
    and cost of project.

    Myth 4-Complete Testing is possible
    Reality– It is an issue when the client or tester thinks that complete testing is possible. It is possible that each one the paths are
    tested by the team but occurrence of complete testing isn’t possible. There might be some scenarios that are not
    executed by the test team or the client during the software development life cycle and may be executed once the
    project has been deployed. The software cannot be tested with all possible values of input and output in practical
    because of the time constraint. Hence we use standard techniques and methods for testing.

    Myth 5-Tested software is Bug-Free
    Reality– This is common myth that clients, project managers, and the management team believes. No one can claim with
    absolute certainty that a software application is 100% bug free even if the software was tested thoroughly.
    Software testing shows the presence of the defects and not their absence.

    Myth 6-Missed defects are due to Testers
    Reality– There are many reason that a software may have defects or bugs. It is not always the tester’s inefficiency to be blamed
    for the resence of bugs in software. The factors that might be the cause for presence of bugs in a software are|
    time, cost and requirements for changing the constraints

    Myth 7- Only the testers are responsible for the quality of product
    Reality- it is very common misinterpretation that only testers or the testing team should be responsible for the quality of the
    product. A testers responsibilities include the identification of bugs but the decision to fix the bug or release the software
    without bug fixes lies with the stakeholders.

    Myth 8- Testers Automation should be used wherever possible to reduce Time.
    Reality- It is true that Test automation reduces the testing time, but it is not possible to start test Automation at any time during
    software Development. Test Automation will be started when the software has been manually tested and is stable
    some extent. Test automation can never be used if requirements will keep changing.

    Myth 9-Anyone can Test software Application
    Reality – People outside IT industry think and even believe that anyone can test software and testing is not a creative job.
    However testers know that it is untrue. Testers can be think up many scenarios to crash the software which even the
    developers who created the software may not have thought of.

    Myth 10- Finding bugs is the task of testing team alone
    Reality- Finding bugs in software is a task of both the testers and the developers.

  7. Here we talk about myths in software testing
    Myth 1-Testing is very expensive.
    Myth 2-Testing is not Time consuming.
    Myth 3-Fully developed products are tested.
    Myth 4-Complete Testing is possible.
    Myth 5-Missed defects are due to Testers.
    Myth 6-Tested software is Bug-Free.
    Myth 7- Only the testers are responsible for the quality of product.
    Myth 8- Testers Automation should be used wherever possible to reduce Time.
    Myth 9-Anyone can Test software Application.
    Myth 10- Finding bugs is the task of testing team alone.

  8. 10 Myths of Software Testing:
    Myth1: Testing is very expensive.
    Myth2: Testing is not time consuming.
    Myth3: Fully developed products are tested.
    Myth4: Complete testing is possible.
    Myth5: Tested software is bug- free.
    Myth6: Missed defects are due to testers.
    Myth7: Only the testers are responsible for the quality of product.
    Myth8: Testers automation should be used wherever possible to reduce time.
    Myth9: Anyone can test software application.
    Myth10: Finding bugs is the task of testing team alone.
    Myth8:

  9. Myths of Software Testing:
    1. Testing is very expensive
    2. Testing is not time consuming
    3. Fully developed products are tested
    4. Complete testing is possible
    5.Tested software is bug free
    6.Missed defects are due to Testers
    7.Only the testers are responsible for the quality of product
    8.Test automation should be used wherever possible to reduce time
    9.Anyone can Test software Application
    10.Finding bugs is the task of testing team alone

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related Articles

Check Also
Close
Back to top button
Close
Close