Manual testing in EA

[Monsieur]

Dear Sparxians,

Ok, here is my daily question about EA:
How can we conduct test in EA, not code testing as shown in every webinar but more as in IBM Rational Quality Manager or in Hewlett Packard Quality Center?

So I will need to have a test catalogue (package) where I have all the tests (obj).
And here is my deal, i want to define a test plan (obj?diag?) which is a selection of tests and I want to conduct only the tests that are contain in a test plan+ the result of execution is contain at testplan level since the test can be reuse an infinite number of time and the test plan will be conducted once

1 test is only once in the test catalogue
1 testplan contain 1 or more tests
The testplan contain the result of the test execution

Since I am not clear at all here is a picture
http://snag.gy/4XHDc.jpg
(I used scenario since it seems to work, but that solution bother me a little since I don’t have the scenario imported inside the testplan object but only in the testing element tool)

Bonus questions:
-Can we do something alike adding one more level of granularity (the step of the test indeed) and work on a level 2 deep relationship? i don't find any way to use a level 2 deep relationship in EA (nor in matrix or ...)
-If I execute a test more than once, where can I find an history of results? (date xxxx, failed; date xxx, pass)

Thank you community!

[Gary]

Here is how we do it.
1) Create tescase elements in a testing package.
2) Add tests to the testcases by an appropriate grouping, for example have all the startup test in a startup testcase.
3) Create an activity with the same name as the individual tests in a testcase. i.e. test1_startup_pass, test2_startup_fail
4) Under the activities create sequence or state or activity diagrams to explain the test scenario. Create a block/class diagram to explain the test setup and connections between equipment.
5) In the test descriptions in the test case explain that the test is documented in the activity.
6) Create a test document template with a results and tester and date sign off section.
7) Export the document and give to the tester to run. have them fill in the result n the document and sign and date it.
When the testing is finished fill in the results tab of the test in the testcase.
9) Have roles with security so that the run by and checked by fields cannot be the same person.
10) Scan the tester completed document.
11) Attach to the testcase as a document artifact.

Each time the test is run redo steps 8, 10 and 11. This will mean that the latest result is documented in the testcase and the historical results are documented in the attached document artifacts as you attach one artifact per run.

Gary

[Stefan Bolleininger]

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

[Monsieur]

Here is how we do it.
1) Create tescase elements in a testing package.
2) Add tests to the testcases by an appropriate grouping, for example have all the startup test in a startup testcase.
3) Create an activity with the same name as the individual tests in a testcase. i.e. test1_startup_pass, test2_startup_fail
4) Under the activities create sequence or state or activity diagrams to explain the test scenario. Create a block/class diagram to explain the test setup and connections between equipment.
5) In the test descriptions in the test case explain that the test is documented in the activity.
6) Create a test document template with a results and tester and date sign off section.
7) Export the document and give to the tester to run. have them fill in the result n the document and sign and date it.
When the testing is finished fill in the results tab of the test in the testcase.
9) Have roles with security so that the run by and checked by fields cannot be the same person.
10) Scan the tester completed document.
11) Attach to the testcase as a document artifact.

Each time the test is run redo steps 8, 10 and 11. This will mean that the latest result is documented in the testcase and the historical results are documented in the attached document artifacts as you attach one artifact per run.

Gary

Thanks Gary for your answer
I do need a few clarification,
You create an activity object which is a copy of the step and use it in your test plan (so that your test doesn't have to bear the result I suppose)
You use an Activity diagram and order the activities(copy of steps) to show the step order.
You generate a document, then conduct your tests out(?) of EA, then fill the results in EA (where exactly? i don't get where you fill your result) and place a copy of the document in a document artifact(?)

[Monsieur]

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.

[Gary]

Thanks Gary for your answer
I do need a few clarification,
You create an activity object which is a copy of the step and use it in your test plan (so that your test doesn't have to bear the result I suppose)
You use an Activity diagram and order the activities(copy of steps) to show the step order.
You generate a document, then conduct your tests out(?) of EA, then fill the results in EA (where exactly? i don't get where you fill your result) and place a copy of the document in a document artifact(?)

We create the activity becauseit is then easy to create an activity diagram to order the tests and each activity serves as place to put the test description diagram underneath. This helps with test document generation.
The test results are filled in on the testing tab.
Press Alt+3 then select an individual test in a test case and then, for instance, the scenario tab there are then four tabs to select from Description, Input, Acceptance Criteria and Result.
We create a test document to give to the tester. He does not sit there with a copy of EA running on a machine so he has a document. This means we can give a tester only the information on the tests he is to undertake not the whole design or the whole testing campaign.

Gary

[Paul Lotz]

I'm not sure if this is quite what you want, but we used it on a previous project and I intend to incorporate it on my new project:
http://catchsoftware.com/testing-tools/enterprise-tester

[Monsieur]

I'm not sure if this is quite what you want, but we used it on a previous project and I intend to incorporate it on my new project:
http://catchsoftware.com/testing-tools/enterprise-tester

Hi Paul,

Not sure to understand. Is that an other software (web based) with an EA sync?
It looks like it's for code/script testing, which is a functionality I don’t need since I use EA to do system engineering.

thanks anyway.

[Monsieur]

Thanks Gary for your answer
I do need a few clarification,
You create an activity object which is a copy of the step and use it in your test plan (so that your test doesn't have to bear the result I suppose)
You use an Activity diagram and order the activities(copy of steps) to show the step order.
You generate a document, then conduct your tests out(?) of EA, then fill the results in EA (where exactly? i don't get where you fill your result) and place a copy of the document in a document artifact(?)

We create the activity becauseit is then easy to create an activity diagram to order the tests and each activity serves as place to put the test description diagram underneath. This helps with test document generation.
The test results are filled in on the testing tab.
Press Alt+3 then select an individual test in a test case and then, for instance, the scenario tab there are then four tabs to select from Description, Input, Acceptance Criteria and Result.
We create a test document to give to the tester. He does not sit there with a copy of EA running on a machine so he has a document. This means we can give a tester only the information on the tests he is to undertake not the whole design or the whole testing campaign.

Gary

Gary,
I have to admit, your way to do it seems pretty good. [smiley=thumbsup.gif] [smiley=thumbsup.gif] [smiley=thumbsup.gif] [smiley=thumbup.gif]
Did you develop some scripting in order to copy automaticatly the test as an activity and copy all the custom field?
Where did you place your new package/diagram with the activities?
In my testing tab I don't have the same tabs that you have (I got Unit, Integration, System, Acceptance, Scenario), how did you modify this UI?
How do you get the scenario in the template, I only have those fields for a scenario and that does not do the trick
scenario >
{ElemScenario.Scenario}{ElemScenario.Notes}{ElemScenario.Type}{ElemScenario.Weight}
< scenario

Regards,

[Gary]

Thanks Monsieur.
There is no scripting involved. I just copy the name of the test from the test in the tescase and paste it into the activity name.
The activities sit under the tescase and the diagrams that detail the test sit underneath the activity they describe thus:
testcase
  |_ activity
    |_diagram
Packages describe the stage at which the test is performed i.e. verification, validation
The result tab I mentioned is contained in the other testing tabs. If you open the testing window. Select Acceptance or System (these are the two i use for systems) you will see a bunch of other tabs. You might have to make the testing window a bit bigger to see them.
The scenario is imported into the document using the RTF generator. Select the Element ->Test checkbox in the template.

Gary

[Monsieur]

Thanks Monsieur.
There is no scripting involved. I just copy the name of the test from the test in the tescase and paste it into the activity name.
The activities sit under the tescase and the diagrams that detail the test sit underneath the activity they describe thus:
testcase
  |_ activity
    |_diagram
Packages describe the stage at which the test is performed i.e. verification, validation
The result tab I mentioned is contained in the other testing tabs. If you open the testing window. Select Acceptance or System (these are the two i use for systems) you will see a bunch of other tabs. You might have to make the testing window a bit bigger to see them.
The scenario is imported into the document using the RTF generator. Select the Element ->Test checkbox in the template.

Gary

Thanks  

[Paul Lotz]

Hi Paul,

Not sure to understand. Is that an other software (web based) with an EA sync?
It looks like it's for code/script testing, which is a functionality I don’t need since I use EA to do system engineering.

thanks anyway.

1) Yes, a web-based tool that synchronizes with EA test cases (and optionally with JIRA as well).
2) I reread this thread in more detail, and I think the core product has the functionality you described in your posts.  We used it for system engineering tests (e.g., component-level and system-level tests), and it worked quite well for these purposes.  In this mode, yes, there is a script in the sense that there is a prompt for the operator to do something and log the system response--which is what I gather you want--but not scripting for purely automated testing or code-level testing.  (Automated testing is now available, I understand.)

[AndyJ]

I have not used it, but there is a product (from Sparx in Spain IIRC) called EA-connector which may be useful.

It synchronises content between JIRA and EA:

http://www.sparxsystems.com/products/3rdparty/testing-qa.html#eaconjira

Andy

[Monsieur]

I have not used it, but there is a product (from Sparx in Spain IIRC) called EA-connector which may be useful.

It synchronises content between JIRA and EA:

http://www.sparxsystems.com/products/3rdparty/testing-qa.html#eaconjira

Andy

Hello Andy,

Thank you but I am [size=14]NOT [/size]looking for code testing

Isn't Jira a software for developpers?

[Paul Lotz]

JIRA is used by developers, that's true, but it is a good (really, a great) tool for tracking any kind of issue or task.  It is quite applicable to systems engineering, if one wishes to use it for that purpose (as we do).