When using the RQM/RFT integration, you may run into a problem running RFT scripts from RQM when using Shared Location, which results in this error:
The script cannot be executed
You have this problem even though the RQM/RFT integration is set up correctly and the RFT script itself works fine.
RFT scripts run from RQM fail with the "The script cannot be executed" error, but the same scripts run from RFT itself work fine.
If you reconfigure the problem script to use Local instead of Shared Location, the script runs fine from RQM.
In the RQM adapter console, the RFT command used by RQM has a UNC or network path in the -datastore switch instead of a local path to a local temporary location.
This problem happens on machines that are missing a Microsoft VC++ Redistributable required by RFT's RQM adapter, which prevents a DLL file (rftrqmcomm.dll) from loading. The RQM adapter relies on rftrqmcomm.dll to get the temporary location where RQM copied the RFT scripts that were in the shared location. The -datastore switch of the RFT command used by RQM should never have a network path as its value -- if it does, that indicates a problem with the integration or the system hosting the RQM adapter.
How to determine whether you are having this problem
Enable debug logging for the RQM adapter. Then start the RQM adapter, reproduce the problem, and check the RFT command used by RQM -- if the -datastore switch has a network path, you might be having this problem. Proceed to the next step.
With the RQM adapter still running, start Process Explorer and use its Find command to search for rftrqmcomm.dll. If nothing is found, that indicates this DLL was not loaded by the RQM adapter, and that you are having this problem.
(If you cannot run Process Explorer but the test from #1 indicates you may be having this problem, go ahead and follow the steps to resolve the problem.)
Resolving this problem
The RQM adapter requires a new enough version of the 32-bit Microsoft Visual C++ 2005 Redistributable. This can be obtained here. Installing the missing redistributable will resolve this problem.
You might notice during import of test data using RQM Excel import utility that 'keywords' included in the RQM excel import excel sheet overwrites existing keywords stored in a RQM Project Area.This happens due to not meeting the required conditions while importing keywords as part of your test data in the XLS sheet.
Here is a sample to begin with using keyword import available along with the RQM Excel Import Utility Installation
Now lets take a look at what you could perform to over come this:
You can note the following points to avoid overwriting existing keywords during your XLS import :
1.The following parameter from the CFG file is critical while you export the 2nd time from the same sheet (with different Test script and Keywords).
This Worksheet name from the XLS has to be different each time. I started with "keyword1" and went on upto "keyword13" for various iterations to confirm this. I am unsure what is the significance of this Worksheet name causing the dependency. Checking with my developer.
2.Secondly the use of the "manual script" column in the keyword worksheet is critical as well ,and each time you have a new set of the Test script and Keywords, please have new set of Identifiers for the same.
The TS Column cause the creation and linking of the scripts to the respective keywords. I notice that re-use of the TS data , will not create the script and tags the existing scripts (created with previous iteration getting tagged with the new keywords.
3.Use of new worksheet name for "keywords" if re-using the same sheet with new data.
Every iteration of import with new test scripts , you need to have different Test script name, different Keyword Worksheet name and the TS ID's in Keyword Worksheet for next iteration.
method as being unable to create the Work Item of type review the case.
The likely cause in this case is that the Work Item type is null which means the process template the your teams using might not contain the Work item "Review" type defined.
You will need to check if you have the work item of Review type defined.
You may click on Manage Project Area > Work Items > Types and Attributes to check if the Work Item Review has been defined.
If the work item “Review type’ is not found , you will need to define the WI Review Type for all affected project areas by following the below steps:
1. Open an RTC client. Connect to the QM server by going to the Team Artifacts tab, then right-click on Repository Connections > New... Jazz Repository Connection, and then fill the requested information (Note: The URL should go as https://<hostname>:<port>/<qm-context>/). Click Ok.
2. Right-click on the newly created connection > Manage Connected Project Areas... and check the project area where the issue occurs.
3. Now the project area is shown. Right-click on it and click on "Open" or just double-click on it. The project area information tab will be opened. Click on the "Process Configuration" tab (shown at the bottom).
4. A tree showing all configuration options will be displayed at the left. Expand the Work Items item and click on Types and Attributes. A panel will appear showing all current work item types defined for this
QM project area.
5. Click on the "Add..." button. A dialog will appear showing 2 fields. Please fill those fields according to the following information:
The recent changes that happened to the server as pointed to us , was that the Database server was accidentally shutdown the day before and post that ,bringing up the Database server and QM application displays this error from RQM Diagnostics.
Note: If the topology is distributed and servers are located in varied timezone than the RQM Web UI user, you should look at the time where the RQM Server and other components are installed to analyse the logs.
IHS logs are huge in size and cannot be opened when IHS is up and running, hence you can copy the logs from IHS install directory and paste it else where to open in a enhanced text editor (Windos notepad has a limitation to open such huge files).
Monitor the server performance and if still continues to display the error, kindly report the error to IBM Middleware Client Support Team with the relevant log entries from each of above log files.
The investigation revealed the ETL job run to update the data-warehouse (Dw) was failing:
->Issue happens with any QM reports, or widgets added from QM Dashboard gathering report data from Dw.
->Issue reproducible with anyRQM ProjArea. You can try with JKE Banking Project Area.
You can hence check the following to overcome this Micro report error from the RQM Dashboard:
1. Check data-warehouse (Dw). setup if the ETL is updating the data in the right DB space.
2. If the database space for data-warehouse (Dw). is setup as same as jts tCheck the team server properties for QM or respective application where the error is reported.
Check for following entries in the teamserver.properties file:
The concept of integrating any of the IBM Rational applications is served using "Adapters".
In almost all cases the adapter component will be shipped with the respective product installations and you will see the specific plugins relative to this being present in the product installation directory.
The adapter can be run in three modes:
In GUI mode, from within the test workbench itself
From the command line
As a Windows service
Rational Test Workbench (RTW) integrates with Rational Quality Manager (RQM) to optimize the planning, authoring and execution of these functional test suites. With Rational Quality Manager, your business-side subject expert can quickly capture these important client-side scenarios and collaborate with developers and test automation engineers to help prioritize and identify process flows for automation.
Rational Quality Manager combines risk-based assessment and review workflows with work items that can be viewed by the tester directly in the Rational Test Workbench. Test execution status and test results are returned to Rational Quality Manager so stakeholders can have a common view of status and progress.
However if you are trying to connect the RQM adapter in-specific to RTW Eclipse Client (RTWec) / Rational Performance Tester (RPT) / Rational Functional Tester (RFT) v18.104.22.168 release, then you may notice that the adapter connection fails, displaying the certificate related problem. This behavior is not seen with any of the previous releases of RTWec / RPT / RFT.
It may be interesting to know if a common timeline for all project area's in IBM Collaborative Lifecycle Management tool is possible.
The production level scenario is that a team has Requirements Management (RNDG), Configuration & Change Management (CCM) and Quality management (RQM) activities, using LPA. But the fact is that you have to create separate timeline/iteration schedule for all 3 project areas, and then remember to update all copies whenever you would make a change. This can be of tedious if your development activities demand timelines for all 3 phases to be the same.
Now let me take you through the current behavior of timeline/iteration usage in all 3 components for IBM Collaborative Lifecycle Management (CLM).
Requirements Management using Rational DOORS Next Generation (RNDG) :
There is no support for timelines in RDNG.
RDNG does however have the concept of baselines that can be used to snapshot the state of artifacts, and with the introduction of DNG 6.0, there is now support for configuration management
You might want to take a look here for the new configuration management support: Administering configurations
The Test Automation (Execution) adapter receives requests from RQM and then runs tests on the machine where the test tool is installed.
Before you try to run a test against a running Execution adapter, you can verify the adapter state on the quality management application on the RQM UI as explained below:
1. Navigate to the RQM project area, click on Execution > Adapter Console
2. The adapter's connected to this project area and the status
Note : Make sure that the adapter status is green before you run the test.
Is it possible to query adapters from outside of the RQM UI? Yes, it is possible to achieve it using RQM REST APIs; here is how...
1. Query execution adapters connected to an RQM project area using REST API:
Note : Replace the entriesserver, port, RQM Project Alias Nameand Project Area ID with correct values. Port value “443” is default for https The REST API queries can be conveniently performed using a REST client or a similar interface, other than a normal browser.
Step (1) Get the “Alias” name of the RQM project area using the link as below on browser:
Step (2) Use the link as below on the browser to get the Adapter List for the project area
2. Query the status of the execution adapter connected to an RQM project area using REST API:
Step (1) Get the “Project Area ID” of the RQM project area using the link as below on browser:
Step (2) Use the link as below on the browser to get the Adapter List for the project area
The procedure explained above can be used as input to an external application to consume the adapter query.
11/13/2015 5:40:54 AM: ERROR: <Unknown Caller Context>: The remote server returned an error: (400) Bad Request.
11/13/2015 5:40:54 AM: EXCEPTION: : The remote server returned an error: (400) Bad Request.
Debug log file:
Log file location : C:\Users\IBM_ADMIN\AppData\Roaming\Mso2Rqm\Mso2Rqm_Debug.log The uploaded content does not consist of well-formed XML or does not match the XML schema for testscript</ns2:message><ns2:trace>javax.xml.bind.UnmarshalException
org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1d) was found in the element content of the document.
11/17/2015 11:58:05 AM: sending testscript0 named US40.2-BU_Due_Date_Triggers-Assign_to_group
11/17/2015 11:58:08 AM: ERROR: <Unknown Caller Context>: RQMConnector: PutToServer - Error putting resource: https://clm404:9443/qm/xxx/service/xxx/resources/TCS%2bTesting/testscript/US40.2-BU_Due_Date_Triggers-Assign_to_group
11/17/2015 11:58:08 AM: ERROR: <Unknown Caller Context>: The remote server returned an error: (400) Bad Request.
11/17/2015 11:58:08 AM: EXCEPTION: : The remote server returned an error: (400) Bad Request.
11/17/2015 11:58:08 AM: at System.Net.HttpWebRequest.GetResponse() at Mso2Rqm_Common.RQMConnector.PutToServer(String url, String data)
Here's why this could be happening:
The error recorded here attributed to a Invalid Character inline with the plain text failing to get exported.
Here's how you can find the character:
1.Export the Excel to XML (use Export to File option).
2.Paste the XML into the POSTER utility and you can see any such invalid character’s and edit it accordingly.
Now fix the problem!
1.Copy the Excel Cell contents to a text editor and retype the erroneous text again and paste it back to the Excel cell.
2.Attempt re-import the script again.
You might be familiar with Rational Quality Manager (RQM) REST API's to query your artifacts. TheRQM Reportable REST APIallows a user to perform CRUD type operations on test resources via XML sequences to the RQM server. This article describes about how to manipulate resources like (test case, test execution record, test results, etc..) in RQM using REST API
CFG files are used to import data into Rational Quality Manager. The file must be in a specific format for the import to work properly. Here is a sample CFG file created for associating a Single Testplan to Multiple Testcases. Also, each Testcase is associated with multiple Testscripts, which will allow you to use with IBM Rational Quality Manager (RQM) Excel Import utility.
// this configuration file will create a single test case from the defined cells and link to all
// test scripts in the same worksheet
// since we aren't defining an ID to use, the tool will create one based on the excel worksheet
// and workbook names
// We want to start looking for scripts after row 8
// the literal "execution" will be put into the step type tag, so all steps will be of type execution
// a new script starts when we encounter an empty row
// we want to use the data we got for each test script to create a test case
testcase.XLSWorksheetID="Testcase1" : "Testcase2"
// test case defined with definite cell locations
//Config for Testplan
You may come across situation where you do not want a user in your Project Area to view data in a particular stream.
Example, a user logged in to the Project area and can switch to any stream and view the data.Would it be possible to restrict a user from viewing some specific streams in a Project Area in IBM Rational Quality Manager ?
Configuration management is a new CLM capability and right now there is no access control on the streams in RQM.
Last week saw the release of version 6.0 for a few different products... here's three blog posts from the Jazz team blog covering what's new in DOORS Next generation, Rational Quality Manager, and Reporting for Collaborative Lifecycle Management!
What’s new in DOORS Next Generation 6.0? - This release could well be introducing the most fundamental function into a requirements management tool since RM systems began. While we continue our drive with usability and productivity we are also providing support for requirements configuration management, built from the ground up as part of the native tool, rather than simply integrating to an external CM system. [Read more]
What’s new in Rational Quality Manager 6.0? - IBM Rational Quality Manager (RQM) 6.0 brings both incremental improvements over v5 and a completely new dimension to managing test artifacts. On the incremental improvements front, the team has done a great job to continue to work closely with our customers to further improve the user experience on specific areas such as dashboard widgets or collaboration. At the same time, v6.0 introduces the support of configuration management for test artifacts, linked to other domains such as requirements or design, and contributing to the notion of global configurations across our Collaborative Lifecycle Management (CLM) solution. This version marks the beginning of a completely new set of capabilities that empower users to do parallel development and test, and to reuse artifacts in an effective way. [Read more]
What’s new in Reporting for Collaborative Lifecycle Management 6.0- It’s been an exciting time here for us in the Reporting team and we’re especially proud of the tremendous progress that’s been made to provide you with an easy-to-use, cross-project, cross-tool reporting solution. We’ve built on the foundation of the Jazz Reporting Service and Data Collection component in 5.0 that many of you have helped shape to bring several new advancements in reporting in Collaborative Lifecycle Management (CLM) 6.0. I encourage you to give the latest release a try and give us feedback! [Read more]
In RQM, if you rename the execution states from the Manage project properties area >> Execution States, these renamed execution states do not appear in the relevant reporting sections, which is misleading.
For Example, look at the below screenshot where few execution states are renamed.
The generated report, for example "TSER Status using Test Case count" does not show these renamed execution states
STEPS TO REPRODUCE:
1. Navigate to Manage Project Properties → Execution States and rename the existing Execution state Permanently Failed to Unavailable.
2. Save the Changes
3. Log out and log back in
4. Create a Test Suite with a few Test Cases
5. Run the Test Suite. Set each of the Test Case results to Unavailable
6. Browse the TCER's and verify the results are set to Unavailable
7. Run the “TSER using Test Case Count (Live)” Report".
8. Note that the column names and Graphs do not reflect the modifications done to the execution states
In a very typical scenario, To create a test, many testers currently sit at a PC and alternate between completing an action in the application under test and writing the step on a notepad. When the test is complete on paper, the tester (or in some cases an administrative assistant for the testing group) types the steps into a standard test template, frequently using either Microsoft Word or Microsoft Excel. Following this procedure, a single manual test is essentially written twice.
Eliminating the need to write each test twice can save you time for other testing.
In addition to writing tests twice, much time is spent adapting existing tests for similar new tests. For example, a tester might create a test to log into the application under test as an administrator, and then adapt that test to log into the application under test as a regular user. This adaptation typically takes one of two forms:
• Open the existing test, edit steps as needed, and save the test with a new filename.
• Open a new test template, copy steps from the existing test, edit steps as needed, and save the new test.
Reducing duplication among many tests reduces the time you spend maintaining test scripts.
Testers typically receive many new software builds during a development cycle, often at an increasingly rapid rate toward the end of the cycle.
When a build contains a new feature or a fix that requires modifying the steps of a test, all of the tests that relate to the new feature or fix must be updated to reflect the change in the application under test. Although this update process is not difficult to manage when only a few tests require updating, when dozens (or hundreds) of tests are affected by changes to a commonly used area of the application under test, such as a login screen, updating can be very time-consuming. Eliminating or reducing the work that is required to keep many tests up to date can save you time for additional testing.
As you increase the efficiency of your testing effort, you can use the saved time to conduct additional tests. Rational Quality Manager can help you work more efficiently in each of the testing activities:
• Creating tests: Rational Quality Manager helps you to manage reusable content and use it in similar tests. As a result, you spend less time authoring tests.
• Running tests: Rational Quality Manager associates text to be typed in the application under test with an execution step. Rational Quality Manager also associates verification text with a test step, and then compares the comparison. Rational Quality Manager provides test data variables so that you can define a test once and run it many times to accommodate different data input values. These features save you time typing in the application under test, comparing actual to expected results, and testing different data values.
• Reporting test results: Rational Quality Manager provides customizable reports that reflect test result data from all phases of the project. These reports save time that you would have spent manually tabulating test results for reporting.
• Maintaining tests: Rational Quality Manager reduces the amount of required test maintenance by storing reusable content only once. As a result, you spend less time updating many similar tests.
Under IBM Rational Quality Manager v4.0.3 , say you have added a few execution variables and these variables are assigned to Test Steps for a given Test Case.
Create a new Test Script and added an Execution Variable <Save>
Add an Execution variable to a few steps <Save>
Changed the state from Draft to Ready for Review <Save>
Changed the state from Ready for Review to Approve <Save>
Changed the state from Approve to ReOpen <Save>
At this point the History section of the Manual Test Script does display the “removed” entry for each of the Execution Variables.
For example: After transitioning the Script state from Approved to Draft (i.e. using the 'reopen' option) the history does include 'Removed' entries corresponding to the Execution Variables (as seen below)
From the UI perspective; the Execution Variables are still associated with each of the steps; however, the Execution Variables View is empty. So basically there are two issues here.
• The History displaying the Removed entry
• The Execution Variables View being empty
This behavior is only specific to RQM v4.0.3 and is not reproducible under later releases of RQM. So as a work-around in RQM v4.0.3, you are forced to re-add the execution variables to the Test Steps. Note that this is a User Interface (UI) problem and does not break the functionality.
IBM® Rational® Quality Manager provides extensible APIs that enable test-automation tools from various industries to be integrated into the Rational Collaborative Lifecycle Management (CLM) environment. These APIs make the automation tools' capabilities available in Rational Quality Manager, providing a rich user experience. After an integration is built, it goes through a rigorous validation process and then is available to users.
ETAS LABCAR-AUTOMATION (LCA), an automated testing tool widely used in the automotive industry, now integrates with Rational Quality Manager through these extensible APIs. MicroGenesis, an IBM business partner, built this one-of-a-kind integration, enabling users from the systems space to leverage the power of collaboration and the enhanced traceability of the CLM environment. (All copyrights and trademarks related to LABCAR-AUTOMATION/LCA are owned by ETAS.)
Stéphane Leroy (Unleash the Labs CLM, IBM Software Engineer) has created a wonderfully simple table to outline the Test Lab managementcapabilities of IBM Rational Quality Manager (RQM). The table shown below and discussed further on his blogshould help speed up your understanding of the currently available capabilities in RQM, and facilitate the decision of the mapping between your own testing shop terminology and RQM terminologies:
Under IBM Rational Quality manager (RQM) v3.x release onwards, during the course of creating a new defect work item, you are allowed to select the record type. Below are 2 such scenarios where the record types differ between older (2.x) and newer versions (3.x onwards) of RQM.
A particular difference between the integrations of RQM 2.x and CQ and RQM 4.x and CQ.
Integration in 2.x with CQ 8.x:
- During script execution, when you click on "Add a new defect", it directly opens the Defect Record form specific to CQ.
However when you setup the Integration of RQM v4.x with CQ 8.x:
- During script execution, when you click on "Add a new defect", it opens the dialog box where you can select the CQ Record type. RQM should only link to CQ defect. However, here you are able to choose any option out of the list of record types and save it. Even have it linked to the test script execution. So, you are able to link any record type to the test script execution.
The functionality to select record types ( RQM/CQ integration) was added via RFE 25717in version 4.0.1; this is the current default behavior (i.e. functioning as intended).
8) For property "image"
To add an image we first need to find the value/location of image. To find this information, add a Headline Widget to any Dashboard. Edit the settings, now select the image you want add from drop down. Right click on Image and select "Copy Image Location".
Paste the copied Image Location on a notepad for editing.
The URL that gets copied will look something like below example:
Now just copy the text after "path=" from above copied Image Location. For example below:
Under IBM Rational Quality Managerv4.0.3, When adding default reporting widgets to RQM dashboard you might encounter the following error:
In order to validate if these default reports are working fine, you may execute the etl jobs for QM applications. However in this scenario, you could notice that the etl job execution was showing no specific errors pertaining to these reports or widgets. You can navigate to the QM and ETL jobs to find if any error gets logged. In most of the cases, you can find an error message :
"The "com.ibm.rqm.reports.service.fragment" bundle could not be resolved."
This fragment is the one that extends the foundation reporting functionality to use specific tools designed in RQM. It acts like a "bridge" between foundation and RQM reporting functions. Since the bundle couldn't be loaded, the reporting functionality in RQM is not working as expected.
There might be several reason for the above error:
It could be that the bundle was removed
It could be that the file is corrupted
It could be a case where the file was renamed.
To confirm , you can navigate to this URL to see if he bundles are activated for the application.On the left pane of the window, click on Internal Tools >> Component Status. All the components listed there are expected to be displayed with green status. Pay special attention to the com.ibm.rqm.reporting section.
Since the bundle that acts as a bridge between the BIRT engine and specific RQM reporting functions can't be resolved, you might encounter such errors. The primary reason could be that the .jar files (com.ibm.rqm.reports.service.fragment_4.0.300.v20130417_0652.jarANDcom.ibm.rqm.reports.service_4.0.300.v20130516_2315.jar) maybe corrupt or maybe it was moved to a part of the disk that is having issues.
First thing you could try is replacing the problematic bundle mentioned above with a clean one while troubleshooting advances, as it is easy and may actually fix the issue. Get a copy of the above mentioned .jar files from a fresh installation of similar version of RQM and perform the below steps.
This blog entry is to provide suggestions to users who are surprised at incorrect / mismatched date attribute (TIMESTAMP) values seen in RQM artifacts while the data is exported from Excel using the RQM Excel Exporter.
In most cases, the excel export will succeed but you might see that the "date attribute" field, is not in accordance with what is exported.
The dateTime (Date/Time which translates to TIMESTAMP) values in Rational Quality Manager artifacts like Test Case, Test Plans and execution artifacts like Test Case Execution Record undergo translation when the data is coming from excel through the "Export to Repository" option in the RQMExcelWordImporter plugin.
A dateTime value passed through the excel sheet should follow a format yyyy-mm-ddThh:mm:ss+/-hh:mm.
RQM Client and RQM Server in same time zone: If the RQM client (where excel is used) and server are on machines in the same time zone? the TIMESTAMP value specified in the sheet is exported into RQM as is.
RQM Client and RQM Server in different time zone: If the RQM client and server are on different machines? the TIMESTAMP value specified in the sheet is converted to the time on the RQM server and used. to avoid this (i.e., to ensure the TIMESTAMP value is as per client time zone) you should use dateTime (TIMESTAMP) string as 2014-06-29T12:00:00+/-hh:mm
For example: 2014-06-29T12:00:00+05:30 provided that the excel exporter is on a machine which is in India (+05:30) time zone.
If the excel exporter is on a machine in a different time zone, replace the timezone string highlighted above with the relevant value.
Rational Quality Manager v4.x: Best Practices in Manual Testing- In this video presentation, Dennis Schultz and Joshua Burton take you through an introduction to manual testing with Rational Quality Manager v4, and beyond, including test case designs, recording manual tests, and augmenting manual tests with automation.
And don't miss the next two videos with presentations based on content from last year's IBM Innovate!
Our folks were busy the last few weeks of 2013 pulling together some new educational material to help you better understand how you can use test case execution records with IBM Rational Quality Manager (RQM). A new six part video series was published to help explain how you can use test case execution records to plan, execute, and report on testing activities.
Rational Quality Manager v4.0.4: Test Case Execution Records
0:14 - Integration with Build Forge 3:45 - Continuous integration servers working with UrbanCode Deploy 4:40 - Example Ant tasks to add different capabilities 8:53 - Verification of live systems 9:51 - Integration with RQM - prechecks 12:30 - Integration with RQM - steps
Here's the most recent list of the latest and greatest downloads which have gone live from Rational Support since August 28th! These links below are provided to help you find the fixes you need in order to stay up to date and successful with your Rational products.... Plus, don't forget to check out the downloads tag to see any of the fixes you may have previously missed: