Unit testing is the process of checking small pieces of code to ensure that the individual parts of a program work properly on their own.
Regression testing is performed to determine if code modifications break an application or consume resources.
Integration testing ensures that an entire, integrated system meets a set of predefined requirements.
Cross-platform testing is used to determine the stability of an application in different environments.
Smoke testing is used to aid the assessment of whether critical functions of the software appear to work correctly.
Sanity testing is used after bug fixes to validate that no further issues are created after those changes.
Testing life cycle
The core testing team analyzes system requirement specifications, determines automation feasibility and identifies features that need focused testing.
In this phase, the QA manager prepares the test plan document, chooses the best-suited testing approach, specifies the number of resources, skills required and testing tools to be used.
The core testing test team writes test cases and scripts for automation if required. The creation of test data is also done in this phase.
Test environment setup
This phase includes the setup of software and hardware which is required for testing the application. The core testing team setup-up the test environment to replicate the end-users conditions.
Test execution and reporting
In this phase, the test cases/scripts get executed in the testing environment, on the test data loaded (re-loaded) for each of the test cases - finally to be presented in form of a report to key stakeholders.
We create long-term nearshoring partnerships with leading companies in the DACH & North American region.