Intemind Software Testing Process: Delivering on Zero Defect Policy

Intemind follows Agile method of software Development process which is also termed as "test-driven software development" model.
In this process unit tests are written first before coding a functionality or feature. As the test suite fails then another round of coding is done for same feature or functionality. The test suites are continuously updated as new failure conditions and corner cases are discovered, and they are integrated with any regression tests that are developed.
Unit tests are maintained along with the rest of the software source code and integrated into the build process (with inherently interactive tests being relegated to a partially manual build acceptance process). The ultimate goal of this test process is to achieve continuous integration where software updates can be published to the public frequently.

Once a feature, function or module is completed then it is made available for demo to clients. Clients can dynamically add new functions or requirements before final integration.
As discussed above 1st phase of testing in Agile methodology take place during unit or module development which are made available to clients. It involves black box, white box and integration testing. The formal testing team at the end is involved in regression, integration, usability and load testing at the end of the software development process.

Agile methodology increases the testing effort done by development team before reaching any formal testing team. In some other development models, most of the test execution occurs after the requirements have been defined and the coding process has been completed.
Two phases of Testing with focus on unit or module testing during development phase and involvement of clients throughout the process helps Intemind in delivering on its Zero Defect policy.