Level 7 Testing stages

Testing stages

Before you begin to plan the testing process, you need to break the whole process into stages:

The stages of the software testing process are groups of work that determine the main direction of activities to achieve a given and defined result for the entire stage

Highlighting the main activities and grouping them into stages of work allows you to plan all activities and evaluate labor costs for a particular stage of software testing

The process of testing consists of next stages:

It is important for every tester to know!

Testing consists of such steps:

Testing process planning
Test Design
Implementation/recording test procedures
Test execution

Test Debugging
Analysis of the results

Documentation of the results

Here, it seems, everything is simple and clear. We have already discussed and passed all these stages. You can do all this individually and all that now needs to be done is a plan to carry out these actions.

Testing stages

So the time has come for a decisive phase in the battle against evil. We are getting ready to blow up the Death Star! In order to hit the enemy, we need to draw up a competent plan, build tactics and sequence of actions in a clear order.

As you guessed, we will prepare a testing plan. The pinnacle of the art of the tester, the culmination of the theoretical part, fanfare, drum roll! You will submit today the most difficult technical documentation in testing!

Testing process planning

Testing process planning

In this drop-down list you can find out what the first stage of testing (planning) includes. Actually, this level was created for this!

“Why do we need a test plan?” You ask. “After all, I have test cases, terms of reference, in the end, I already know what to do, I can tell everything on my fingers!”

And this is true. My personal opinion (and it coincides with the opinions of many employers) is that the time spent on documentation should not be comparable with the time spent on direct testing, that is not exceed about 10% of the total time spent.

For example, if you have to test only the form for sending data as at level 4, you do not need a test plan for this - you will spend more time on it than on the testing itself.

A test plan is necessary when the feature is large and it is simply impossible to keep the entire amount of work on it in your head. One of the aspects of testing cannot be missed. And for this it is necessary to put everything in a document, sort out the order of actions, consider everything “on the shore”. It is especially important to have a test plan if several people participate in the test. Then you already save time on meetings and multiple explanations of the action plan to other people.

Important facts about the test plan:

The test plan contains: scope of work, deadlines, ways to solve tasks to complete the work, resources, schedule of work

This is the main artifact that harmonizes development and testing team plans

The necessary artifact to carry out planning work on a software development and delivery of project

Sections and strategy

Main sections of the test plan

Title, Project

Change Log

Introduction
- Project identification
- Application area
- Initial data
- Purpose

Test requirements
- Testing Strategy (hereinafter)
- Resources
- Schedule

Reporting Materials

While you are still studying, C3PO has reached level 23, has become a tester and is buzzing now

Testing Strategy

The strategy is written at the very beginning. It prescribes the sequence of work, including even filling out your test plan. For example, the order of developing documentation and actually passing tests.

Work with incoming technical documentation (as a technical task)
Test documentation generation
Choosing test types, creating a test script:
- Installation testing
- Configuration testing
- Security and Access Control testing
- Perfomance testing
- Testing data and database integrity
- User interface testing
- Business Cycle testing
- Functional testing
- Testing Tools

Testing strategy

Resources

The test plan describes the resources that are needed to conduct testing within the time frame you specify. A request for resources for your specific project is formed based on the priority of the task, deadline and real resources of your company.

There are resources in testing: human ones are those roles that you will need to work on a project and technical ones are all the equipment necessary for testing.

Roles
- Сonstructor
- Designer
- Data base administrator (DBA)
- System Administrator
- Tester
- Testing Designer
- Test Manager

Technical system
- Test database
- Test server
- Test environments
- Test repository

Test schedule

Test Scope Definition
Determining the order of the execution of testing process
Determining the order of measurement of test results
Calendar plan

Although time is one of our most valuable resources, we usually do not value it enough. To correctly distribute the time-costs, the test plan contains a calendar work plan.

A feature of planning for Agile is that the evaluation is performed sequentially at each iteration. No one expects preliminary estimates to be as accurate as subsequent estimates. Improvement occurs over time, so that the team increases confidence in their abilities and capabilities.

In addition to the basic historical knowledge based assessment approach, team members at Agile often use relative assessment models in which teams develop narratives (stories) that define user needs. These stories are analyzed by teams and each story is matched by numerical values (Story Points). Story Points (SP) can be expressed in abstract units, for example, as numerical values, or in the form of Ideal Developer Days (IDDs).

In testing, as in all business processes, the time spent on the project will be equal to the project volume (number of story points) divided by the number of testers involved in the project.
At the same time, the volume of testing is determined at the beginning, then the order of testing stages is taken from the strategy, time is allocated for carrying out the resulting work, that is, reporting - and all this is recorded in the schedule

Materials for delivery

Reporting materials

Testing model

Testing Protocols
Reports of discovered defects of system

I think everything is clear here. Bug reports. By protocols we mean test cases and checklists with passing marks.

We are approaching the goal

Implementation and execution

Test Plan Templates

Design of testing process

Designing consists of four main stages. When you pass them - the main part of the test plan will be ready.

Define and describe test cases

At the first stage, you think over and outline which test cases you need to write. Then, according to this structure, you will write check lists or test cases, depending on the requirements for detailing documents.

2. Prepare an analysis of the expected workload (for perfomance testing)

In this case, the management agrees with the expected load of the project: the number of users, the number of steps in the user story for the average user. Session time, peak load and more ...

3. Define and structure test procedures

Here it is necessary to decide - which tests will initially be designed manual and which automated. Break them into sections. Define a testing approach. Break functionality between colleagues.

4. View and evaluate test coverage

After you have ready test scripts, you can evaluate the test coverage of the project functionality. Understand whether you have reached the required minimum or something else you need to cover with tests. Time to inspect the project and pretty smile after the work done.

Test plan templates

Mine give you templates! Check out. It is interesting!
According to Rational Unified Process
According to IEEE (ANSI / IEEE Standard 829-1983)
According to my personal version of WIX.com (english)

Testing process implementation

Write or program test scripts

Define special test functionality in the design model and implementation model

Sometimes companies have test functionality that simplifies routine operations. For example, a script that adds n pages to a site so as not to do it manually.

Install external test data sets

Collect the necessary data set for testing, if required. For example, card data for test payments.

My mission is to help. I will give you comments on each item of the test plan.

Testing process execution

Run test procedures

Evaluate testing (completed, not completed)

Fix failed tests

Correct, if necessary, test procedures

Check results

Analyze unexpected results

Report defects

Test score

Evaluate functionality coverage with test cases

Make sure that every important functional node is checked in a test. It is important not to forget about negative test cases.

Assess code coverage with test cases

Evaluated % code that is covered by tests.

Analyze defects

Understand the localization and causes of defects. If there are a lot of bugs in a particular place, then he needs to pay special attention, increasing the detail of the coverage, and also take this into account in regression testing. It is possible to raise a question about the problematic quality of code from some programmers.

Determine if criteria for completion and success of testing have been met.

First of all, to analyze whether testing metrics have been achieved (test coverage, verification of all functionality, etc.). And also, do you feel that everything has been checked completely, are there still critical bugs.

Practical advice

The test script should work in each test run or should be completely excluded from the test suite

Test scripts should be played from the moment of development

Cover with automated scripts detected critical priority errors

Record the key points of working with automated testing in the Product Quality Plan

In the metric of automated coverage, set the priority of the "version ban"

Do not try to create a test plan exactly the same as suggested. Each project is unique!

Try to apply the concept of "living documents"
- Use common sense ...
- and common sense!
- and ask the right questions :)

Testing Evaluation

Useful articles to read:

Test metrics

I feel that you have learned the material. Think about these questions, my student. You will find the answer in understanding this level.

This level is very important in the way of the tester. Chewbacca says that this and the next level were the hardest in his life!
Why, you have to explore the Death Star at the end of the next level. Take the decisive step in this course - take the test and complete the task. Then you will probably become already half a tester.

Test