1. Bugzilla
Are you
looking for a stable, actively maintained, widely adapted bug tracking system?
Look no further. Bugzilla is for you.
This is used by
various big open source projects to track their bugs. For example, Linux kernel
development team, Apache development team, GNOME development team uses
bugzilla. Red Hat also uses bugzilla to track the issues found in Red Hat
Distribution system.
Bugzilla is written
in Perl, and works on various databases including MySQL and Oracle. This
step-by-step instruction guide on how to install bugzilla will get you
started.
Bugzilla Features:
- Time tracking
- Private attachment and
commenting
- Flexible reporting and
charting. Including ability to to scheduled reports and receive it via
email.
- Add custom fields and
workflows.
- View full list of features
here.
Additional Info:
- Home Page: http://www.bugzilla.org
- Developed by: Mozilla
foundation
- Stable Release: 3.6.1
- License: Mozilla public
license
2. Mantis
Mantis
issue tracking system is written in PHP, and works on various databases
including MySQL, MS SQL, PostgreSQL.
Mantis Features:
- Source code integration
- Time tracking
- Issue relationship graph
- Custom fields and workflow
- Anonymous access
- View full list of features here.
Additional Info:
- Home Page: http://www.mantisbt.org
- Stable Release: 1.2.2
- License: GNU v2
3. Trac
Trac is
written in Python. Apart from issue tracking, it also provides wiki, and
integration to subversion. The web interface is very simplistic and easy to
use. This also provides project management features including roadmap and
milestone tracking.
- Home Page: http://trac.edgewall.org/
- Stable Release: 0.12
- License: BSD
4. Redmine
Redmine is written in
Ruby on Rails. Apart from tracking issues, it provides a full project
management features.
Redmine Features:
- Project management including
Gantt chart
- Project Wiki
- Time Tracking
- LDAP Authentication
- View full list of features here.
Additional Info:
- Home Page: http://www.redmine.org/
- Stable Release: 1.0.1
- License: GNU v2
5. Request Tracker
RT is written in
Perl. Apart from the standard issue management, you can use this as a ticket
tracking system. RT Features:
- Time tracking and reporting
- Integrate with LDAP
authentication
- View full list of features
here.
Additional Info:
- Home Page: http://bestpractical.com/rt/
- Stable Release: 3.8.8
- License: GPL v2
6. OTRS
OTRS bug tracking
software is written in Perl. OTRS has all standard defect tracking features
that you would expect. View full list of features here.
- Home Page: http://otrs.org/
- Stable Release: 2.4.7
- License: GPL
7. EventNum
This
was developed by the MySQL team, and written in PHP. You can use this as a bug
tracking tool, or issue tracking system. This provides all the basic features
that you might expect in a tracking system.
Home Page: http://forge.mysql.com/wiki/Eventum/
Stable Release: 2.2
License: GPL
8. Fossil
Fossil
is written in C, and uses SQLite database. Apart from bug tracking, it also
provides Wiki. Installation is very straight forward, as it is a single
executable that contains everything you need to get fossil up and running.
Home Page: http://www.fossil-scm.org
License: BSD
9. The Bug Genie
Bug genie is written
in PHP. Provides a wizard based bug tracking software. It also integrates the openSearch functionality.
Integrates with Subversion. You can develop your custom modules on top of bug
genie.
Home Page: http://www.thebuggenie.com/
Stable Release: 2.1.1
License: MPL
10. WebIssues
WebIssue is written
in PHP, and uses MySQL database for the server side. Everything in this top 10
list is web based bug tracking system except WebIssues. This is at number#10
because it doesn’t provide a web-based interface. You
need webissues client that runs on Windows, or Linux to access the server
component.
Home Page: http://webissues.mimec.org/
Stable Release: 0.9.6
License: Open Source
출처 : http://www.thegeekstuff.com/2010/08/bug-tracking-system/
'QA & TEST' 카테고리의 다른 글
채번 규칙이 필요한 이유 (0) | 2013.09.27 |
---|---|
ISTQB_Foundation Level Syllabus 차례(영문/한글) (0) | 2012.01.16 |
Slideshare의 Effective Software Testing 자료 (0) | 2012.01.05 |
2012년 ISTQB 정기시험 일정 (0) | 2012.01.04 |
Bug Triage(버그 선별)을 해야 한다. (0) | 2012.01.03 |
댓글