filter tests in RTF documents

[bEAr]

i have a list of all system tests of my ea-modell in my rtf-document generated with the RTF-editor. now the half of the tests pass and some new tests are added in the model. how do i filter all the "Pass" tests when i generate the rtf-document? i want to see only the "Not Run" tests in my document.

What i get is:

Test1	"Pass"
Test2	"Not Run"

What i want is:

Test2

"Not Run"

bEAr

[«Midnight»]

Perhaps you can change the status of those tests that have passed - you might also change those that have failed, to differentiate them from yet to be run tests. You might have to add some new status types, but that's easy to do, and you can color code them to make this easier to view.

You'll have to check whether you can filter or sort by status, but I suspect you can. Regardless, the colors would help to pick out each group.

David

[Eve]

Currently there isn't any mechanism for filtering features of elements (such as test cases).  We are currently investigating the best way to achieve this.

[Jan ´Bary´ Glas]

That is very nice to hear, simon. This feature is requested for very long. You probably will skimm all the relevant threads before implementing it. I remember a lot of nice thoughts on this topic.

[Tonu]

I am also happy to hear abut the potential filtering in RTF output.

A hint to bEAr. We have managed to generate filtered documents using automation. We have an add-on, that makes a new package, then, based on filtering condition, copies all relevant elements to this package. After that we can generated document using standard document generator. This allows us to make documents answering questions
"Show all requirements related to selected actors and all elements connected to those requirements using <<trace>> dependency" or "output all requirements related to the selected use-cases" or "all requirements with certain priority"  ...

Of course, it would be possible to make a script that writes data directly to RTF document. However, this means that you need to make also all formatting yourself ...
Also, the advantage of "temporary package" is the ability to change grouping of elements (by making sub-packages) before me generating documentation.

Tonu

[mchiuminatto]

Simon

When you estimate this feature will be released?, to take a decision if we build an add-in or not.

[mchiuminatto]

A suggestion

You can use the Rational SoDA approach, that is filtering by  element properties, for instance you can document use case connectors and the elements associated to it. You right click the element node (from the elements tree) to show a context menu that includes a Filter option. This option opens a dialog box where you can select a property and a constant value to filter to; for instance Type='Actor'. This way you will be able to document the actors related to the use case.