QA Process

Running tests is necessary, as well as planning and documenting the process. Testers are responsible for developing test scenarios, as well as preparing to test and evaluating its results. It took years to develop the idea of a fundamental testing process at all testing levels. Within this process, key steps can be identified:

• planning and management;
• analysis and design;
• implementation;
• evaluation of output criteria and writing reports;
• steps to complete testing.

Here the actions are described in a logical order, but in a real project, they can overlap, occur simultaneously, or even be repeated. Usually, these steps are adapted to the needs of a specific system or project. Let’s take a closer look.

1. Planning and management

The planning of testing includes activities aimed at identifying the main testing objectives and the tasks that must be performed to achieve these goals.

During the planning process, we make sure that we correctly understood the goals and wishes of the customer and objectively assessed the level of risk for the project. After that, we set goals and objectives for testing itself.

For a more clear description of the goals and objectives of testing, such documents as Test Policy, Test Strategy and Test Plan are drawn up.

Test Policy is a high-level document that describes the principles, approaches and main goals of the company in the field of testing.

Test Strategy is a high-level document that describes testing levels and approaches to testing within those levels (at the company or program level).

Test Plan is a document that describes the tools, approaches, schedule, and resources required to conduct testing. Among other things, it defines the testing tools, the functionality that needs to be tested, the distribution of roles in the team, the testing environment, the testing design techniques being used, the criteria for starting and ending testing, and risks. In other words, this document describes the entire testing process in details.

In any activity, planning is not a final stage. We need to monitor and measure progress. This is why test management is an ongoing process.

Test Management is matching the current situation in the testing process with the plan and reporting.

In turn, the data obtained in the course of monitoring the process is taken into account when planning further actions.

2. Analysis and design

Testing analysis and testing design is the process of writing test scripts and conditions based on the overall testing objectives.

During the analysis and design process, we develop test cases based on the overall testing objectives identified during planning.

Test scenario is a document that defines the established sequence of actions when performing testing.

3. Implementation

During testing, test cases are written, based on previously written test scripts, the information necessary for conducting tests is collected, a testing environment is prepared and tests are launched.

Test case is a document containing a set of input values, pre-, and post-conditions, as well as the expected result of the test, designed to verify that a certain system functionality meets the requirements.

Test environment is the hardware, software, and other tools needed to run tests.

4. Evaluation of output criteria and writing reports

The output criteria determine when testing can be completed. They are required for each level of testing because we need to know if enough tests have been run.

When evaluating output criteria, it is necessary to:

• check whether an adequate number of tests have been run, whether the desired degree of system quality assurance has been achieved.
• make sure that there is no need to carry out additional tests. If there is such a need, it may be necessary to change the established output criteria.

After the end of testing, a report is written, which will be available to all interested parties. After all, not only testers need to know the test results – this information may be necessary for many participants in the software development process.

5. Steps to complete testing

By the end of testing, we collect, organize and analyze information about its results. It may come in handy later – when releasing a finished product. There may be other reasons for finishing testing, for example, early project closure or completion of a certain stage of development.

The main objectives of this stage:

• to make sure that all planned functionality has been implemented;
• to check if all earlier submitted bug reports were, in one way or another, closed;
• shutdown of the testing software, testing environment.
• to evaluate the overall testing results and analyze the experience gained in its process.