locked
How to test my software that has some bugs

    Question

  • This is a photo slideshow video called DVD Photo Slideshow software we developed 2 months ago,but there are some bugs.We have add the software to our website to sell.After some cumstomers using,some bugs appear.But we test the software in our computer without any bugs.Why the bugs occur when the cumstomers use?
    We have support some resuluton resource to the cumstomers,but some bugs still exist.
    How to resolve the problem ?We have test the software by using WinRunner and LoadRunner.We have do the function test and performance test for many times.
    Who can give us some constructive suggestion to resolve the problem ?

    You can also review our software Photo Slideshow DVD here . why we don't the buds of the software but the cumstomers can discover ??
    We need some software test experience to resolve the software bud problem.

    our software runs on the windows OS platform.
    Wednesday, September 30, 2009 2:22 AM

Answers

  • Hi,

     

    The problem is likely related to the software and hardware configurations that are or are not supported by your software. You say that you have performed the functional tests and performance tests a number of times. Have you performed these tests on all the popular configurations or not? Here are a few suggestions:

     

    1. First of all, you need to know your software. Find out the following and publish this information to your customers.

    a. The minimum hardware and software configuration that is needed to run the software e.g. list the slowest processor, minimum amount of RAM, minimum amount of video memory, minimum free hard disk space etc. that is needed to run the software

    b. The recommended hardware and software configuration: You may get this configuration from the system on which you perform the most number of tests. Include the required device drivers in your list.

    c. The OS that your software works on e.g. Windows XP, Vista and so on.

    d. The languages that your software works in e.g. English (US), English (UK) and so on. List only those languages with which you have tested your software.

     

    2. Secondly, build and maintain test beds with the most popular configurations used by your customers.

    Before releasing the software to your customers, you should perform functional and performance tests on each of these test beds to satisfy yourself.

     

    3. Thirdly, build a bug repository with all the customer-reported bugs in it. In each bug report, make sure that the configuration used by the customer is recorded.

    If possible, re-test these bugs before every release as part of your regression test.

     

    By this stage, you should have a good handle on the problem.

     

    4. Finally, request your developers to write or modify the source code in as configuration-agnostic way as possible e.g. use Windows features wherever possible, remove hard coding and so on.

    Test your software on each supported configuration before you release the software to your customers.

     

    Thank you,

    Inder P Singh

    Blog: Software Testing Space

    Monday, October 05, 2009 7:21 AM
    Moderator

All replies

  • And the software also cause some hardware problems,some cumstomers can not use the software on some computers with new hardware
    Wednesday, September 30, 2009 2:29 AM
  • Hi,

     

    The problem is likely related to the software and hardware configurations that are or are not supported by your software. You say that you have performed the functional tests and performance tests a number of times. Have you performed these tests on all the popular configurations or not? Here are a few suggestions:

     

    1. First of all, you need to know your software. Find out the following and publish this information to your customers.

    a. The minimum hardware and software configuration that is needed to run the software e.g. list the slowest processor, minimum amount of RAM, minimum amount of video memory, minimum free hard disk space etc. that is needed to run the software

    b. The recommended hardware and software configuration: You may get this configuration from the system on which you perform the most number of tests. Include the required device drivers in your list.

    c. The OS that your software works on e.g. Windows XP, Vista and so on.

    d. The languages that your software works in e.g. English (US), English (UK) and so on. List only those languages with which you have tested your software.

     

    2. Secondly, build and maintain test beds with the most popular configurations used by your customers.

    Before releasing the software to your customers, you should perform functional and performance tests on each of these test beds to satisfy yourself.

     

    3. Thirdly, build a bug repository with all the customer-reported bugs in it. In each bug report, make sure that the configuration used by the customer is recorded.

    If possible, re-test these bugs before every release as part of your regression test.

     

    By this stage, you should have a good handle on the problem.

     

    4. Finally, request your developers to write or modify the source code in as configuration-agnostic way as possible e.g. use Windows features wherever possible, remove hard coding and so on.

    Test your software on each supported configuration before you release the software to your customers.

     

    Thank you,

    Inder P Singh

    Blog: Software Testing Space

    Monday, October 05, 2009 7:21 AM
    Moderator