Search

TOPIC: RAT Plugin doesn't have the same metrics than RAT

RAT Plugin doesn't have the same metrics than RAT 4 months 3 weeks ago #32

  • javier-fernandez
  • javier-fernandez's Avatar
  • Offline
  • Administrador
  • Posts: 52
  • Thank you received: 1
  • Karma: 0
Hello!

I just inform you that I found a little error in RAT plugin for DOORS (v15.1)

Indeed, metrics that concerned DOORS attributes are not correctly assessed in the plug in. The metrics are correctly evaluated in RQA and in RAT but are not in RAT plug in for DOORS.

Is there a solution for it?

Thanks!
The administrator has disabled public write access.

RAT Plugin doesn't have the same metrics than RAT 4 months 3 weeks ago #33

  • javier-fernandez
  • javier-fernandez's Avatar
  • Offline
  • Administrador
  • Posts: 52
  • Thank you received: 1
  • Karma: 0
Hi!

This is a common problem when RQA/RAT and DOORS Client are installed in the same computer (as localhost).

The RQA, RAT and RAT Plugin use the DOORS Database connection as a parameter in order to create the connection to the requirements modules. In RQA/RAT, this parameter is provided by the user and they have their own internal file to store this parameter in your computer. However, in RAT Plugin, this parameter is provided by DOORS Client. The thing here is that there is a mismatching between the DOORS database connection parameter used in RQA/RAT and RAT Plugin.

You probably have something similar than this:
RQA/RATRAT Plugin
36677@localhost36677@yourcomputer

This means that, in fact, they are different connections, so different repositories. You can check this information in the SKB assets in the RQS Server.

The solution for that is simple: just change the DOORS connection parameter from 36677@localhost to 36677@yourcomputer.

IMPORTANT: if you do that, you won’t access to the quality metrics you created for 36677@localhost (you won’t lose them, but you won’t access to them). In this case, I suggest upgrading the metric baseline with the changes before making this connection modification.

Hope you find this information useful. The solution for this issue is already in the roadmap for next release.

Regards,
The administrator has disabled public write access.