Skip to Content
Former Member
Mar 10, 2011 at 09:18 AM

Problem: COMMIT on aborted test


We have implemented the following mechanism for our automated tests.

The SETUP method of our unit test classes creates a few entries in our tables, these are used for the tests.

The TEARDOWN method does a ROLLBACK WORK to get rid of the entries. No COMMIT is performed by any of the tested routines or by the tests themselves.

Problem: When I run the tests from ECA and abort the transaction when the tests are running, the test entries are persisted in the tables. This can only be the case if a COMMIT is issued somewhere. The question is where?

When I let the tests run to completion then the entries are rolled back - no problems.

RFC colleagues tell me that no COMMIT is issued when a connection is aborted.

Appeciate any help!

Steps to recreate the problem: run test catalog SEPM_EPM_UNIT_TESTS from ECA as is (the tests run against YI3). Abort the transaction when the tests are running. See table SNWD_PO - you will find exactly 3 test entries.

Thx + Regards