# ABAP Unit Test Case Worksheet (Test Plan Template) > Source: https://netray.co/tools/abap-unit-test-case-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable test case log for ABAP objects with expected and actual values, variance and pass/fail status, exportable to Excel. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - ABAP developer - QA tester - SAP test manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Test case **Key:** tc **Type:** text #### Object **Key:** object **Type:** text #### Scenario **Key:** scenario **Type:** text #### Input data **Key:** input **Type:** text #### Expected rows **Key:** exp_rows **Type:** number #### Actual rows **Key:** act_rows **Type:** number #### Variance **Key:** variance **Type:** number **Expr:** act_rows - exp_rows **Format:** integer #### Result **Key:** result **Type:** select **Options:** - Not run - Passed - Failed - Blocked #### Tester **Key:** tester **Type:** text #### Test date **Key:** date **Type:** date **Rows:** **Tc:** UT-001 **Object:** ZMM_OPEN_PO_AGING **Scenario:** Plant with open POs, default selection **Input:** Plant 1000, all vendors **Exp rows:** 412 **Act rows:** 412 **Result:** Passed **Tester:** RDEV **Date:** 2026-10-14 **Tc:** UT-002 **Object:** ZMM_OPEN_PO_AGING **Scenario:** Plant with no open POs **Input:** Plant 2000 **Exp rows:** 0 **Act rows:** 0 **Result:** Passed **Tester:** RDEV **Date:** 2026-10-14 **Tc:** UT-003 **Object:** ZMM_OPEN_PO_AGING **Scenario:** Deleted items included **Input:** Plant 1000, flag on **Exp rows:** 437 **Act rows:** 430 **Result:** Failed **Tester:** RDEV **Date:** 2026-10-14 **Tc:** UT-004 **Object:** ZMM_OPEN_PO_AGING **Scenario:** User without plant authorization **Input:** Plant 3000, restricted user **Exp rows:** 0 **Act rows:** 0 **Result:** Not run **Totals:** #### Test cases **Key:** tc **Agg:** count **Format:** integer #### Total variance **Key:** variance **Agg:** sum **Format:** integer **Notes:** Automated ABAP Unit tests are written as local test classes (FOR TESTING) and run from SE80, ADT or SE24. Use this worksheet for the manual and integration tests around them, and as evidence for review. ## Content **Intro:** Unit tests in ABAP are only part of what a developer must prove before a transport leaves development. This worksheet captures the scenarios, expected values and results in one place, so reviewers can see what was tested. **Sections:** #### How to use the worksheet **Body:** Before coding, add rows for the scenarios in the specification: the normal case, the empty result, boundary values, wrong or missing master data and the authorization failure. Record expected row counts or amounts from a trusted source, such as a manual query or the functional consultant. After running the object, enter the actual values. Variance is calculated for you, so a non-zero value points straight at a failing case. Set the result, tester and date for evidence. **Bullets:** - Write scenarios before coding - Include at least one empty and one error case - Record the data used, not only the outcome - Retest and update after every fix #### ABAP Unit versus manual testing **Body:** ABAP Unit lets you test methods in isolation with local test classes, assertions through CL_ABAP_UNIT_ASSERT and test doubles for database access. It is fast and repeatable and fits clean, class-based code. Manual and integration tests still matter for screens, authorizations, posting results and interfaces. Use this worksheet to list both, and mark which cases are covered by automated tests so nothing is tested twice and nothing is missed. #### Common mistakes **Body:** Developers often test only with their own master data, which hides authorization and data-quality failures. Others compare results to what the program returns instead of an independent expected value. Another gap is forgetting to retest after a bug fix. Keep expected values independent, test with a second user and repeat the full list before the release of the transport. **Bullets:** - Expected values taken from the program - Only one user tested - No negative cases - No retest after fixes **Cta:** We can discuss generating draft ABAP Unit test classes and scenario lists using a model that runs inside your own network. **Faq:** #### Does this replace ABAP Unit? **Answer:** No. ABAP Unit is the automated test framework inside the ABAP runtime. This worksheet documents test scenarios and results, including manual and integration tests, and gives reviewers evidence in a form they can open in Excel. #### How many test cases should an object have? **Answer:** It depends on risk. A simple report might have five to ten, an interface or posting program many more. Cover normal flow, empty data, boundaries, invalid input and authorization before adding variants. #### What does variance show? **Answer:** Variance is actual rows minus expected rows. Zero means the count matched. It does not prove the content is right, so compare key values as well for important cases. #### Can testers outside the dev team use it? **Answer:** Yes. Business testers can fill actual results and notes, then export to Excel and attach it to the change ticket or test management tool. ## Search terms abap unit test template, abap test case template excel, sap unit test plan template, abap test plan, sap developer unit test document, abap unit test cases example --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json