레이블이 rqm인 게시물을 표시합니다. 모든 게시물 표시
레이블이 rqm인 게시물을 표시합니다. 모든 게시물 표시

2012년 1월 6일 금요일

RQM - DOORS Integration Architecture

as-is




to-be



-

2011년 12월 27일 화요일

RQM Utilities

1. RQM URL Utility
https://jazz.net/wiki/bin/view/Main/RQMURLUtility (includes Java source!)


 "RQMUrlUtility" is a sample utility that is not intended for production use and performs actions similar to the cURL utility. This utility is a stand alone Java command line application that users can use as the basis of their development efforts to GET and PUT/POST records to an RQM server via the  RQM Reportable REST API. It allows a user to upload/download an attachment or upload/download/delete an artifact to/from the RQM Server and its goal is to provide the sample code that grants the insight to a toolsmith.
The RQM Rest API allows a user to perform CRUD type operations via XML sequences to the RQM server. This sample will provide a code that exposes those CRUD operations for GET, PUT, POST and DELETE of RQM records via HTTPS. The term CRUD stands for Create, Read, Update, Delete which corresponds to the basic database operations.


2. RQM Excel Word Importer
https://jazz.net/wiki/bin/view/Main/RQMExcelWordImporter

Microsoft Excel and Word are popular document formats used by many test organizations to author, store and maintain their test assets. These document formats are easy to use and widely available. RQM provides a utility that allows the Excel and Word applications to export test data to RQM via HTTP. Using this utility these applications can directly export test artifacts as XML file(s) in a well-defined XML format. This XML file(s) can be imported into RQM using the RQM Reportable REST API.

 The Excel and Word add-ins provide new features to these applications. The add-ins provide the following main features :
  • Export the document(s) as XML files on the local file system (‘Export to File’)
  • Export the document(s) onto the RQM repository, creating corresponding test artifacts on the RQM side (‘Export to Repository’) 
3. RQM Copy Utility
https://jazz.net/wiki/bin/view/Main/RQMCopyUtility (includes Java source!)

The RQM Copy Utility is an open-source stand-alone Java application used to copy RQM artifacts such as Test Plans, Test Cases, Lab Resources, etc. The destination of the copy can be the same Project Area, a different Project Area in the same RQM repository, or a different repository/server altogether. The primary goal of the copy would be to share common artifacts across projects and teams. It is not intended as a back-up utility. Please note: the RQM Copy Utility only works with RQM 2.0, or later. The utility will do a full copy of all supported artifacts by default. The copy utility can be directed to only copy artifacts of a given type (such as testplan, testcase). When copying artifacts of given type(s), the default behavior will be to do a "deep copy", where all referenced artifacts are copied as well. A single artifact can be copied by specifying its type and id.

The RQM Copy Utility is built on the RQM Reportable REST API, which is not compatible between Rational Quality Manager versions.

4. RQM Command Line Execution Tool
https://jazz.net/wiki/bin/view/Main/RQMExecutionTool

The RQM Command Line Execution Tool is compatible only to supported version of Rational Quality Manager. It works RQM 4.0 onwards.

The RQM Execution Utility is an stand-alone application used to execute Test Case Execution Record (TCER) and Test Suite Execution Record (TSER). The primary goal of the tool would be to be able to execute test from command line for automation framework outside the RQM. The tool can either trigger execution and exit or exit till execution completes


-

RQM Reportable REST API

https://jazz.net/wiki/bin/view/Main/RqmApi
참조 : OLSC-QM 스펙 ( http://open-services.net/bin/view/Main/QmHome )




Resource Exposed in the UI as GET PUT POST DELETE LOCK UNLOCK SNAPSHOT PROPFIND
adapter N/A X X X X



attachment6 Attachment X X X




builddefinition Build Definition X X X




buildrecord Build Record X X X




catalog N/A X X





category3 Category X X X




categoryType3 Category Type X X X




configuration Test Environment X X X X



contributor User X






datapool Test Data X X X X



executionresult Execution Result X X X X X X

executionsequence Execution Schedule X X X X



jobscheduler3 Job Scheduler X X X




executionsequenceresult Execution Schedule Result X X X X



executionworkitem Test Execution Record X X X X



job Automation X

X



jobresult N/A X






keyword Keyword X X X X



labresource Lab Resource X X X X



labresourceattribute N/A X X





objective N/A X X





projects1 Project X






remotescript Test Script (type: non-manual) X X X X X4 X4

request Request X X X X



requirement1, 2 Requirement X X X X



reservation Reservation X X X X



resourcegroup Lab Resource Group X X X X



suiteexecutionrecord3 Test Suite Execution Record X X X X X5 X5

tasks Execution Request or Adapter Task (see Execution Console) X X X




teamarea1 Team Area X






template Template X X X X



testcase Test Case X X X X X X X X
testcell Test Cell X X X X



testphase Test Schedule (see Test Plan editor) X X X X



testplan Test Plan X X X X X X X X
testscript Test Script (type: manual) X X X X X X X X
testsuite Test Suite X X X X X4 X4 X X
testsuitelog Test Suite Log X X X X X4 X4

workitem1 Defect, Task X







1 Support to be deprecated in a future release since support will be provided by Collaborative Lifecycle Management (CLM) 2011, specifically Jazz Foundation, Rational Team Concert (see Rational Team Concert SDK 3.0), Rational Quality Manager, and Rational Requirements Composer.
2 When Rational Quality Manager requirements reference resources in Rational Requirements Composer, the following configuration is required:

  1. The Quality Management project area in Rational Quality Manager must have a "uses and requirements" association to a Requirements Management project area in Rational Requirements Composer. Note, multiple Quality Management project areas can be associated with a single Requirements Management project area.
  2. Set the following Requirement ( com.ibm.rqm.requirement.service.internal.RequirementService) advanced server configuration properties (see Configuring advanced properties in the Collaborative Lifecycle Management 3.0.1 Information Center):

  • Requirements Composer User Name
  • Requirements Composer User Password
3 Rational Quality Manager 3.0.1 or later.
4 Rational Quality Manager 3.0.1.1 or later.
5 Locks and unlocks the test suite execution record's current test suite log.
6 Attachments have the following unique characteristics:

  • Attachments are binary resources.
  • Attachments do not have a resource schema.
  • Attachment feeds do not have a feed schema.
  • Attachment HTTP GET request Accept header is ignored.
  • Attachment HTTP PUT/POST request Content-Type header must be application/octet-stream.
  • Attachment HTTP response headers contain the attachment file name, size, and last modified date/time.
  • Attachment HTTP requests cannot be invoked using Poster (see Common Usage Scenarios for other HTTP client options). 

- 참조

Debugging Tips Using the RQM API (https://jazz.net/wiki/bin/view/Main/RQMAPIDebugging)
Required: A HTTP client is required to invoke the Reportable REST API. Choices include:

  • Using the RQM URL Utility.
  • Using Poster from a Mozilla Firefox browser. The Mozilla Firefox browser must be authenticated with the Rational Quality Manager server.
  • Writing a custom Jazz client. The Jazz client must be authenticated with the Rational Quality Manager server. As an example, see the Jazz client in the RQM URL Utility and/or RQM Copy Utility source. 

https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItemAPIv2