Third Acceptance Testing - ALL4TEC



Third Acceptance Testing

Objectives of third acceptance testing

Third acceptance testing is a shared way of organizing work and test acceptance, where different client companies cater to the same team, which reduces the costs of such a structure. This helps balance the load of each tester to clip the peak load and fill the hollows of activities, while reducing costs through optimization of inactivity. It is very interesting for ALL4TEC customers to limit periods of non-billing and gain the ability to sell their services at a better cost.

ALL4TEC added value

All4tec has learned from its experiences on Model Based Testing, through IT and industrial projects, rewarding returns, on which we are able to capitalize on the best practices, tips, and lessons. All4tec proposes to apply these best practices to define the test strategy of the pilot system so that it meets its ambitious quality and robustness goals, and is perfectly suited to the user’s needs in a multi-teams context.

Breakdown of the activity

 

Step 1 is intended to analyze the context of the acceptance testing so that All4tec can identify its scope and determine its objectives. Once the scope has been defined, it is submitted to the client’s acceptation.

During Step 2, the test model is designed and it automatically generates test suites thanks to MaTeLo.

The modeling phase ensures the systematic identification of unknown use cases. Compared with a traditional approach, modeling allows to discover use cases that could not be necessarily imagined.

The original test generation strategy adopted by ALL4TEC basically involves first to meet the objectives set by the client to Step 1 and then to correct the many potential bugs and quantify the reliability obtained after the test. We also guarantee the optimized way to cover the test objectives identified in Step 1.

Therefore our approach is divided into two distinct parts:

-> The debugging phase: The number of generated test cases is optimized by trying to focus on test cases that may reveal bugs.

-> The qualification phase: MaTeLo generates user oriented test cases. The stopping criterion of this phase is reached when the estimated operational reliability is acceptable.

Step 3 is to automatically generate scripts and run the test plan.

Some tests cannot be automated, it is necessary to introduce a tester that will perform "by hand" the supplement of the test plan generated by MaTeLo.

Reports containing test results are extracted and used to provide a global view on the test indicators presented in different forms: Table, Dashboard, Graphic...  

The tester collects all relevant information to the proper definition of problems. It also makes proposals for solution to remove a defect or bypass it.

At the end of Step 3 a meeting with the client decides whether the system under test can be accepted or not.

Our engagement

All4Tec, MaTeLo editor, applies the best practices in complex systems testing. We guarantee the stability of our resources, managing motivation of our teams to accompany you in the long term. We capitalize both on the team and on its expertise. Our engineer’s motivation to work on the design of automated tests, compared to the traditional manual validation, is an additional guarantee of the stability and performance of our team.

Contact Us: +33 180 750 755