topic Re: eCATT Testdata in Application Development and Automation Discussions

eCATT Testdata

Former Member — Mon, 18 Aug 2008 11:36:07 GMT

Hi all,

i am very new to eCATT. I wonder how to create testdata regarding a "create"-transaction. How can I repeat a testskript that creates a persistent object in the system using data defined in the testdata-container?

Sincerly

Christian

Re: eCATT Testdata

Former Member — Mon, 18 Aug 2008 11:54:03 GMT

Hi,

After you have done testscript in eCATT, you have to create test data container where you have to define the parameters to be uploaded in parameters tab. Then in variant tab, you have to create variants.

Now you have to configure the testscript and test data container in test configuration.

Thanks.

Re: eCATT Testdata

Former Member — Mon, 18 Aug 2008 12:02:13 GMT

HI,

I already know how to create testdata. My problem is how to handle create-transactions. For example i use predefined testdata for creating a new Material (mm01). The test works great and all is fine. After a while i need to change the process using a userexit. Now i want to reuse the testskript without creating new testdata. But the material is already in the system!

Edited by: Christian Dsen on Aug 18, 2008 3:16 PM

Re: eCATT Testdata

Former Member — Mon, 18 Aug 2008 13:25:24 GMT

Hi Christian.

I am not that aware about eCATT.

But, I have come across and would like to share some knowledge,

[SAP HELP Library - Standard Reference for Testing a Transaction Suitable for TCD (Record) - ECATT Tutorials|http://help.sap.com/saphelp_nw04/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm]

Hope that meets your requirement.

Good Luck & Regards.

Harsh Dave

Re: eCATT Testdata

Former Member — Mon, 18 Aug 2008 13:47:03 GMT

thank you for the link. But my problem is not a lack of technical knowledge. It is more conceptual.

Re: eCATT Testdata

Vny12 — Wed, 08 Oct 2008 05:01:12 GMT

Hi,

i see that your explanation is more on creating new objects which is possible for create transaction.

Can you please give me an example how data should look like for 1st , 2nd and 3rd variants or 1st ,2nd and 3rd loop if you are using one variant.

i hope you got my point,

best regards

vinay

Re: eCATT Testdata

uwe_schieferstein — Wed, 08 Oct 2008 05:40:20 GMT

Hello Christian

You are talking about a major problem of testing:

How to clean up the test environment?

In the long-term you may have a look at [SAPu2122 Test Data Migration Server (TDMS)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b43e2b4d-0b01-0010-c191-cba32880cb95]

I have not yet looked into TDMS in detail yet I assume this is a way to completely reset a useful testing environment.

In the short-term you may try a similar logic we have for (ABAP) Unit Testing:

(1) SetUp      : prepare testing environment (create master data, customizing, etc.)
(2) Run Tests: execute test scripts
(3) TearDown: remove/delete data generated by test scripts  " <<<

Regards

Uwe

Re: eCATT Testdata

Former Member — Wed, 08 Oct 2008 09:18:00 GMT

Hello ,

If i understand your problem right then here is the solution , Once you have recroded the script you have to parametrize all the values in the script for which you have to enter the values.

then you have to create test data containers for the same script , in this test data containers you will hav to create variants , these variants will have all the parameters that you created in the script . then you can pass multiple values for these parameters in different variants. while executing the script you can select the test variant you need to use and then execute the script. test script takes the values mentioned in the variants and executes the script.

hope it answers your questoin.

thanks and best regards,

ajay

Re: eCATT Testdata

qianchen — Wed, 08 Oct 2008 17:33:18 GMT

Hi,

When creating a test data container, please make sure that you really need it. In general a test configuration may already be enough for your requirements.

In your case, it seems to me that you would like to have a flexible material number as an input. Then you can always program a segment of coding in your eCATT script to generate a new material number, and pass the generated material number to your data creation eCATT. The coding of material number generation can either be outside of your material number creation eCATT or insdie it, depending on your own requirements. I personally would prefer that part of coding outside of your material number creation eCATT, as the material number creation eCATT can be used as a standalone reusable module.

If you just need new material numbers while other fields remain completely the same, probably the above way can already fulfill your requirement. In that case, creating variants in a test configuration would even be redundant.

If you need new sets of data (meaning each material number has different combinations of data), you can still just use a test configuration without using a test data container, while generating the material numbers can still be programmed by yourself.

Concerning test data container, my personal experience is, when the import parameter list is really very long, and only a few parameters have different values, it would be inconvenient to always go through the parameter list from left to right in a test configuration to maintain data (e.g. less than 10 fields should always have different data, while there are 40 or 100 import parameters in your eCATT), then a test data container would be a better solution.

Moreover, just creating a test data container would not help at all. Only when it is referenced in a test configuraion can it be productively used.

Hope my information helps.

Kind Regards, Qian