A vendor source describes the capability, interface or configuration. This is not a UnitWeave test result and does not guarantee your application.
Test lab / evidence register
SUNMI POS, Kiosk and Device Compatibility Testing
Turn a compatibility question into a reproducible record for a named SUNMI device, application build, peripherals and operating environment.
Discuss your projectTest scope / before a result
Test the setup your rollout will actually use.
Compatibility belongs to a defined combination of hardware, software, configuration and operating conditions. Start with the workflow that matters, then name the setup closely enough that another reviewer can repeat it.
The evidence vocabulary
“Supported” needs a source and an owner.
The same word can hide very different levels of confidence. These states explain what the record means and what it does not mean.
A dated UnitWeave record names the model, OS, firmware, app build, accessories, method, result and reviewer.
A named customer acceptance record confirms the agreed workflow for its environment. It is not automatically a universal result.
Some paths pass and a defined limitation remains. The supported path and failed or excluded path must both be written down.
A named record says the requested setup is outside the confirmed scope or fails the agreed acceptance criteria.
Validation record / required fields
A useful test can be repeated by another reviewer.
A positive, partial or negative conclusion stays tied to the setup that produced it. The record below is the minimum context for comparing a result, reopening a defect or extending coverage to a new build.
01
Target identity
Record the model, exact variant, Android release, firmware, application package, version and build. Do not use a family name as a substitute for the tested configuration.
02
Connected setup
Name the printer, scanner, drawer, customer display, holder, paper, payment sandbox, network path and power assumptions used during the run.
03
Test method
Write the preconditions, test data, expected result, steps, repetitions and observed result. Include cold start, reconnect and relevant offline paths when they are part of the workflow.
04
Recovery and limits
Capture permissions, errors, logs or screenshots, recovery behavior, known limitations and excluded paths. Keep customer data, credentials and production binaries out of the public record.
05
Decision and owner
State the evidence level, acceptance result, test date, reviewer, evidence location, support owner and next action. A result remains scoped until a new record extends it.
From question to record
A short path from uncertainty to a scoped answer.
The lab process makes the unknowns visible before purchase, certification or rollout. It also gives engineering and customer teams a shared handover point.
- 01
Frame
Describe the business workflow, target market, device variant, application build and acceptance criteria.
- 02
Prepare
Freeze the firmware, peripherals, network, power, accounts, permissions and test data before execution.
- 03
Execute
Run scripted cases, repeat important paths, exercise restart and recovery, and retain the observed evidence.
- 04
Publish
Separate vendor facts from test results, assign the evidence state, record limitations and name the next review.
Publication boundary
A test result is specific by design.
The lab can make a defined decision easier to trust. It cannot turn one successful setup into universal compatibility, payment certification or a local support commitment.
- A SUNMI specification remains a manufacturer statement; it is not rewritten as a UnitWeave test result.
- One model, firmware, application build or accessory set does not silently cover another configuration.
- Payment certification, acquiring, tax, import, customer data and local service need their own responsible owner.
- The quotation, acceptance record and contract control the deliverable, availability, warranty and support commitment.
Start with the open question
Need a compatibility answer before rollout?
Send the target workflow, model or shortlist, application build, peripherals, country and acceptance criteria. We will turn the open question into a scoped validation brief.