How we work

 

Code Q’s Approach to Test Automation

 

The above services relate closely to Code Q’s main components of the test automation process. For every step we offer a specific approach built to minimize the risks of possible disruption of the automated testing process, and to optimize the costs of testing. Depending on the particular circumstances and stage of a project, the Code Q team will suggest the most relevant interaction options and service levels.

 

 

Initiation

 

During the initiation stage, the greatest amount of time is spent gauging the functional scope of a project and completing the required knowledge transfer. Therefore, identifying the core functionality underlying the UI and the application business logic will help a project team gear up for work. In this phase, the key requirements for automated testing are outlined, and the implementation cost calculation methods are mapped.

 

 

To facilitate a smooth kickoff, Code Q has a number of ready-made project templates (frameworks), which require minimal effort to roll out a working version of automated tests within a short time frame.

 

 

Each testing scenario goes through acceptance tests for all possible input data. Once the initial test has been run, the automated tests are executed on a daily basis. Run in different environments, the tests may reveal application defects as well as inconsistencies in the automated tests themselves.

 

 

Test Development

 

During this stage, the majority of time is spent on description, development, testing and execution of automated tests. We seek to minimize the resources engaged in developing general functionality.

 

Should the project scope require more resources for test development, the team can be expanded easily, at no risk, thanks to the successfully completed initial phase.

 

 

Depending on the project size, the test development stage can take considerable time. When this is the case, to ensure interim results delivery we recommend dividing the active development stage into short phases.

 

 

Automated Test Execution

 

The extent of support provided for automated tests depends on the number of change requests affecting the business logic and UI of the tested application.

 

 

With our approach to automated tests development, the impact of such changes on the automated tests execution will be kept to a minimum. The controls we use are based on more “stable” and unique object properties. Custom application content, like menu or certain business logic rules, is stored outside of the code. With this approach there is no need to seek additional help from developers to incorporate changes to automated tests.