Infor LN Test Case Log for UAT and Regression Testing
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.
| Test ID | Process area | LN session code | Scenario | Expected result | Result | Tester | Run date | |
|---|---|---|---|---|---|---|---|---|
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.
Automate repeatable LN checks
An optional conversation about scripting regression checks for your LN scenarios.
Optional. The tool and every export work without this. No spam.
How to use the log
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
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.
- 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
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
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.
Frequently Asked Questions
How many test cases do we need for an LN go-live?
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?
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?
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?
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.
If regression testing after each LN patch or upgrade is slow, we can help script repeatable checks against your own scenarios.
Related Tools
Infor LN Cutover and Go-Live Checklist
A cutover checklist for Infor LN and Baan migrations: freeze, conversion, reconciliation, integrations, support and rollback decisions.
Infor LN & BaanInfor LN SQL Query Generator
Fill in the table, company number and key range to get read-only SQL for the LN database, with the physical table name built for you.
Infor LN & BaanInfor LN Batch Job Schedule Register
An editable register of scheduled and batch jobs in Infor LN with owner, frequency, dependencies and last run status.
Infor LN & BaanInfor LN Support Ticket Template
Write an LN incident report that support can act on the first time: environment, session, steps, error and business impact.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Infor LN and Baan Customization Inventory Worksheet