# Infor LN Test Case Log for UAT and Regression Testing > Source: https://netray.co/tools/infor-ln-test-case-log > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable log to record LN test scenarios by session, with expected result, outcome and a live pass rate. ## Category infor-ln ## Erp Infor LN ## Audience - LN tester - LN consultant - Key user ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Test ID **Key:** id **Type:** text #### Process area **Key:** area **Type:** select **Options:** - Sales - Procurement - Warehousing - Manufacturing - Finance - Service - Integration #### LN session code **Key:** session **Type:** text #### Scenario **Key:** scenario **Type:** text #### Expected result **Key:** expected **Type:** text #### Result **Key:** result **Type:** select **Options:** - Not run - Pass - Fail - Blocked #### Tester **Key:** tester **Type:** text #### Run date **Key:** run_date **Type:** date **Rows:** **Id:** T-001 **Area:** Sales **Session:** tdsls4100m000 **Scenario:** Create sales order for stocked item **Expected:** Order saved, price and delivery date defaulted **Result:** Pass **Tester:** A. Key user **Run date:** 2026-10-12 **Id:** T-002 **Area:** Procurement **Session:** tdpur4100m000 **Scenario:** Create purchase order and print **Expected:** Order saved and document prints with correct supplier **Result:** Pass **Tester:** B. Buyer **Run date:** 2026-10-12 **Id:** T-003 **Area:** Warehousing **Session:** whinh2100m000 **Scenario:** Receive purchase order line into stock **Expected:** Inventory increases in target warehouse **Result:** Fail **Tester:** C. Stores **Run date:** 2026-10-13 **Id:** T-004 **Area:** Manufacturing **Scenario:** Release and complete production order **Expected:** Materials issued, finished item received, WIP cleared **Result:** Not run **Tester:** D. Planner **Run date:** 2026-10-14 **Id:** T-005 **Area:** Integration **Scenario:** Send sales order confirmation to customer by EDI **Expected:** Message created and acknowledged **Result:** Blocked **Tester:** E. IT **Run date:** 2026-10-14 **Totals:** #### Test cases **Key:** id **Agg:** count **Format:** integer **Notes:** Session codes in the example rows are illustrative: replace them with the exact sessions in your own LN version. Set the Result column for each run and count passes yourself, or filter the exported Excel file for Pass and Fail to get your pass rate. ## Content **Intro:** User acceptance testing fails quietly when results live in emails. This log keeps every LN scenario, its session and its outcome in one place you can export for the steering group. **Sections:** #### How to use the log **Body:** Add one row per scenario that a user can run end to end, such as create a sales order, receive against a purchase order or complete a production order. Record the LN session code so a developer can reproduce it, write the expected result in business words, and set the result after each run. Export to Excel to share with the project team and filter by area or by Fail to drive the defect review. #### Writing good scenarios **Body:** A useful scenario starts from a real business event and ends with a checkable outcome. Avoid scenarios such as test the sales order screen. Prefer create a sales order for a stocked item, confirm the price and delivery date default, and check the order appears in the warehouse release list. Include data conditions, because LN behavior often depends on item type, warehouse and business partner setup. **Bullets:** - One business event per scenario - Name the item, partner and warehouse used - State the expected result as something you can see or count - Include negative cases such as blocked partner or missing price #### Reading the status **Body:** Count Pass, Fail and Blocked separately. A high Blocked count means a dependency such as integration or master data is missing, and it hides real risk because those scenarios have not run at all. A scenario that fails should become a defect with the test ID attached. When it is fixed, rerun the original and any neighbors that share the same session or table. #### Common mistakes **Body:** Testing with a developer account instead of a real user role hides authorization faults. Testing only the happy path misses most go-live defects. Reusing one test partner for everything misses currency, tax and credit rules. Run at least some scenarios under production-like roles and with at least one foreign currency partner. **Cta:** If regression testing after each LN patch or upgrade is slow, we can help script repeatable checks against your own scenarios. **Faq:** #### How many test cases do we need for an LN go-live? **Answer:** It depends on scope. A focused rollout may need under a hundred end to end scenarios, while a full multi-module migration can need several hundred. Cover every process in scope, plus integrations and period end. #### Who should run the tests? **Answer:** The people who will do the work after go-live. Key users and real role holders find more problems than consultants, because they know what normal looks like. #### What is the difference between Fail and Blocked? **Answer:** Fail means the scenario ran and the result was wrong. Blocked means it could not run because something it depends on is missing or broken. Track them separately because they need different actions. #### Can I import this log into another tool? **Answer:** Yes, export to Excel or CSV and import into your defect tracker or test tool. Keep the Test ID unchanged so results stay linked across tools. ## Search terms infor ln test cases, infor ln uat template, erp test case template excel, baan to ln testing, erp regression test log, infor ln test script, uat tracker erp --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json