How RQM helps in generating RPT reports beyond what RPT does

The RPT adapter for RQM will attach a static HTML report back into RQM once the run completes. The report(s) will be the same as the default report(s) that are open automatically when you run the test/schedule directly from RPT. Which report(s) depend on the protocol for the test/schedule you are running. So for HTTP you'll get the default HTTP performance report. For SOA test the RQM results will contain the default SOA report, and so on.

The default report is defined as a preference inside RPT via ( Windows->Preferences->Test->Performance Test Reports->Default Report). If you want the RQM result to contain more or different information then the default RPT reports, then use the RPT workbench to define a custom report and change the default report preference to your custom report. From then on, the RQM results for RPT runs will contain your custom report.

In addition to the default report(s), starting in release RPT 8.1 the performance requirements report for the last defined user stage is also attached when you run a performance schedule. The pass/failed verdict of the schedule's performance requirements is what is used to indicate if the RQM execution result passed or failed. If no performance requirements are defined, the RQM result will be inconclusive and will have to be set manually.