Our approach
A proven methodology
A flexible method with a set of procedures and tools adaptable to various project situations.
Our approach
The goal
Target
Introduce within the population a methodological approach concerning qualification, and wherever the scenario leads (deployment, migration, upgrade ...).
Design a reference test plan constructed at the headquarters that covers exclusively by business area the functions of the common application to all branches with the application. This test plan will be distributed to subsidaries.
Issues
Streamline under the qualification process on the application and develop efficient operation.
- Normalize the QA process and communication between the different contributors
- Capitalize the test repository
- Increase understanding the test strategy through the use of a method and a standard terminology
- Master the costs of qualification in projects
- Win in product quality
Progress
Structuring principles of the approach
The steps of the implementation are synchronized between the development cycle and the qualification.
Identification
Identification of qualifying tasks
- Map the business requirements and the use cases
- Determine the target and the testing effort
- Analyze risks
Planning
Project Planning
- Estimate the workload of the test team
- Determine the deadlines and the teams to implement
- Assign the roles
-
Preparation
Test Plan Preparation
- Write the test cases
- Preset the data
- Write the step design
Set the data and execute
Run the campaigns
- Set up the test data
- Execute the running campaign
Steering and Monitoring
Management and monitoring of the test project
- Manage the defects
- Manage the business coverage
- Manage the rest to be done
- Formalize the minutes
Guarantee
Regression test
- Automated testing
- Automatic Execution
Agile cycle
Issues
Today more and more projects are managed in agile mode.
The agile context causes an improvement in the development cycle and improved management of the project pace. You can complete the agile context of an agile quality control adapted to this new mode.
Constraints
Quality control must be adapted to agile context.
It includes tests to validate the increments (Sprint). Tests need to be added to validate each of the increments given in their business context (in view of the overall solution).
- In order to not alter the speed of the project, they will have supported:
- Parallel works and a fast pace.
- Short lead times and a fixed identical duration.
- A daily Piloting.
- The development team is focused on building the application.
- An agile quality control enables:
- Respect the pace of delivery, the dynamism, the involvement of development teams.
- Ensure the quality standard goals.
- Monitoring the business coverage.
- Monitoring of functional coverage.
- Safety Golives.
- Detection of blocking defects prior to production.