In the world of technology people always come out with something that can make their life easier. My current job now focusing more on bug fixes and I can say that I use bug tracker. Bugs, defects, errors are the common thing for all the developers. Bug Tracker is one of the platform for developers to keep track all reported software bugs in work. In this situation Tester Team will work together with Developer Team and at the same times it will makes a collaboration with team members and client easy, fast and professional. There's a lot of bug tracker nowdays like Mantis Bug Tracker , Team Foundation Studio ZOHO Bug Tracking , Axosoft, Bugherd and so forth.
In this entry I would like to talk about Mantis Bug Tracker which I use in my work.
What is Mantis Bug Tracker?
MantisBT is a web based bug tracking system. It is one of the most popular open source bug/issue tracking systems. It is developed in PHP, with support to multiple database back-ends including MySQL, MS SQL, PostgreSQL and DB2. By using this software or tools, you can see how many bugs is assigned under your name during software testing happen. Beside, we also can identify the priority of every defect coming in whether it is high, medium or low.
Why Mantis?
Praying Mantis are insects that feed primarily on other insects and bugs. They are extremely desirable in agriculture as they devour insects that feed on crops. They are also extremely elegant looking creatures. So, we have a name that is fairly distinctive and descriptive in multiple ways. The BT suffix stands for "Bug Tracker" and distinguishes this project from general usage of the word Mantis. However, over time the project was typically referred to as Mantis.
Bug Track Life Cycle
It is the process or work flow on how the software testing undergo. There's a few status used to categorizes all the bugs stages together with person in charged. Example status New. New means new defect/bug/error defected or reported by tester team. So the person's in charge will be Tester Team. The process will continuously looping until the bug is fixed and successful test by user.
No comments:
Post a Comment