Test Documents are not updated in Test Plans after modifications

[Former Member]

Hello,

We are using the functionality of Solution Manager of Test Workbench.

We are at stack 17 of SolMan 7.0. Test cases are not updated when small

modifications are done in test document. Those modifications are not

available for the users in the STWB_Work.

Steps to reproduce:

1. We have created a test document (an excel) assigned to the SOLAR02,

tab Test Case.

2. Then we created for the first time a Test Plan in transaction STWB_2,

selecting transactions and test cases (not released). We select the

scope of the test plan, including the test document assigned to the

structure. Generate the test plan.

3.Then we created a test package including the transactions and test

case (excel).

4. Later on we need to update the excel adding some comments for the

user. We went to SOLAR02, tab Test Case and use the modify function,

make the modification and save it back into SolMan.

5. Then we went to the test plan STWB_2 and regenerate the complete

plan. However when we double click the test case it still shows the old

content of the excel.

6. We found that we need to de-assigned the test case from the plan in

Transaction STWB_2. Then regenerate the plan again.

7. Then re-assigned the test case in the plan in STWB_2, regenerate the

plan for third time, and now we see the modification.

8. Then we need to go to the package and reassign the test case and

regenerate in trx STWB_2. Then finally you have the small modification

done in the test case reflected corrected.

We found that this procedure is akward, and prone to do errors, missing

test cases in the plan an so on. We consider this an error, steps 6, 7

and 8 should not be needed.

We consider that the process should be upto step 5, that we modify the

test cases and then regenerate test plan and test packages and it should

be enough.

Please, let me know if there is a note that corrects this error. I

search for notes and I could not find myself any specific note.

Esteban Hartzstein

SolMan Consultant

Nidera

[Former Member]

Hi All,

My requirement is to update the testcase status in stwb_2 transaction using excel sheet. The excel sheet contains the test plan , test package and test case name .

Can we do using BDC or LSMW.

OR is there a way other then this to update the testcase status from excel.

when i used shdb , i m not getting the plan and package name but im getting below codes

'=%_GC 136 35'.

'=%_GC 134 1'.

'=%_GC 146 35'.

Below is the code which i got when i recorded.

perform bdc_dynpro using 'SAPLS_TWB_H' '0200'.

perform bdc_field using 'BDC_CURSOR'

'FAVORITES-TEXT(03)'.

perform bdc_field using 'BDC_OKCODE'

'=SELE'.

perform bdc_field using 'T002-SPRAS'

'EN'.

perform bdc_dynpro using 'SAPLS_TWB_H' '0200'.

perform bdc_field using 'BDC_CURSOR'

'T002-SPRAS'.

perform bdc_field using 'BDC_OKCODE'

'=PACKAGE'.

perform bdc_field using 'T002-SPRAS'

'EN'.

perform bdc_dynpro using 'SAPLS_TWB_G' '0110'.

perform bdc_field using 'BDC_OKCODE'

'=%_GC 136 35'.

perform bdc_dynpro using 'SAPLS_TWB_G' '0110'.

perform bdc_field using 'BDC_OKCODE'

'=%_GC 134 1'.

perform bdc_dynpro using 'RSTWB_ANALYZE' '0200'.

perform bdc_field using 'BDC_OKCODE'

'=%_GC 146 35'.

perform bdc_dynpro using 'SAPLSTATUS' '0150'.

perform bdc_field using 'BDC_OKCODE'

'=STATUS'.

perform bdc_field using 'BDC_CURSOR'

'D0100_ELEMENTS-STATUS'.

perform bdc_field using 'D0100_ELEMENTS-STATUS'

'ALMOST_OK'.

perform bdc_field using 'D0100_ELEMENTS-NOTE_TEXT'

'Purchase Order has been Created'.

perform bdc_dynpro using 'SAPLSTATUS' '0150'.

perform bdc_field using 'BDC_OKCODE'

'=SAVE'.

perform bdc_field using 'BDC_CURSOR'

'D0100_ELEMENTS-STATUS'.

perform bdc_field using 'D0100_ELEMENTS-STATUS'

'ALMOST_OK'.

perform bdc_field using 'D0100_ELEMENTS-NOTE_TEXT'

'Purchase Order has been Created'.

perform bdc_dynpro using 'SAPLSTATUS' '0150'.

perform bdc_field using 'BDC_OKCODE'

'=BACK'.

perform bdc_field using 'BDC_CURSOR'

'D0100_ELEMENTS-STATUS'.

perform bdc_field using 'D0100_ELEMENTS-STATUS'

'ALMOST_OK'.

perform bdc_field using 'D0100_ELEMENTS-NOTE_TEXT'

'Purchase Order has been Created'.

perform bdc_dynpro using 'RSTWB_ANALYZE' '0200'.

perform bdc_field using 'BDC_OKCODE'

'=TRRT'.

perform bdc_dynpro using 'SAPLS_TWB_G' '0110'.

perform bdc_field using 'BDC_OKCODE'

'=BACK'.

perform bdc_dynpro using 'SAPLS_TWB_H' '0200'.

perform bdc_field using 'BDC_CURSOR'

'T002-SPRAS'.

perform bdc_field using 'BDC_OKCODE'

'=BACK'.

perform bdc_field using 'T002-SPRAS'

'EN'.

perform bdc_transaction using 'STWB_2'.

perform close_group.

Any help in this regard is highly appreciated.

Many Many Thanks in advacne.

Regards,

Gana

[Former Member]

Hello I got the answer from SAP. I share with you

"As of SP12 there is a version management for testcasedocuments.

This means that in the testplan always the version of the document

remains as it was when the testplan was generated.

I try to explain it by a small example:

You have created a testdocument in SOLAR02

Afterwards you have created a testplan and a testpackage for this test-

case.

Now you enter SOLAR02 again and change the testdocument.

You will see that this change is not reflected in the testplan and in

the testpackage, but the initial version remains.

When you now want to have the new changed testdocument in the testplan/

package you will have to enter the testplan in changemode and navigate

to the node of the testdocument and select the document.

Then you have to click at the 'General Data' tab on the right hand.

You will see the text 'Newer Version Exists' and you are able to

take the new version over into your testplan/packages by pressing the

button 'Assign current version' (green and red balls)

Afterwards you have to regenerate the testplan and the new version of

the document is availabele also for the testers in the testplan.

There is also a button called 'Next changed Document' (two yellow

rectangles) which helps you to find the node where a newer version of a

document exists.

When you press the button you are taken to the node."

Hope it works for you

Regards

Esteban Hartzstein

Solution Manager Consultant

[Former Member]

Thanks Esteban,

That works indeed!

Maybe you can help my on the following as well:

I am looking at Solution Manager to help us to do Integration Testing. Which way of working would you recommend? For example if we want to test multiple variants of one integration test, how would you do this best. Would you then describe all possible variants which need to be tested in your test document and then assigning them to one test package. Then you cannot maintain the test status for each variant.

So overall, what do you propose for integration testing via Solution Manager? How can this be organised in the best way? Are you aware of a best practise?

Thanks a lot!

Kristof

[Former Member]

I would be pleased to get an answer from someone on this topic as well, as we are facing the same problem in testing. For the moment we haven't found a proper solution for this, which prevents us from sharing information between testers.