What LogicHive does on an ERP rollout.
You import the client's test pack, give their testers a login (or a guest pass for a one-off tester), and they work through it step by step. Defects land against the failing step. When the last module passes, you generate the sign-off pack and hand it over. That is the whole product, and every row below is one part of it.
No card. Free forever plan. Built by a working BC consultant.
Features
One row per thing you will actually do.
No adjectives. Each line names a job a Business Central consultant does during UAT and what LogicHive does with it.
- Test pack import
- Import a 300-line Excel test pack in one upload. Flat or hierarchical, CSV or JSON, and it is ready to execute the same day.
- Scenarios and test cases
- Group test cases by module and business process (Purchasing Ops, Sales Ops, Warehousing), so the pack mirrors how the rollout is phased.
- Shared steps and parameters
- Write "log in as AP clerk, open Purchase Orders" once as a shared step and reference it from every case that needs it. A placeholder like {{vendor}} takes a default value on the case, and a cycle can override it for one run without touching the case.
- Case dependencies
- Mark that a case needs the purchase order number a different case created. The cycle orders cases to respect it and flags an "Upstream failed" case rather than blocking you from running it anyway.
- Personas and process flows
- Give a case a role (AP clerk, warehouse supervisor) and chain cases into a swimlane like Procure to pay. Run process walks the chain and notifies the next persona when a handoff is due.
- Custom fields
- Add an SAP module, a business owner or a regression risk rating to test cases, issues, requirements or cycles, project by project, without waiting on us to build it in.
- Test case review and approval
- Put a case up for review, a named reviewer approves it against a specific version, and a project can be set so only approved cases are ever added to a cycle.
- Test case versions and history
- Every content change to a case files a version with a field-by-field diff. Restore an old version as new, or let the sign-off pack print "ran v4, approved v3".
- Multi-step execution
- A client tester walks each step, marks it pass or fail, and attaches a screenshot of the posted purchase invoice as evidence.
- Test cycles
- Scope a named round of testing to the areas going live this phase, with its own environment, build and per-case assignment. Each cycle carries its own sign-off bar, a minimum pass rate and a cap on open issues, and can only be signed off once every case has a result and it clears that bar. Otherwise it is failed, with a reason, and the retest cycle starts from what failed.
- Environments and builds
- Record UAT2 and transport 412 against a cycle, a run and an issue, so a triage conversation says which system and which release instead of guessing. Found in and fixed in print on the sign-off cover.
- Retest cycles
- Pull everything that failed or is blocked in the last cycle into a fresh one with one click. It carries over the same testers and the environment, so you are not re-running what already passed.
- Milestones
- Attach a cycle to a dated milestone like "Go-live" or "UAT sign-off" and see how many days out it is, or how many days overdue, from the project's Run tile.
- Requirements and traceability
- Link requirements to test cases, so you can show which of the 40 requirements have a passing test and which have none, and export the traceability matrix as CSV or JSON.
- Issues and change requests
- Raise a defect from the failing step. Tag it bug, change request or enhancement, set severity, assign it to the developer who owns the extension.
- Custom issue workflows
- Replace the six built-in statuses with a client's own (New, Triaged, Ready to test, whatever they use), and control which status can move to which. Analytics still count against open, in progress, resolved and closed underneath.
- Pass rate and coverage analytics
- See pass rate per module and execution velocity over the last 14 days, so the Monday steerco gets a number instead of a guess.
- Status reports and the steering view
- Reports › Status gives the steering committee a RAG banner, pass rate, open defects, blocked cases and the next milestone on one page, with a trend chart and a PDF export. Schedule it to email itself weekly, or hit Send now before the meeting.
- Sign-off packs
- Generate a frozen PDF snapshot: results, the version each case ran against, environments and builds, who ran what and when, an approved column, and results by process. Sign it to record who accepted the results, then hand it to the client.
- Activity feed and audit trail
- A timestamped feed of every status change, so six months after go-live you can show who signed off the warehouse module.
- Test timer
- The built-in timer records how long each test actually took, which is the number you need when scoping the next UAT phase.
- Risk register
- Log the risks that come out of testing (the EDI mapping nobody has signed off, the missing posting group), with an owner and a severity.
- Run Licenses for client testers
- Give a client tester a login that can execute assigned tests and log defects, without buying them a Full License. For someone who only needs one cycle, invite them with a guest pass instead.
- Guest tester passes
- Invite a business user into one cycle from a link: their name and email, no account, no seat, no licence. They run their assigned cases and raise issues. The link and their access last five days from when it was created, or until the cycle closes if sooner.
- Public API and CI results
- Post automated results into a cycle from a pipeline, as JSON or a JUnit XML file, using a company API key. An automated run counts towards cycle progress and the sign-off pack exactly like a manual one. Included on the Team, Business and Scale plans.
- Template marketplace
- Start from the Business Central Implementation Template. Purchasing Ops and Sales Ops (17 scenarios, 48 test cases) are free on every account.
- One project per client
- Run five client rollouts side by side, each in its own project, without one client ever seeing another client's test pack.
- Bulk operations
- Change the status, owner or module on fifty test cases at once instead of opening each one.
- White label and custom subdomain
- On Business and Scale, put the consultancy's logo on the client-facing screens. Scale adds yourbrand.logic-hive.app.
See it in action
Four walkthroughs, setup to sign-off.
One Business Central procure-to-pay project, from creating the client to handing over the sign-off pack.
Part 1: Overview
Getting started
The dashboard and a project's results and analytics, shown with sample data.
Part 2: Setup
Setting up a project
Create the company and project, set the sign-off rules, add requirements and risks, build the test structure, then write a full test case for a Business Central procure-to-pay process.
Part 3: Test cycles
Test case management
Review and approve test cases, add the environment and build, create a test cycle and assign a tester, then run the procure-to-pay test, fail a step and report a bug from it.
Part 4: Sign-off
Review and sign-off
Work the bug through Issues, retest on the new build and close it, then sign off the cycle against its pass rate and open issue thresholds and produce the client sign-off pack.
Further reading
Guides and free resources.
Essential UAT software features include: test case management for organising and versioning test cases, test execution tracking with pass/fail recording, issue and defect tracking linked to test cases, real-time collaboration for distributed teams, customisable reporting and dashboards, role-based access control, and audit trails for compliance. Advanced features to consider are change request management, risk registers, and bulk import/export capabilities.
LogicHive differentiates itself by being purpose-built for UAT with an intuitive interface that non-technical stakeholders can use easily. Unlike complex enterprise tools, LogicHive offers quick setup with no training required, built-in collaboration features, comprehensive reporting, and affordable pricing for SMBs. It includes unique features like risk registers and change request management specifically designed for the UAT workflow.
Yes, through a public REST API. A CI pipeline can create cycles, and post its own results as JSON or a JUnit XML file, into a LogicHive cycle using a company API key; an automated run counts towards cycle progress and the sign-off pack exactly like a manual one. LogicHive does not push tickets into Jira or Azure DevOps: that is on the roadmap, not shipped. Test results can also be exported as CSV or JSON when you need to hand work to a dev team.
Yes. LogicHive supports test case review and approval, with sign-off pinned to a specific version, full version history with a diff on every change, configurable issue workflows and custom fields per project, and a complete audit trail. A public REST API lets a CI pipeline post its own results in. The multi-tenant architecture supports complex organisational structures, and white-label options are available for MSPs and consultancies serving multiple clients.
Most teams are productive within hours of signing up. LogicHive's intuitive interface requires minimal training, and you can import existing test cases via CSV or Excel. The platform includes pre-built templates to accelerate your first project setup, and the free plan (1 Full License, 3 Run Licenses, 1 project) has no time limit, so you can run a real UAT cycle before paying.
Run your next UAT cycle in LogicHive.
Nothing to install. Free plan, no card, no time limit. Import your test pack and run the first case today.