We are primarily interested in improving the flexibility to customize parts of the tool. At this point, we feel that the customization is bad. For example, we would like to be able to automatize internal projects. We would like like to see the visibility improved, and want to perform certain tests faster.

We would also like to manage the integration testing end-to-end. This is very important to us.

In terms of usability and the interface, a few small improvements can lead to a lot of benefits. The interface is good but can be improved.

The section on managing requirements for testing has to be improved. This is an old feature that has not been updated at the same rate as the rest of the tool.

Better management of mandatory fields.

Some minor usability issues.

From a test automation perspective, the main feature missing is the ability to schedule executions with only failed tests.

• Reporting
• Execution planning
• Requirement
• Dashboard

So far so good. Although, I once met an issue where I created a test case, and deleted it immediately. However, it seems that this test case still exists in the database, and that this test case is still being included in our execution runs, I've no idea how to completely removed this unused test case.

I think that the portal could be cleaner and faster.

Product does not respond well on virtual machines because of network and memory issues. It will be great if we get something which works well on bad network and takes less memory to execute the commands.

Adding the test cases and assigning them to particular testers can be improved. 

The testers who wrote the test cases and added it to the plan were the only ones able to see and execute it. Others, who weren't this involved, couldn't. 

And we weren't able to find the import function of test cases from Excel.