Mantis Bug Tracking Interview Questions & Answers

  1. Question 1. What Is Mantis Bug Tracker?

    Answer :

    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.

  2. Question 2. Mention The Salient Features Of The Mantis Bug Tracker?

    Answer :

    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.

  3. Testing Tools Interview Questions

  4. Question 3. What Is The Difference Between New And Open Bug?

    Answer :

    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.

  5. Question 4. Explain The Different Types Of Bugs?

    Answer :

    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.

  6. Testing Tools Tutorial

  7. Question 5. Mention Some Tips For Bug Tracking?

    Answer :

    • If any bug found is confusing, it should be discussed with the developer.
    • The bugs should follow a proper cycle until closed.
    • If any bug closed by developer is not fixed, it should be reopened.
    • Never assume while tracking a bug.
  8. QTP Interview Questions

  9. Question 6. How To Write Good Bug Tracking Report?

    Answer :

    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.

  10. Question 7. What Is The Difference Between Bug And Defect?

    Answer :

    • A bug is getting a problem at the time of testing, where as a defect is problem that got by the customer in production time
    • A bug is a fault in a program which causes it to behave abruptly. Bugs are usually found either during unit testing done by developer of module testing by testers.
    • A defect is found when the application does not conform to the requirement specification. A defect can also be found when the client or user is testing.
  11. QTP Tutorial
    Media Interview Questions

  12. Question 8. What Is The Process Of Bug Cycle?

    Answer :

    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’.

  13. Question 9. What Is The Diff Status Of Bug Cycle?

    Answer :

    • A bug when found by the tester is marked as NEW.
    • This bug is checked for its validity by the test lead to mark it as OPEN.
    • The bug is then ASSIGNED to the developer.
    • The developer on fixing the bug gives it to the tester for regression testing.
    • The tester may either REOPEN or CLOSE the bug.
  14. Bugzilla Bug Tracking System Interview Questions

  15. Question 10. How To View Specific Projects In Mantis Bug Tracker?

    Answer :

    • Log in with your username and password. If you’ve forgotten your credentials, you can reset your password using your email address from the link on the login page.
    • To see your project’s main page, you must select its name in the drop-down menu displayed in the upper right corner of the screen. Once the page loads, click on the tab ‘See issues’ to see all the previous entry bugs for this project.
  16. Bugzilla Bug Tracking System Tutorial

  17. Question 11. Explain How To Report A Bug In Mantis Bug Tracker?

    Answer :

    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.

  18. Automation Testing Interview Questions

  19. Question 12. Does Mantis Provide An Xml-rpc Interface?

    Answer :

    No, but it provides a SOAP webservice interface.

  20. Testing Tools Interview Questions

  21. Question 13. Is There A Mantis Version For Smart Phones / Pdas?

    Answer :

    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.

  22. Jira (software) Tutorial

  23. Question 14. How To Add A Mantis Bug Tracker?

    Answer :

    Under Manage Tab, go to Manage Projects:

    • Enter Project Name
    • Select Status
    • Enter Description
    • Click Add Project
  24. Question 15. How To Create User In Mantis Bug Tracker?

    Answer :

    Go to Manage > Manage Users and Click on ‘Create New Account’ and update below fields:

    • Username
    • Real Name
    • Email
    • Access Level
    • Click Create User

    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.

  25. Jira (software) Interview Questions

  26. Question 16. How To Create Custom Field In Mantis?

    Answer :

    • Go to Manage Custom Fields
    • Enter Field Name
    • Click Button ‘New Custom Field’
    • Select Field Type
    • Enter Field Specific Data
    • Hit Update Custom Field

    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.

  27. The Java Debugger (JDB) Tutorial

  28. Question 17. Does Mantisbt Integrate With Source Control Tools?

    Answer :

    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).

  29. Test Estimation Interview Questions

  30. Question 18. How Do We Get Help For Mantis?

    Answer :

    • Use MantisBT Forums or mantisbt-help at lists dot sourceforge dot net for posting questions. Our preference goes to the forums.
    • Use mantisbt-dev at lists dot sourceforge dot net for development related discussions.
    • Use Mantis Bug Tracker for reporting feature requests and bugs.
    • Use MantisBT Manual comments to identify a problem with the documentation or to contribute hints that are ought to be part of the documentation.
    • Use mantisbt-lang at lists dot sourceforge dot net for discussions relating to localisation to a specific language.
  31. QTP Interview Questions

  32. Question 19. How Do We Contribute Patches?

    Answer :

    • If you are about to implement a major feature, it is strongly recommended to get in touch with the developers. Such interaction will make it much more likely that your mods be applied to MantisBT distribution.
    • Patches should be attached to a Mantis Bug Tracker issue.
    • A patch should be attached as a single zip or .tar.gz file.
    • A patch should include a copy of all new files / modified files as well as a diff (patch) file (if possible).
    • A patch should only contain one feature. If a patch has a mixed bag of features, it makes it harder to understand and apply.
    • If you require feedback from developers relating to the patch, then post a message to mantisbt-dev at lists dot sourceforge dot net which refers to the issue including your patch. Ideally, the feedback will be added to the issue as notes. If not, then the patch owner should summarise the feedback as notes.
    • Fixes and updates to the patch should be attached to the same issue as should be marked clearly. With every attachment there should be a note that refers to the file name and specifies the updates done.
    • Join MantisBT IRC channel for realtime discussions with developers.
    • Patches should following MantisBT coding style.
    • Keep your patches up-to-date as new MantisBT versions are released.
  33. GDB Debugger Tutorial

  34. Question 20. How Do We Contribute Localisation To A New Language?

    Answer :

    • Use strings_english.txt as the basis for the new localisation file.
    • Consider using UTF8 encoding.
    • Submit an issue into the Mantis Bug Tracker and attach a compressed version of the file.
  35. The Java Debugger (JDB) Interview Questions