0

Miriam Kilav (15●1●6) | asked Jan 15 '17, 3:22 p.m. retagged Jan 20 '17, 5:07 a.m. by Minakshi Jaint (511●3) We are in a stage of design for moving our tests and test suites to RQM.  We have a question regarding the right structure of tests and test suites. Our use case is: we have a cycle that runs every night (and is called "nightly") and is triggered by Jenkins. This cycle contains 5 test lists. Each one for one environment. (e.g.: one with X tests, running in Linux and one with Y tests, for Windows7, one with Z tests, for Windows8, etc.). So from the documentation i understood that each test list called test suite in RQM. I can create the test suites but I don't find a way to group all those test suites to one object (test plan? test suite? scheduled execution?). My requirement is that Jenkins will trigger (via REST API) ONE object and not the 5 test suites one after another.  I'd like to have this grouping for two reasons: 1. To ease the process of nightly triggering (one click and not 5 clicks) 2. We would like to see indicators and trends of this nightly so we need a way to group the results somehow If that important: we will probably use test cell for lab management. We'd like RQM to provide us the machines on run time.

One answer

---

Register or log in to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.