The inseparable Excel from any bug tracking tool

I had seen many tools and met many test managers and leads; whenever they want to present some report to their management, they need Excel sheets. Tools provide many charts and reports, but end of day, they have specific format for their needs.

The easy way to help them is to provide an export option from tools to Excel.Simple clicks, and test manager can get the relevant data and do whatever he/she wants. Look at this sample from QAMonitor tool.

Usually there will be grids to show the defect details; from there,the manager or lead can do filtering and then export. This is one of their top most requirements.

Also, many test leads and managers are not happy with open source tools. They want to move out to a better test management system. But how to move the data from the existing ones to the new system? QAMonitor provides a simple solution.

Import from an excel sheet. Before doing this, export the data to csv files, either from the tool or from the database the older tool uses. Once this is done, you are just minutes away from using QAMonitor.



Do an import. Import engine will ask you to point the file and it will take you thru steps to map the columns in your excel file to the fields that QAMonitor needs for bug tracking. Very simple with virtually no learning curve required, you can import the defect details and get started in minutes.





This way, QAMonitor helps any test manager or lead to get started in minutes, whether you start new or migrate from another tool. QAMonitor helps you to feel comfortable in presenting the results, the way you want.

How adaptive is QAMonitor?

Dinosaurs did not adapt to the environment and hence they perished. Cockroaches did that trick well and still living. Same for any tool.

Recently we received a set of questions from customers - but most of those questions followed the same tone - "How can I make the tool to adapt to my project?". I am used to some names and the tool does not have those, what to do?

The UI must show the exact labels that the users are familiar with. Else, they may feel that the tool is not capturing the data they want to.

Here is the simple 10 minutes exercise you need to do.

1. What fields you want to capture in requirements, test case, tasks and defects? First list them out.
2. Login as eadmin to your enterprise, Go to settings, go to System Defined Fields.
3. Check whether the list of fields you have is there in the respective module such as defects.
4. For example, you need a field called "Importance" and there is a field called "Priority".
5. In that screen, change the label of the field Priority to Importance.
6. This way, there may be fields already available, but you call it by one name and the tool calls it by another name; just rename in the tool.
7. Log out and relogin; go to the project that you configured. Click on new defect. You will see the same field names that you wanted. This is half the battle won.
8. Mark those fields that you have in list that are not in the tool.
9. For example, you want a field called Browser as a list box, with values MS IE, FireFox, Chrome.
10. Login as eadmin to your enterprise, Go to settings, go to User Defined Fields.
11. In the defects module, add a new field, with field label as Browser and type as single selection list box and add these values as comma separated ones.
12. Repeat the above step for all the fields that are not in the tool.
13. Log out, relogin and go to the project. Create a new defect.
14. Now you will see those new fields that you want, right in front of you.

This way, you can make the tool to adapt to your templates.