To ensure that new features function reliably and accurately reflect the underlying use cases, they undergo a structured, four-stage testing process at Can Do. This phased approach guarantees the highest quality and minimizes risks when introducing new functionality.
Stage 1 – Developer Test (Local Environment)
In the first phase, the responsible developer tests the new feature on their local system. The goal is to ensure basic functionality and to check initial use cases. Only if this test is successfully completed will the feature move on to the next stage.
Stage 2 – Internal Production System (Can Do Consultant)
After passing the local check, the feature is transferred to Can Do’s internal production system. A Can Do Consultant then takes over the testing. In this phase, the feature is tested under more realistic conditions, with continued focus on functionality and coverage of relevant use cases.
Stage 3 – Customer Test System (Can Do Consultant)
If the feature is successfully tested in the internal production system, it is then deployed to the customer's test system. There, a Can Do Consultant tests the feature again. This involves checking how well the feature integrates into the customer's specific system landscape and validating the defined use cases.
Stage 4 – Customer Test (Customer)
In the final test phase, the customer tests the feature independently in their own test environment. The aim is to ensure that the feature works as expected in the customer’s actual environment and meets operational requirements. Only after successful approval by the customer is the feature considered released.
Note: Each testing stage is a prerequisite for the next. Any errors or issues lead to feedback to the previous stage, allowing for adjustments. This iterative approach ensures that only high-quality, thoroughly tested features are deployed in production.