Testing & Review
Before launch,
everything gets a review.
Testing & Review is the stage where the developed project is checked for functionality, interface behaviour, responsive presentation, integrations and other applicable requirements before final delivery.
Why testing matters
Development and testing are different stages. A feature may be implemented but still require testing across different screens, devices, inputs or connected services. Review helps identify issues before the project moves toward delivery.
A project can be reviewed from multiple angles.
Testing is performed according to the nature and requirements of the individual project.
What may be checked?
Functional Testing
Core features, buttons, forms, navigation and expected user actions are checked where applicable.
Responsive Review
Layout and interface behaviour can be reviewed across supported screen sizes and devices.
Integration Testing
Applicable APIs, payment services and third-party integrations can be checked for expected behaviour.
Interface Review
Visual consistency, spacing, content placement and user interaction can be reviewed against the project direction.
From issue to resolution.
Identify
An issue or unexpected behaviour is identified during review.
Investigate
The relevant functionality or technical cause is examined.
Resolve
Applicable development changes are made to address the issue.
Re-test
The affected functionality can be checked again after the change.
Not every issue has the same meaning.
During review, issues can relate to functionality, design, content, integration or technical dependencies. Their handling depends on the project scope and circumstances.
Functional Issue
A required feature does not behave according to its intended functionality.
Interface Issue
A visual or responsive behaviour does not match the applicable design direction.
Integration Issue
A connected external service or API does not respond as expected.
Testing is followed by project review.
Client perspective
Depending on the project arrangement, the client may review the developed product and provide feedback on the agreed functionality and deliverables.
Testing is performed according to the nature, scope and technical requirements of the project. Third-party outages, external API changes, unsupported devices, unavailable services or issues outside the project environment may require separate investigation.
Frequently asked questions.
Why is testing performed before delivery?
Testing helps identify applicable functionality, interface and integration issues before the project proceeds toward final delivery.
Does every project require the same testing?
No. Testing depends on whether the project is a website, e-commerce store, mobile application, admin panel or another type of digital product.
Can the client report an issue during review?
Yes. Client feedback can be part of the review process according to the applicable project arrangement.
What happens when a bug is found?
The issue can be investigated and, where applicable, addressed before the project proceeds to the next stage.
Does testing guarantee that no future issue can occur?
No. Testing reduces identifiable issues within the applicable review scope but cannot guarantee that every possible future issue will be eliminated.
Review before delivery.
After development, testing and review help prepare the project for the next stage: final delivery.
Discuss Your Project →