1) The difference between a test plan and a test plan:
Plan: a document at the organization management level, planning test activities from the perspective of organization management;
Scheme: It is a document at the technical level, planning the testing activities from a technical point of view.
Test plan: stipulate and restrict the organization, resources, principles, etc. of the whole test process, and formulate task allocation and time schedule for each stage of the test process, and propose assessment, risk analysis and management requirements for each task.
Test plan: Describe the characteristics to be tested, the test method, the planning of the test environment, the design and selection of test tools, the design method of test cases, and the design of test code. The test plan needs to be carried out under the guidance of the test plan. The test plan proposes "what to do", and the test plan clarifies the "how to do" software test cases including software test case design and writing.
Software test case design: It is considered from the design level, such as designing test cases from the aspects of functionality, usability, security, etc. Software test case writing refers to the writing specifications of software test cases, including writing format, logo naming specifications, etc.
The software test case design draws out the content of the software test case, and then implements it in the document according to the software test writing method. The two are the relationship between form and content.
The eight basic items of the test case format are: test case number, test item, test title, importance level, preset conditions, input, operation steps, and expected output.
What is a test plan?
The so-called test plan refers to a document that describes the scope, methods, resources, and progress of the test activities to be carried out.
It mainly includes test items, tested features, test tasks, who performs the tasks, and risk control.
What is a test plan?
The so-called test plan refers to the description of the characteristics to be tested, the test method, the planning of the test environment, the design and selection of test tools, the design method of test cases, and the design of test code.
In fact, the plan is often a technical pre-research of what will be done! ! !
The following is a template foreword for a test plan
This is the template for Zhihu Dashenfa. Then I used it to make a material for my own study. Each company is different and has its own documents.
Remarks: If the software test report is different from the bug report, leave a pit and add it later
Overall architecture diagram
See the catalog
1. Introduction 1.1 Purpose of writing
To provide software development project managers, software engineers, system maintenance engineers, and test engineering with test guidance on the overall function and performance of the project system, and it is also an important basis for users to determine whether the software is fully tested
1.2 Project background
xxxx
1.3 Test objectives
Before using the software, try to find the errors and unreasonable points in the software as much as possible, eliminate the errors and unreasonable points in the software, eliminate the potential errors in the software, and finally deliver the high-quality software system to the user . System test coverage: function, performance, UI, security, compatibility, capacity
1.4 Test Reference Document
GBT 15532-2008 Software Test Specification
GBT 9386-2008 Computer Software Testing Document Preparation Specification
1.5 Test submission documents
Software testing program
Software test cases
Software test report
1.6 Terms and abbreviations
Terms and definitions used in this article
Term/Concept
definition
2. Test requirements
2.1 Test configuration requirements
Category / software, version
Operating system
server
database
other
2.2 Test method
The functional test of the system uses manual testing, using the equivalence class division, boundary value analysis, error inference, and causality diagram in the black box test.
System UI tests include: usability test, normative test, help facility test, rationality test, aesthetics and coordination test, uniqueness test, quick method combination test.
System security, compatibility, hidden conversion and anti-installation, configuration testing is also manual testing
Unit testing uses white testing, and functional testing uses black box testing
2.3 Test data
The test data is mainly based on the "xxx" document, referring to the operating limits specified in the "xxx" document, and design test cases as the test data of the xx platform
2.4 Testing strategy
2.4.1 Unit testing
First, when dividing the list according to systems, subsystems, and modules, the final unit must be a functional module, or several types in the object-oriented process. Unit testing is a test to verify the correctness of functional modules and is also the basis for subsequent testing. The purpose is to find various errors that may exist in each module, so we need to design test cases from the internal structure of the program, focusing on the following five aspects:
-
Module interface: Test the data flow of the tested module.
-
Local data structure: check for incorrect and inconsistent data type descriptions, apply to variables that have not been assigned or initialized, incorrect initial values or default values
-
Path: Although exhaustive testing cannot be done, design test cases to find incorrect comparisons due to incorrect calculations (algorithm errors, incorrect expression symbols, insufficient calculation accuracy, etc.) or abnormal test flows (including different data types) Comparison of each other, inappropriate modification of loop variables, wrong or impossible loop termination conditions, etc.) resulting in errors
-
Error handling: Check whether the module has a relatively complete error handling function designed for common conditions to ensure its logical correctness
- Boundary: Pay attention to the relatively straightforward use cases in the design data flow and control flow that are just equal to, greater than, or less than certain
2.4.2 Integration Test
Integration testing is also called assembly testing and joint testing. Usually on the basis of unit testing, all modules need to be assembled into the system according to the design requirements. At this time, the issues that need to be considered are as follows:
-
Connect each module, whether the data of the module interface will be lost
-
Does the function of one module adversely affect the function of another module?
-
The combination of each child, whether it meets the expected requirements of the parent function
-
Is there a problem with the global data structure
- If the errors of the unit modules accumulate, will they be amplified to reach the level of unacceptable countermeasures. When we assemble, we can refer to the one-time assembly method or the value-added assembly method.
2.4.3 System Test
The purpose of the system test is to verify whether the software function and performance and other characteristics are consistent with the user's requirements, mainly the following types of tests
1. Functional test
Verify that the system functions meet its requirements specifications, verify that the system is functionally complete, without redundancy or missing functions. The detailed introduction is as follows:
测试范围：验证数据精确度、数据类型、业务功能等相关方面的正确性
测试目标：核实所有功能均已正常实现、即是否与需求一致
技术：采用黑盒测试、边界测试、等价类划分测试方法
工具与方法：手工测试
开始标准：开发阶段对应的功能完成并且测试用例设计完成
完成标准：测试用例通过并且高级缺陷全部解决
需要考虑的特殊事项
```~~
2.用户界面测试
测试用户界面是否具有导航性、美观性、行业或者公司规范性、是否满足设计中客户要求的执行功能、详细介绍如下边UI测试
其中，Web 测试通用方法可以参考《Web 测试检查点总结》
Test Range
Test Objective: Verify style of each window (including color, font, message, icon, title, etc.) and demand are
consistent, or in line with acceptable standards, to ensure user-friendly interface, ease of operation, and operator
co-user Operating habits
Technology: General Methods of Web Testing
Tools and methods: manual testing, visual inspection
Start standard: interface development completed
Completion standard: UI meets the acceptable standard, can ensure the user-friendliness, easy operation, and conform to user operation habits
Test focus and priority
Special considerations
3 性能测试
测试相应时间、事务处理效率和其他时间敏感的问题。介绍如下表:
Test scope: performance test when multiple users are online for a long time
Test objective: to verify the stability of the system's software performance during large-flow data and multi-user operations, and not cause system crashes
or related
Technology: manual testing, automated testing
Starting standard: automated test script design and review passed, project team handed over to system test
Completion criteria: the system meets the performance requirements of users
Test focus and priority
Special considerations
4 兼容性测试
测试软件在不同平台上的使用的兼容性。介绍如下：，
Test Range:
- Use different versions of browsers, resolutions, and operating systems to test separately
2. Combination testing of various conditions such as different operating systems, browsers, resolutions and running software
Test objectives:
Verify that the system runs stably in different software and hardware configurations
Technology: black box testing, manual testing
Start standard: project team handover system test
Completion standard: The function can be implemented normally under various different versions and different types of browsers, operating systems or their combinations (the secondary
test determines the scope of the test according to the basis provided by the development)
Test focus and priority
Special considerations
5 安全性测试
测试软件你系统对于非法侵入的防范能力。详细介绍如下表：
Test scope: password security, authority, illegality of users and administrators***
Test target: user, administrator password management, application-level security, users can only verify the operation of all of its authority to operate
the function as the; security system level, as long as there have verification system
Technology: Black Box Testing
Tools and methods: manual testing
Start standard: project team handover system test
Completion criteria
Test focus and priority
Special considerations
6 配置测试
测试在不同网络、服务器、工作站的不同软硬件配置条件下，软件系统的质量，详细说明见下表
Test scope: different networks, servers, workstations, different software and hardware configuration conditions
Test objective: to verify whether the quality of the system reaches the standard under different hardware and software configuration conditions
Technology: Black Box Testing
Tools and methods: manual testing
Starting standard: after system development is completed
Completion standard: meet relevant requirements
Test focus and priority: test priority is based on the priority of test requirements
Special considerations: software and hardware equipment issues
7 回归测试
Test scope: test types for all functions, user interface, compatibility, security, etc.
Test goal: verify that the functions, performance, etc. meet the standards required by user requirements after executing all test types
Technology: Black Box Testing
Tools and methods: manual testing, automated testing
Starting criteria: Whenever the software being tested or its development environment changes, regression testing is performed at each verified testing stage
Completion criteria: 95% of the test cases passed and passed the system test
Test focus and priority: Test priority is based on the priority of test requirements
Special considerations: software and hardware equipment issues
**2.4.4 验收测试**
用户新增呢或则修改内容，以及用户反馈问题确认
`测试项—测试方法—预计结果—实际结果—结论`
**2.5 测试资源**
人员：
角色 / 职责、任务 / 备注
Project Manager: Project Management
Test team leader: Specify test plan, program and arrange test work
Test Engineer: Perform tests
Test Engineer: Perform tests
**2.6 测试阶段及范围**
1: Test plan / test plan of the entire system / time
2: System training: training for the entire system test
3: Test involves: test cases of the real system
4: Test execution: the entire system
5: Result analysis: all test results
**2.7通过测试的标准**
一般有“基于测试用例” 和基于“缺陷密度”两种评比准则，在这里我们采用前者
1. 功能性测试用例通过来吧达到100%
2. 非功能性测试用例通过率达到95%
3. 没有高于优先级3以上的问题
备选通过方法：根据实际由开发部门经理、项目经理、测试负责人共同讨论确定本测试阶段是否结束
《系统测试各阶段准入准出规则》
**3 软件结构介绍
3.1 概述
**
xx平台简称xx,总共有xx大功能模块，分贝时：xx。每个模块需求如下表所示：
本文档描述的数据接入需求模块，需求表示及需求描述如表：Demand identification
Demand module
Description of Requirement
**4.测试用例**
测试用例文档附件粘贴即可（也可以注明测试用例访问的位置）
**5.关注点**
下面几个关注点可以参考 [测试要点]，把里面对应的内容全部填写上去就行了
**5.1 文本输入框
5.2 下拉类表
5.3 增加数据
5.4 修改数据
5.5 删除数据
5.6查询数据
5.7数据导入导出
5.8数据接入与处理
5.9其他**