The solution shouldn't be so tightly integrated with the ALM tool that they have. It should have its own base rather than the repository. If we could save it in other repositories or some other spaces, then that would be a plus.

We should also be able to create a BPP script on its own.

Initial releases we used of the product (v12) were a little unstable, but with the release of v12.01, we had no further issues.

The run speed is not as fast as if a local script would be running, but that is one of the downfalls of using a client/server approach.

There's only one thing that I think needs improvement. When I started off using this solution, I used the Google search engine to learn how to use the tool. I would also check with my colleagues who have a lot of knowledge about it. Selenium has fields of information available. If you click on that field there will be an explanation about how to use the tool. It will be a lot easier to understand if Micro Focus included this feature. It is easy to find with the search button, but it would be a great help to the users who are new to this tool.

The only one I can really think of is speed to test execution.

Since all the artefacts are maintained in Quality Center sometimes accessing tests to maintain and modify takes a lot of time. If there is network failure while opening then the corresponding script gets locked for a long time. So it would be really convenient if they create a local copy of the component or give option to the user to edit the component or script offline.

Another thing is components should have the ability to copy within the script itself rather than dragging the component from the repository each time it is required to be used.

Test Execution speed has been my biggest concern. HP has improved on it over releases, but there is still room for improvement.