Testing & Quality
Quality has to be designed in long before the product goes into production. At Move we work with testing in both development and production, but for different purposes: in development, testing creates learning and validates requirements. In production, testing ensures repeatability, traceability and consistent quality from batch to batch.
Testing & Quality
Testing in development and testing in production
Testing and quality mean different things depending on where the product is in its lifecycle. In the development phase, testing is about learning, validating and reducing risk. In production, testing is about repeating, controlling and documenting. Both matter, but they call for different methods, tools and ways of thinking about quality.
Requirements for testing
Test plans that cover every requirement
Testing along the way
Subsystem, integration and end-to-end
Testing in the design
Test points, fixtures and test mode
End-of-line
Pass or fail, every time
Quality starts with clear requirements and the right test strategy
In development, quality starts with clear requirements. What does the product need to do? Which functions are critical? Which interfaces have to work? What should be tested as a subsystem, and what should be tested as a complete product? That is why we work with test plans in which requirements are mapped to concrete tests. That way we can see whether the product actually does what it was designed to do.
We use testing as an active part of the development work. That can be subsystem testing of electronics, firmware, sensors, mechanical functions or software modules. It can be integration testing, where several parts have to work together. And it can be end-to-end testing, where the product's whole flow is tested from input to output — for example from sensor, electronics and embedded software through to cloud, app or user interface.
In software and embedded development we like to work with principles from test-driven development. That means expected behaviour is described early, and tests are used to steer development. A good test has to be concrete, repeatable and tied to a requirement or a function. When new functionality is built, existing functions must keep working. That is why regression testing, automated tests and continuous validation matter, especially when the product evolves over time.
In development projects, requirements often change. You learn something new, the customer adjusts the need, the technology shows its limits, or the market points in a new direction. When the requirements change, the test structure has to follow. Otherwise you risk testing the product against an outdated reality. That is why test plans, acceptance criteria and documentation have to be maintained as a living part of the project.
From prototype to repeatable production
The transition from development to production is one of the most important places to work on quality in a structured way. A prototype may well work once on the bench, but production requires that the same solution can be built many times and still work the same way. Here, testing must not only prove that the product can work. Testing has to prove that every unit produced works.
In production we therefore work with controlled processes, clear assembly instructions, test instructions, end-of-line testing, functional checks, measurements, calibration and documentation. The goal is to be able to determine unambiguously whether a product passes or fails. It has to be clear what has been tested, which limit values apply, and how the result is recorded.
Design the product so it can be tested
Production testing also has to be efficient. It has to catch faults without making production unnecessarily heavy. That is why we design testing in from development onwards. Test points on the PCB, access to interfaces, firmware for test mode, fixtures, calibration routines and automated test sequences can make a big difference when the product has to be manufactured in repeated batches.
Quality throughout the product's lifetime
When the product is in operation, quality work does not stop. Components can change, software can be updated, faults can be discovered in the market, and the product can get new versions. That is why a controlled release process matters. Changes have to be assessed, tested, documented and released, so you know what has changed, why it changed, and which version has been manufactured or shipped to the customer.
At Move we see testing and quality as the bridge between development and production. When requirements, test plans, development testing, production testing and release processes fit together, the product becomes more robust — not only as a prototype, but as a product that can be manufactured, delivered and maintained over time.
Frequently asked questions
What is the difference between testing in development and in production?
In development, testing is used to learn, validate requirements and reduce technical risk. In production, testing is used to ensure that every unit is built correctly and works consistently.
What is a test plan?
A test plan describes what is to be tested, how it is tested, which requirements the test covers, and when the product can be considered approved.
Do you work with test-driven development?
Yes. We use principles from test-driven development, where expected behaviour is described early and tests are used to ensure that new functionality does not break existing functions.
Why is testing important in the transition to production?
Because a prototype that works once is not necessarily ready for production. Production requires repeatable tests, clear limit values and documentation that every unit works.
How do you handle changes after launch?
Changes are handled through a controlled release process, where changes are assessed, tested, documented and released, so the product's quality and traceability are preserved.
Shall we turn your idea into reality?
Technical development takes more than good ideas — it takes the right skills. We have gathered hardware, software and engineering expertise under one roof, so you get from prototype to production quickly and safely.
Reach out to us →