Shulou(Shulou.com)06/02 Report--

Software testing accounts for more than half of the workload in software development, and there is a large demand for jobs and a large talent gap. In the field of IT training, the introduction to software testing is not difficult. As long as you are willing to study hard, no matter what your major is, you can enter the software testing industry.

For novice software testers, this article provides a number of small knowledge points about software testing, which novice software testers must keep in mind:

01. Software testing (the significance of software testing)

1. The process of finding errors in a program and executing the program.

two。 Verify that the software meets the needs of users

3. Improve user experienc

02. Principles of software testing (common sense)

1. Intervene as early as possible (intervention in demand analysis)

2. Trace back to the needs of users (don't work behind closed doors)

Programmers should avoid checking their programs, except for unit tests. Positive test + negative test 28 principle, 80% of errors are concentrated in 20% of modules (aggregation effect)

4. There is a process of confirming the wrong results (do more tests, record the test process, occasional BUG)

5. Make a strict test plan (start time, responsible module.)

6. Complete testing is impossible, and testing needs to be terminated (there will be some reasonable BUG that will not affect the user experience and use. These BUG may not be changed until the next version).

03. Classification of software testing

1. According to the testing phase:

Unit testing, integration testing (both developers and testers can do it, interface testing is divided into integration tests), system testing (a complete and overall test, not Android or Apple), acceptance testing (formal acceptance testing, Alpha testing, internal testing of Beta testing games, pre-release version, public testing)

Note: Alpha testing: pre-user testing, acceptance testing under simulated actual operating environment (internal testing) belongs to the development environment, development and testing can not participate in Beta testing: late user testing, real environment (public testing), development and testing can not participate in the same point: development and testing can not participate in different points: Prophase and later, the development environment and the real environment

Second, according to the testing technology:

White box testing (code level), black box testing (discovered by external operations and surface reactions), gray box testing

Third, divide it according to the content contained in the test:

Function test (dot-by-dot), interface test (UI interface), security test, compatibility test, ease of use test (easy to use), performance test, stress test, load test, recovery test (disaster recovery, self-repair)

4. Other tests:

Smoke testing (backbone testing before release, before real testing), regression testing (verifying whether the BUG repaired by the test and its related functions are normal), exploratory testing (test thinking) random testing

04. The life cycle of software testing (six phases)

First, the problem definition and planning stage mainly determine the purpose and feasibility of software development, and formulate a development plan.

Note: boss, product manager, R & D, project manager, demand analyst to do it.

Second, requirements analysis / review phase analysis source (prototype diagram / software requirements specification), participants (host-product manager, other participation, research and development, design, testing), focus on one question-what is the purpose of testing to participate in this requirements analysis? (know yourself, know the enemy, and make it easy to ask questions)

Third, the software design stage (attribute: belongs to the development work) outline design (database table and other framework things) detailed design (pseudo code level)

IV. Developer tasks and programmer coding in the software coding phase

Fifth, the task of the test engineer or the task of development in the software testing phase: unit test, development or test: integration test-interface tester: system test, customer or product manager: acceptance test-Alpha test, Beta test

VI. Software operation and maintenance phase version, product launch (version upgrade and improvement) BUG repair

05. Workflow of software testing

First, which positions do you come into contact with

Development, product manager, customer service, implementation / technical support / field implementation, designer

Second, the workflow of the test:

1. Test requirements analysis phase:

Read the requirements / understand the requirements, sort out the demand points, and catch all the areas where you have questions, discuss them, and figure it out.

2. Test plan phase:

One document: the test leader / team leader makes a plan

What is included:

① purpose: we want to complete the test, about when to complete, what kind of goal to achieve. ② staff: who is involved and becomes the test team.

③ task division: who is responsible for which functional module testing / use case writing.

④ schedule: when to start writing use cases, when to start testing, when to finish testing, and when to launch.

Documentation issued by ⑤: use cases, bug lists, test reports.

Application / preparation of ⑥ resources: apply for a server? What kind of test am I going to do? What kind of tools do you need to prepare?

3. Test design phase:

Write test cases:

① review: review each other whether the use case is complete or correct or not OK

② modification: understanding error: correction, requirement change: modification

Test execution phase

A smoke test will be carried out before the test (pass, continue, fail, call back),

Execute the test according to the test case:

① found that bug-- was submitted to the bug management system.

After the ② development has been fixed, you need to verify it and then do regression testing.

4. Test and evaluation phase:

After the test, issue the test report.

If you pass the test, you will be online, and if you fail, you will call back, modify, and retest.

This article is written by the source time teacher. The purpose of this article is to help novice software testers better master the knowledge of software testing. )

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.