Testing with trac

trac [ is an enhanced wiki and issue tracking system for software development projects.

Documentation on trac is available at:

URLs

Library Project

Restaurant Project

Store Project

Notes

  • Testers do not need to be logged inin order to use the trac system. Developers got a login/password.
  • Look at the list of implemented features before submitting a bug.
  • Use trac to submit bugs only. If a feature works and you want to congratulate the developers, use e-mail.

Table of Contents

1. List of Implemented Features

2. Submit a Bug

3. Bug Report

4. Bug Fixing Report

1. List of Implemented Features

  • For testers
  • Updated by developers
  • DO NOT TEST A FEATURE THAT IS NOT IMPLEMENTED i.e. NOT LISTED!
  • The list of implemented features is available at the following URLs:

Figure 1: List of Implemented Features

2. Submit a Bug

  • For testers
  • Go to: New Ticket
  • Enter the following REQUIRED information:
  • your email address[1]
  • a short summary of the bug (no more than 20 characters)
  • the type of the bug (i.e. Bug_GUI, Bug_Docs, Bug_Other, Bug_Database, Bug_java, Bug_Functional_Requirement or Bug_Nonfunctional_Requirement)
  • a full description of the bug
  • THIS PART IS VERY IMPORTANT: DEVELOPERS MUST BE ABLE TO REPRODUCE THE BUG SO YOU HAVE TO PROVIDE ADEQUATE INFORMATION.
  • This description must contain how you logged in, the complete URL to access the screen of the bug, and a description of the bug itself (What is the actual result? What is the expected result? What went wrong?).
  • the priority of fixing the bug (i.e. blocker – highest priority, critical, major, minor or trivial)
  • the component (i.e. database, design, functionality, gui)
  • Keywords (one or two keywords)
  • CC ( and your email address separated by a comma - ,)
  • Submit the ticket
  • On the next screen, you can add an attachment(You can attach a Word document with a screen snapshot to support your bug submission. For example, when you detect a bug, you may want to press Print Screen to save the browser screen, and then you can paste the content of the clipboard in a Word document.)
  • is an example of bug submission.

Figure 2: Submitting a Bug

3. Bug Report

  • For developers
  • To view the number of bugs submitted with their description, status, priority and definers, go to: View Tickets and Bugs
  • Reports can be created if you logged into the system.
  • Specific reports may be added during the semester.

Figure 3: View Tickets

Figure 4: Bug Report Sample

4. Bug Fixing Report

  • For developers
  • Log in the system
  • Go to: View Tickets and Bugs
  • Click on the bug you are addressing

Figure 5: Bug Report Sample (When Logged In)

  • Enter the following REQUIRED information concerning your bug fix:
  • your email address
  • a comment (no more than 20 characters)
  • a description of the bug fix
  • Change the status of the bug (i.e. fixed, invalid, wontfix, duplicate, worksforme) by clicking on resolve as.
  • Submit the changes

Figure 6: Bug Fixing Report (Page 1)

Figure 7: Bug Fixing (Page 2)

1

[1] There are problems with yahoo emails so use a gmail, Pace, ITC, Delhi University email that permits to identify you (I want to be able to see who submitted bugs or not).