5 avg. rating (100% score) - 5879 votes
Are you interested in game testing jobs? Looking for the testing career opportunity? Having expertise in Mantis Bug Tracking testing tool will be great opportunity to win testing jobs. MantisBT is a widely used free web-based bug tracking system works with PHP, MySQL, MS SQL, and PostgreSQL databases. Search and apply for the latest jobs such as QA tester, QA engineer, manual testing,sr.engineer,manual test enegineer,enterprise developer, quality analyst, senior tetser,software test engineer, test analyst-mobile/web application testing, senior quality assurance engineer and assistant manager testing etc. If you have expertise in regression testing, Testing and Quality Assurance of mobile and web apps, including cross-browser testing and cross-device testing then it will be an added advantage. Have a look at Mantis Bug Tracking tool job interview questions and answers to get succeed in job interviews.
MANTIS is a free, open source bug tracking software. It can be used to track bug for various software projects. You can easily download and install the Mantis for your use. Mantis now also provides a hosted version of the software.
Some salient features of Mantis are:
Email notifications: It sends out emails of updates, comments, resolutions to the concerned stake holders.
Access Control: You can control user access at project level
Customize: You can easily customize Mantis as per your requirements.
Mobile Support: Mantis supports iPhone, Android and Windows Phone Platforms.
Plugins: An ever-expanding library of plugins to add custom functionality to Mantis.
New: In finding an issue in testing, all relevant checks are performed, like whether is was occurring in the previous release. If the issue is so, reopening the bug and creating new defect is done by changing the status of that defect to ‘new’.
Open: When a new bug is opened, development or project manager revises it, followed by assigning the task to the developer, and changes the status from ‘new’ to ‘open’.
When the bug is found by the tester, the status is marked as NEW. Once this bug is verified by the test lead for its validity, the status is changed to OPEN.
The different bugs are:
Show-stopper / critical bugs: The core dumps, products abnormally shuts down and no work around will be found out, like OS automatic freezing.
Major Bugs: The work around is found, but the implementation can be done, like performance degradency.
Medium Bugs: These bugs include database errors, link errors, low response time
Low/minor Bugs: These bugs are typos, simple GUI errors.
Title should be clear: A good title is a must, which the essence of the bug report be well grasped by the developer.
One but per report: A bug report should have only one bug and not more or no less. In case more bugs are placed, some of the bugs may be overlooked.
Minimum, quantifiable steps to reproduce the problem: This is a very important tip. Developers need to get the problem in the shortest possible time. So the tester needs to help them for doing just that task. Testers need to have few rounds of testing and be able to produce the problems using minimum steps.
Expected and observed results: A bug report should always contain the expected and the observed result. The developer does not think that the bug is a real bug. Testers should take the responsibility to explain the developers that went wrong.
The build that the problem occurs: It is common the daily builds. If the exact problematic build is not specified by the tester, it is hard for developers to resolve an already-solved problem.
Pictures: ‘A picture is worth a thousand words’! Certain times, the words do not flow. If such situations, it is better to have a clear picture that perfectly illustrates the problem.
The following steps involved in the bug cycle process:
Bug investigation:when the tester find the bug
Bug assignment:when the tester assigns the bug to the developer
Bug fixing: when the bug is fixed by the developer
Bug retesting:when the developer fixes the bug and given to the tester
Bug closing and reopening:when the tester retested and the status is changed to ‘closed’.
1) To report a new issue, click on 'Report Issue' in the main menu bar (shown below.)
2) A form will open titled “Enter Report Details”. You must fill in every field that it contains. The following steps describe how to do this
3) First, you must always select 'All projects – general' in the *Category drop-down menu.
4) Select the reproducibility from the second dropdown. Keep in mind that as much as you can, you should find the bug’s circumstances before logging it. Ideally, you should be able to reproduce it 100% of the time. But sometimes it is impossible. In these rare cases, you can use 'sometimes' if the bug occurs sporadically or 'random' if you really are unable to reproduce it.
5) Select a severity for the bug:
minor if the bug is important but not detrimental to the proper functioning of a feature
major if the bug is important and compromises the user’s experience
critical if the bug completely prevents the user from continuing what he was doing, or if the bug crashes or freezes the site/app/game
6) Select a priority for the bug:
'low' if the bug has very little impact on the user’s experience
'normal' if it needs fixing soon but it is not urgent
'high' if it needs fixing relatively soon
'urgent' if it is a top priority and should be quickly
'immediate' if it needs fixing right now
7) Fill in the 3 forms under “Select Profile”. These are:
Select a Platform: the device you used for your tests
Select an Operating System: the operating system of the device
Select an OS version: the version number of the operating system
8) Leave the 'Assign to' drop-down blank unless told otherwise.
9) In the summary field, enter a title for your bug. The title should begin with the name of the section of the app/website/game in which the bug happens between brackets , followed by a brief description of the bug.
10) Update the description field the detailed info abt the bug.
11) The 'Steps to reproduce' section should contain the steps that a developer or other tester unfamiliar with the project should follow to reproduce the issue
12) The 'Additional information' field must be used to inform the developer of what device/browser and on what device/browser version the bug was found
13) Use 'Upload File' to upload your screenshot or video
14) View status should be left public and the ‘report stay’ checkbox should be left unchecked unless you have another issue to enter immediately.
No, but it provides a SOAP webservice interface.
Yes, MantisWAP provides a very light weight interface for Mantis access through a smart phone or PDA. It is optimize for speed and minimization of consumed bandwidth.
Under Manage Tab, go to Manage Projects:
Go to Manage > Manage Users and Click on 'Create New Account' and update below fields:
In the next screen assign user to the desired project.Update Email and other Account Preferences as desired. After that the login credentials are sent to the user on their email.
Now the custom field got created. Click the Custom Field Again and Link Custom Field to your Project. After that in Report Issue section, the new custom field will be reflected.
Scmbug is a system that integrates software configuration management (SCM) with bug-tracking. It aims to be a universal tool that will glue any source code version control system (such as CVS, Subversion, and Arch) with any bug-tracking system (such as Bugzilla, MantisBT, and Request Tracker).
Mantis Bug Tracking Related Tutorials
|Testing Tools Tutorial||QTP Tutorial|
|Bugzilla Bug Tracking System Tutorial||Jira (software) Tutorial|
|The Java Debugger (JDB) Tutorial||GDB Debugger Tutorial|
Mantis Bug Tracking Related Interview Questions
|Testing Tools Interview Questions||QTP Interview Questions|
|Media Interview Questions||Bugzilla Bug Tracking System Interview Questions|
|Automation Testing Interview Questions||Jira (software) Interview Questions|
|Test Estimation Interview Questions||The Java Debugger (JDB) Interview Questions|
|Zomato Social Media Strategy Interview Questions||Test Manager Interview Questions|
|Test Director Interview Questions||HP QuickTest Professional Interview Questions|
|Test Plan Interview Questions||Defect Reporting Interview Questions|
Mantis Bug Tracking
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.