Changes between Version 2 and Version 3 of HowtoBugBuster


Ignore:
Timestamp:
Mar 31, 2009, 11:16:06 AM (16 years ago)
Author:
Leo Fortey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HowtoBugBuster

    v2 v3  
    11= How to be a Bood Bug Buster (beta-tester) =
    22
    3 These steps explain how to report bugs correctly and how to be a correct beta-tester, like to report the correct information but also not many, and that the important is not to try an application to see if works, just the inverse, is needed to made it not working correctly...
     3These steps explain how to correctly report bugs and how to be a proper beta-tester. Reporting the correct information, though not too much, is more important. Quality, not quantity. The concept of a beta tester is not to try an application to see if works but to make it not work, and report it.
    44
    55== Essential points to remember when beta-testing ==
    … …  
    88 2. Search for bugs or visual defects
    99 3. Test all the different parts of the application to see if the program works well entirely and all its options available
    10  4. If you are on this step and everything before works correctly, try to do all the possible combinations of the parts of the application to found a possible bug
    11  5. Use your brain, so try using the application under many different circumstances to see if it works with other applications and the distro as a whole. For example, configure the network with with different interfaces (eth0, eth1, ath0, wifi0, ra0...), also test what happens if you configure the network and disconnect the cable, etc, be ingenious
    12  6. Think how the program works. The work of a beta-tester is not show how well the program works. It is the complete opposite. Your mission is to try to crash the application, to find a bug. Just as a cracker looks for a bug to enter a system without privileges, you need to be more intelligent than the machine. You need to understand how the machine and the program works and how the program communicates with the machine. You should try to confuse the program within limits. You need to beat the program. Only then... are you really satisfied.
     10 4. If you are on this step and everything before works correctly, try to do all the possible combinations of the parts of the application to find a possible bug
     11 5. Use your brain, so try using the application under many different circumstances to see if it works with other applications and the distro as a whole. For example, configure the network with different interfaces (eth0, eth1, ath0, wifi0, ra0...), also test what happens if you configure the network and disconnect the cable, etc, be ingenious
     12 6. Think how the program works. The work of a beta-tester is not to show how well the program works. It is the complete opposite. Your mission is to try to crash the application, to find a bug. Just as a cracker looks for a bug to enter a system without privileges, you need to be more intelligent than the machine. You need to understand how the machine and the program works and how the program communicates with the machine. You should try to confuse the program within limits. You need to beat the program. Only then... are you really satisfied.
    1313 7. Finally, and the most important one... try to report all the possible information (only useful) in order that the developer could fix the problem in the most easy and fast way... if you fix it, you can include a patch (or explanation) in the report, they are more than welcome!
    1414