IBM Rational has the RFT, which is rational functional testing. We do test automation with rational functional testing. So after we do that, we can put in all the code, then I can build it, then put all the test cases, and put all the build code for the shared location. And then rational that shared location means that RQM has access to the shared location. So, when we execute, if a test case is automated, we can run it from RQM. We need to have the environment ready for it to execute.

Once we have that, then we can select the task case. So, by clicking on one button, the other environment is automatically plugged in. Then test results will be automatically transferred back to our RQM. So, in RQM, we can view it, and it is integrated. So we can run the test and the automation from RQM, and the test results will come back. Azure DevOps first test case is there, but then we tried to use Selenium to do half automation. Still, we realized that it wouldn't have the integration. We could do something in the pipeline, but it fires the Selenium test automation code. But then the test results won't be brought back or added to AzureDesk DevOps. That's something that I do hope that there can be another other system that can have this kind of integration.

RQM can be improved because it's not related to our server and could be faster. We need to find out how much database storage is needed and keep increasing it. We heard that the latest version of RQM can clean up some old ones and give the same test result. But that one feature we are yet to use. It's a setting that we can set up, and then it goes automatically or gives me the choice to do it manually.

In a test plan, all of the test cases are flat and there's no hierarchy in it. It would be helpful if we could assign a hierarchy to a group of test cases. Instead of using a test suite or child test plan, I would like to have sessions. For example, we could have a session for eFax fixes, a session for regression, and sessions for new feature testing. I would like to have some hierarchy in it.

RQM could be improved by adding a feature that allows test requirements to be selected when creating a task plan. I would also like to see a feature where you can have a test plan with manual and automated test cases, and the automated ones can be added into the pipeline so they can be invoked after deployment.

Currently, the user interface needs to be more user-friendly.  

In one of IBM's main competitors, Quality Center, the options are much more straightforward than what is offered in IBM. IBM's platform is too complicated and should be simple like Quality Center's. 

The integration and enhancement features need to be across all the testing tools and there needs to be integration between them.

The solution should simplify the import or export as well as support multiple extensions.

Overall, the solution is not user-friendly, and you need a very technical person on it in order to run it properly.

I think it's fine from a performance perspective but usability is something that needs improvement. It might be because of the complexity. They introduce some entities before people learn how these entities link to each other. It's not intuitive. Tools like JIRA qTest are much more intuitive, for example. Quality Center is simple as well.

Integration capabilities with other vendors' tools should improve.

There are a couple of things that can be improved:

1. The user interface can be improved; it is the same interface that I have been seeing for the past so many years, whereas the other CLM modules changed significantly.
2. It does not provide inbuilt capabilities for managing the tasks and planning activities related to testing. For this purpose, you need to buy another module, i.e., IBM Rational Team Concert (RTC).

Mainly Quality Assurance and DevOps, but of course the whole company and management areas with more knowledge of quality and client success approach.

• Management of artefacts
• Support of paramater needs to be easier
  

Adding support for uploading a collection of test cases would be a helpful addition. As it is now, we cannot upload a set of test cases, and instead, have to create it manually. Being able to upload hundreds of test cases would save us time, but it needs to be fast. For example, if 10 users are writing 100 tests case in a day, then uploading them should not take more than a minute.

Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed. As the number of test cases grows, it’ll be really difficult to maintain the test cases. The tool should be able to support and maintain the test cases in a folder-wise structure to identify the different module/phase-wise test cases.