How can the iteration of a TSER be used for naming the corresponding TCERs?

Stefan Greim (13●1●3) | asked May 19 '15, 1:42 p.m.
edited May 19 '15, 2:08 p.m.

When executing a Testsuite the first time, executional records for all included Testcases are created automatically by RQM. When excecuting Testsuites for different Iterations / Testplans later, the corresponding TSERs will all use the same TCERs, since the Iteration is not used for naming those TCERs.

It's impossible to track Tescase results like this, cause the last result is permanently overwritten by the execution of other (irrelevant) TSERs. This seems to be a major bug in RQM.

When creating a TSER or TCER manually, one can make them unique by using the selected iteration as a suffix for its name. How can an Iteration be used for naming TCERs, which are automatically created during the first TSER execution?

Accepted answer

permanent link

Don Yang (7.6k●21●97●134) | answered May 19 '15, 11:54 p.m.

I don't think you can do that(using iteration as part of TCER naming) without creating them manually.
However, if you are at RQM4.0.6 or later, RQM has a new feature [Automatically create test case execution records whenever a test suite execution record is created]. You can simply create various TSERs beforehand for different iterations/testplans, which will create TCERs for each iterations as a result even though test case is the same and TCER name is the same(you will see multiple same name of TCERs for different iterations) in TCER view.
So when you run each TSER, it will have its own set of TCERs(for different iteration) and you won't have the concern that the result will be mixed up.

Stefan Greim selected this answer as the correct answer

Comments

Stefan Greim commented May 20 '15, 7:06 a.m.

Thx for your answer! It behaves as you described it indeed. We had problems here yesterday with the visibility of some TCERs and since most of the widgets don't provide a live view, the confusion increased ;)

Still would be nice to have unique names for automatically created TCERs -> Enh Request.

It's all about the answers!

Related questions

How can the iteration of a TSER be used for naming the corresponding TCERs?

Accepted answer

Your answer