Article Directory
1 Introduction
Common defects include processing scenarios and software testing life cycle and content
- NEW: New state refers to the testers found a flaw and submit a new defect is also known as new state (usually submitted to the head of the test or development)
- OPEN: After opening the state testers found a flaw submitted to the test leader, test leader confirm that it is a defect, the defect will be set to open state
- ASSIGN: assignment status after the test leader confirmed that this is a defect, the defect is assigned to the appropriate developer at this time is set to the defect state Assign
- REJECTED: do not accept the state of development of the defect is not considered a problem, the problem will set the tester is REJECTED status assigned to submit a question
- DEFERRED: delay processing state, the development of accepted defect, the moment did not have time to modify, the defect is set for the state, test personnel assigned to solve the problem after submission
- Duplicate: repeatedly submit state, after receiving the development defect, found that the defects and defects before submitting the same or similar, the defect will be set to repeatedly submit state. Assigned to testers submit a question
- Fixed / TEST: Corrected a bug / defect can be accepted after the test development, determine its problems, and has been corrected, it will issue at this time is set as fixed / testable. And assigned to testers submit a question
- Reopened: Reopen when the testers tested again and found the developers state Fixed / TEST defect or not correct it, put the issue reopened and assigned to development
- VERIFIED: Confirmed state, testers test again when developers really the problem has been repaired successfully
- CLOSED: closed state, the defect test pass again set to the closed state
2, how do random defects
- 1, record submitted
- 2, try to reproduce the problem, looking for a developer to see if you can reproduce
3, controversial defect
- 1, see the Requirements Document
- 2, to confirm product demand
4, how to put defect entry
- 1, submitted to the test leader, test leader to make allocation
- 2, submitted to the R & D group leader, head of research and development to make allocation
5, software testing life cycle
Test Plan -> test design, test development -> test execution -> Test Evaluation
6, V model of software testing
用户需求 验收测试
需求分析与系统 系统测试
概要设计 集成测试
详细设计 单元测试
编码
7, double V model of software testing
- W model increases the verification and validation activities to be carried out simultaneously in each software development phase. W model consists of two V-shaped models, representing the testing and development process, the drawing clearly shows the parallel relationship between the test and development.
- W model features: the object is not only a test of procedures, requirements, design, etc. also have to test, test and development are carried out simultaneously
- W model advantages: in favor of a comprehensive identify problems as early as possible. For example, after the completion of requirements analysis, test personnel should be involved in the verification and validation of requirements in order to find out where the problem lies as soon as possible. At the same time, demand for testing is also beneficial to keep abreast of item difficulty and test risk for early development of response measures to significantly reduce overall test time, speed up the progress of the project.
- Limitations: requirements, design, coding and other activities are considered serial; testing and development activities to maintain a linear context, completely finished on a stage, before the official start of the next phase of work. Unable to support iterative development model. For the current complex and changing software development, W model and test management is facing not relieve the confusion.
8, software test cases
Requirements documents as follows:
phone number
- 1, accept only Arabic numerals, requirements for the 11 mainland phone number, do not meet the requirements given: "Mobile number format error"
- 2. Enter the number has been used, the error: "This phone has been registered, use another number."
- 3, Required, if not fill in the text box to display the text: "Please enter the phone number."
- 4, if not fill and click Next, an error in the text box: "Please fill phone number"
Test Points
- 1, less than 11 mobile phone number
- 2, more than 11 mobile phone number
- 3, non-mainland mobile phone number
- 4, mobile phone number with illegal symbols (letters, special characters, spaces, etc.)
- 5, 11-bit format but does not conform to the phone number
- 6, a variety of different carriers and different number of segments
- 7, enter the phone number of characters long
- 8, check the error message does not meet the time requirements
- 9, enter the phone number has been registered and checked tips
- 10, the default check box input message
- 11, the phone number is not filled directly click Next, check the message
9, software testing Category
Stages by: unit testing, integration testing, system testing, acceptance testing
- Unit Testing: debugging function is generally called, refers to the developer to test a function executed after completion of the development, developers generally test themselves, but also a professional engineer white-box testing
- Integration testing: testing called FBI development, a single developer after completion of the test sources, and other developers to test the joint process (where most defects)
- System test: After integration testing, all of the code released to the system under test, testers deployed from the installation of the system under test to check (service function, the system environment, etc.) testing the core functionality is generally complete by the test engineer responsible for, it is one of the most central part of
- Acceptance testing: the user is docking. α test: customer representative to the software company, with the testers, one by one to check whether the software is implemented according to product instructions; β test: (beta version) to develop good software is deployed to the client company, to the customer after the training finished, problem by the customer to try, made by the process of
According to whether to perform the test program
- Static test unit testing, white box
- Dynamic black box testing, functional testing
Smoke testing: For each new version of the developer submitted by the main core business functions for verification.
Regression Testing: Verify that the problem is repaired before and verify whether other functions are correct
Testing installation, uninstallation, compatibility, ease of use, power consumption, network
Performance Test
Load Test: test specified maximum system
pressure Test: Test system limits
Stability Test
10, software testing experience
It found that only 80% of the testing phase, the remaining 20% to 80% will be exposed when a large area, as well as the remaining 20% will be gradually exposed after long use
学如逆水行舟，不进则退
