Software testing zero-based quick start

Basic concepts of soft testing

Soft test definition

Software testing is a series of testing processes from the review of requirements documents in the early stage, to the design of test cases and test execution in the mid-term, to the submission and closing of problem tickets in the later stage.

80/20The principle means that 80% of the bugs are concentrated in 20% of the modules

Software classification

Black box testing: It is a test that does not pay attention to the structure and algorithm of the internal code of the software, but only focuses on all the functional characteristics displayed outside the software

White-box testing: The definition of white-box testing is just the opposite of black-box testing. White-box testing is a test that only focuses on the structure and algorithms of the internal code of the software, and does not focus on the functional points displayed outside the software.

testing phase

Unit testing: used to test the code, using the method of white box testing
Integration testing: use black-box testing for modules obtained from unit testing
System testing: test whether the 6 aspects of software appearance, interface, function, performance, security, usability, and compatibility meet the requirements in the requirements document (testers intervene at this stage)
Acceptance testing: tests performed by users

Soft test plan

Five categories of soft test plan: test scope, test environment, test strategy, test management, test risk

Key points of testing strategy

Test basis: determined according to requirements documents and test cases
Test access criteria: start the test after clarifying what conditions the system meets. The access standard is generally a smoke test (that is, test the basic function points before the system test, and start the system test only if the results are all passed)
Test tool: selenium
Test focus and method
Test standard:

Test management: mainly refers to the distribution of test tasks, the arrangement of time schedule, and communication methods.

Test risks: Common risks include incomplete understanding of requirements documents, underestimation of test time, and inadequate test execution

Soft test plan template

1. Document Identification
2. Test Purpose
3. Test Scope
4. Test Environment
5. Test Strategy
6. Test Management
7. Test Risk

test case design

A test case is a set of test inputs, execution conditions, and expected results prepared for a specific purpose in order to verify whether a specific requirement is met

The test case is the basis for the tester to execute the test. It is a very critical document. It serves as the standard of the test and guides the tester to carry out the test work.

Test Case Design Method

The basic idea of testing: testers need to test any data within the limits of the requirements document; testers also need to test any data beyond the limits of the requirements document

等价类划分法
Divide all possible input data into several areas, and then take a small number of representative data from each area for testing

The data that does not meet the requirements specified in the requirements document is called an invalid equivalence class
A valid equivalence class meets the requirement document requirements

The following picture shows the test data for the normalization of the username format filled in during registration

[External link picture transfer failed, the source site may have an anti-leeching mechanism, it is recommended to save the picture and upload it directly (img-OZfYaSIQ-1681816679733)(./img/softtest/st1.png)]

边界值分析
The boundary value analysis method is to take some data slightly above or slightly below the boundary for testing

错误推测法
Testers rely on their intuition, testing experience, and divergent thinking to design some test points that are likely to cause software errors

正交表分析法
For example, if we need to test the contents of three input boxes at the same time, we must use the orthogonal table method

[External link picture transfer failed, the source site may have an anti-leeching mechanism, it is recommended to save the picture and upload it directly (img-1mP8LELM-1681816679736)(./img/softtest/st2.png)]

The causal judgment method
is mainly used for test procedures with more complex logic

Test Case Review

Testers generally perform test case review based on the following five points
(1) Whether the test case is written according to the requirements document.
(2) Whether the execution steps and input data in the test case are clear, concise, and correct; whether the execution steps with high repetition rate have been simplified.
(3) Whether each test case has a clear expected result.
(4) Whether there are redundant use cases (invalid, equivalent, redundant use cases) in the test cases.
(5) Whether the test case covers all the function points in the requirements document, and whether there are any omissions.

test environment

There are two main architectures of the software system: the software system of the browser/server (B/S) structure, and the software system of the client/server (Client/Server, C/S) structure

B/S architecture, for junior software testing engineers, they need to be familiar with the testing methods of using various browsers under the windows platform, and at the same time be proficient in setting up virtual machines in vmware

C/S architecture, you need to be familiar with the windows server platform and manipulate the database

record bugs

How to log a bug

A bug can include the following information points

[External link picture transfer failed, the source site may have an anti-leeching mechanism, it is recommended to save the picture and upload it directly (img-KCNoHdZE-1681816679736)(./img/softtest/st3.png)]

Regression Testing

The previous round of bugs was fixed, and new bugs may be found in the next round of testing. It does not mean that after the previous round of bugs are fixed, there will be no other problems

Software testing is not completed in one round of testing. Under normal circumstances, a software product may need to go through multiple rounds of repeated testing and verification before it can reach the online standard.

Soft test report

Below is a simple testing basis report template

1. Purpose of writing
2. Module function description
3. Test process
4. Test environment
5. Function point test scope
6. Test execution results
7. Risk assessment
8. Test conclusion

interview analysis

The work of software testing pays more attention to the hands-on ability and communication ability of testers

When the company recruits junior software testers, only about 35% of the companies will give written test questions, and most companies do not have written tests for recruitment, and mainly conduct interviews directly on the candidates' resumes

What principles should software testing follow?
Reference answer: I think software testing should follow the 80/20 principle, that is, modules prone to problems or modules with more problems should be tested emphatically.

At what stage is software testing involved?
Reference answer: In general, for functional testers, we intervene during system testing.