Using SoloBug

SoloBug is a stand-alone bug reporter for TestTrack. A SoloBug file is a single bug report that includes the following:

• Your contact information and computer configuration
• A description of the problem or feature request
• The steps to reproduce the problem
• Optional file attachments

Keep the following in mind before you start:

• You may want to create a directory to save your SoloBug files in. This makes it easier to find them and email them to your vendor.
• The tasks in this section are illustrated using the default SoloBug executable. The SoloBug executable may include customization of such things as the title, instructions, and field names. You may follow different steps depending on the information your vendor needs.

Starting SoloBug

SoloBug is distributed as a stand-alone executable. Your software vendor may email the SoloBug executable to you or ask you to download it from their Web site. When you find a bug simply start SoloBug, provide the requested information, save the file, then email it to the software company.

1. Double-click the SoloBug executable.
   If you are using cross-platform SoloBug, the executable ends with a .exe extension.
   If you are using Palm-based SoloBug, the executable ends with a .pdb extension. The executable is usually named SoloBug.exe or SoloBug.pdb. However, you may be using a customized SoloBug executable that has a different name.
2. After SoloBug starts, you can leave it running and switch to it to create bug reports and feature requests. When you're ready, email the SoloBug files to your vendor.

Entering your contact information

SoloBug stores your contact information so you only have to enter it once. You can change it at any time.

1. Click Contact Info.
2. Enter your contact information.
3. Click OK. Your information is saved.

Entering computer information

Your computer information helps the support department troubleshoot the bugs you submit. SoloBug stores your computer information so you only have to enter it once. You can change it at any time.

1. Click Computer Info.
2. Click Capture Config (Windows only option). SoloBug automatically populates some of the fields such as Operating System and OS Version.
3. Enter the information in the remaining fields. Some defects are related to hardware and supplying complete and accurate information can help support fix the bugs you report.
4. Click OK. Your information is saved.

Creating a bug report

Bug reports and feature requests are important to improving a product's quality. Make sure your bug reports are concise and accurate.

1. Start SoloBug.
2. Enter your contact information and computer configuration if you have not already done so.
3. Enter the SoloBug information.
4. Enter Summary information about the defect.
5. Select a defect Type.
6. Select a defect Severity.
7. Select a Product name.
8. Enter a Component name, if applicable.
9. Enter a software Version.
10. Click the Description tab. Enter detailed information about the bug you are reporting or feature you are requesting.
11. Click the Reproduce tab if you are reporting a bug.
12. Select a Reproducible level.
13. Enter the steps to reproduce the problem. These steps are often crucial to solving the problem.
14. Click Attach File to attach a file. You may want to attach a file to help make your description clearer. For example, if a bug causes a server crash, you can attach the server log file.
    To attach multiple files zip them together and attach the zipped file.
15. Click Save.
16. Enter a file name or use the automatically generated name.
17. Click Save again. The SoloBug file is saved with a .sbg extension. It is now ready to email to your vendor.
18. Choose File > New to enter another bug report.
19. Choose File > Exit to close SoloBug. ( File > Quit on Mac OS X)