Hi,
you may do that with compilations of tests within a diagram or a package.
My favorite condition is the following:
Create a Package for each Test plan.
Add a Diagram into the Package.
Move all Test case elements into this package.
On Diagram options "inclde all Elements from that diagram into the report"
Do not show the diagram within the report
Create a test plan template for the specific need.
One
Problem: Each test-case-element is available ONCE, but you can overwrite it.
You ahould use the audit trail function for using it AND writing the device under test identifier into the result.
Regards
Stefan
Stefan,
Where is the option "inclde all Elements from that diagram into the report"?
Why not showing the diagrams? Why creating a test plan template?
Where is the audit trail function?
What do you mean by "writing the device under test identifier into the result"
Sorry if my questions look dumb to you, I just don't understand your way to proceed.
Hi
When i create the test plans and test specifications within a terxtual way, i don't like the diagrams beeing included, because they are just ways of view. Therefore I exclude them.
The option "include all elements" is on the "right-click into the diagram -->diagram options"
The test plan template is a rtf document template which is used for managing tests and test setups. It will be the very first step within a testing framework, the main definition and scope. And to ensure a quick generation, I usually creat a template for.
The audit trail is in "Project-->Auditing". a really valueable feature.
The device under test, the correct reference for a single device or version is usually not handled by enterprise architect in a usable way. to have the information bound to the test in the Testing window, i use the device-identifier within the test result. The device is hand-written in there and with that approach i can manage variants and updates with regression and problem solution processes.