Organizing regression test using ecatt

[Former Member]

Hello

I am trying to organize regression test using ecatt. and try to find out the best to compare two series of results. Does anybody is doing this? any experience to share?

Thanks

[Former Member]

We are currently trying to create regression tests for SAP in eCATT. Unfortunately we are not far enough along in our efforts that we can begin comparing logs from different regression cycles, we are only beginning to develop our initial set of regression tests. One of the problems we are grappling with is how to organize our regression library. We are currently using Solution Manager to store our tests, however this system is project based and we are not fully convinced that we want to organize regression tests according to project. Other ideas that we have had were to organize tests by module, component and transaction. The drawback of this solution is that few unit tests are independent and usually must be part of an integration test. At this point we would like to try to organize tests by processes - such as order-to-cash or purchase-to-pay. I'd like to hear some of your thoughts on how you organized your library of regression tests.

[Former Member]

Hi Ben,

I see that we are about doing the same project. This is my third project with eCATT, and i learn each time a bit more about the tool.

I am also wondering if I should use Solman or not on this project. We are doing an updgrade and our business case is to invest into automated testing so we can reuse this case in the future. Like you said solman is project oriented and "silos" organized which does not really fit our process integration view.

I would like to share more experience with you if you wish. We have started build our ecatt script last week, maybe we could share best practice or recording standard in the next few weeks.

Gilles

gilles.samoun@qsit.com

[Private_Member_12087]

Hello Gilles,

Since no one else has replied yet, I will make a few comments.

An eCATT log contains a lot of information. So, try to minimize the number of logs you need to compare. Design your tests so that the key information results in a simple pass or fail of the test. Only the logs that fail need to be examined (perhaps then compared to the previous passed execution). There are several check possibilities in eCATT that result in a fail status - remember a fail anywhere in the test propagates up to the top of the log.

You can make the comparison of logs easier by using the LOG command to bring key information to a more visible location in the log. Similarly, by assigning information to export parameters, these will be easily found in the log.

You can use the print function to get a hard copy of the log. With print preview, you can also save to a local file (System - List - Save - Local file) in various formats.

If you want to get really advanced, you could use some abap to export key information to a table - each row of the table corresponding to an execution.

Best regards,

Martin

[Former Member]

Hi Martin,

i have similar requirement in the our project.

The log is not use friendly to end user.

customer expecting, customised test result in the Excel file with Input Entries and corresponding test result for each and every row.

do u any solution for that.

can u guide me?

Regards,

Sree..