A/B testing
lab
Why?
A minor change in a design may alter user behaviour in ways that are hard to detect in a usability test. An A/B test allows you to compare real-world user behaviour across different versions of a product.
Methods
Lab research is done to test your ideas with the users of your product. You use lab research to learn if things work out the way you intended them.
Component test
lab
Why?
Test a subsystem or component in isolation to ensure its correctness before integrating it with other components or modules.
Computer simulation
lab
Why?
Computer simulations are used when a real-world process, system or event situation is not available or feasible.
Data analytics
lab
Why?
Gain insights by measuring and analysing data. Researching a dataset can give you useful quantitative information about the topic of interest.
Data quality check (ML)
lab
Why?
Ensure that the data you are using is of sufficient quality to base further conclusions on.
Hardware validation
lab
Why?
Hardware does not always perform according to its specifications. Hardware validation ensures that the hardware performs as expected and excludes hardware as a source of errors.
Model evaluation (ML)
lab
Why?
Verify the correctness and usefulness of the results of your model with the stakeholders or compare different models with respect to their usefulness.
Model validation (ML)
lab
Why?
Ensure that your model produces results of sufficient quality to base your conclusions on.
Non-functional test
lab
Why?
Test the operating conditions under which the system delivers its intended functions.
Security test
lab
System test
lab
Why?
Solve problems before your system goes into production and demonstrate that the system operates according to its requirements.
Unit test
lab
Why?
Find certain types of bugs as early as possible and ensure your code keeps running after a change.
Usability testing
lab
Why?
Detect problems users have with your solution and correct them before the system goes live.
