What is software testing?
Software testing is the use of manual or testing tools to test the product j according to the test plan and process.
one. Test introduction
What is software testing?
Use technical means to verify that the software meets the requirements
Use technical means to verify that the software meets the requirements
Understanding software and testing
What is software?
Chat, E-commerce, Operating Systems
Software: Tools that control the work of computer hardware.
Page Client -> Request Code Server
Page Client - "Request Code Server" Request Data Server
Page Client -> Request, Response Code Server - "Request Response Data Server
Software Control Hardware Tool
03-Software generation process
Demand generation (demand side, customer, user, product manager) - "demand document product experience demand document product manager, design renderings (UI designer) - " product development - " R & D personnel
product development - " product testing - " deployment upper limit
04 What is software testing
Use technical means to verify whether the software meets the needs of use
Reduce software bugs and ensure quality
Tools to control the work of computer hardware
Use technical means to verify whether the software meets the needs of use
Tools to control the work of computer hardware.
What is software testing?
1. Functional testing
2. Automation testing
3. Interface testing
4. Performance testing
Mainstream suggestions:
1. Functional testing + interface testing
2. Automation testing + interface
3. Function + performance
function, automation, Interface performance test
Function test + interface test, automated test + interface
function + performance
Automated test + interface
function + interface test
two. Test mainstream skills
Automated testing:
what is software: a tool to control the work of computer hardware
What is software testing: use technical means to verify whether the software meets the needs of use
The purpose of software testing: reduce software defects and ensure software quality
05-Mainstream skills
1. Functional testing
Verify documents when executing functions,
2. Automated testing:
tools or code to execute him
Use code or tools instead of manuals to test the project
Use code or tools instead of manuals to test projects 3. What is
interface testing
interface?
Request login - "Call
interface test, use code or tools to test the interface provided by the server.
Background development
3. Interface test - tool implementation
4. Performance test - tool implementation
Simulate multiple people using the software to find server defects
Functional test + interface test
Functional test + performance test
Functional test:
test whether the function of the main verification program meets the requirements
Automated test:
use code or tools
2. Commonly used categories for testing
Classification
Stage division (stage: software production process sequence)
code visibility
2.1 Stage division
unit test
Description: Test the program source code (unit: the smallest independent functional code segment)
Tips:
1. Domestic unit testing is generally developed for self-testing
2. Unit testing can be solved - quickly locate defects
and use technical means to verify whether the software is Satisfy requirements 1 1. Functional testing
2. Automated testing
3. Interface test
4. Performance test
Mainstream suggestions:
1. Functional test + interface test
2. Automation test + interface
3. Function + performance
123456789
3. Improve test execution efficiency
Integration Testing
Description: Test for the interface between the unit and the unit
Tip: Test the interface of the symmetry.
System test
Description: For the overall function of the system + compatibility + documentation (description, installation documentation)
Acceptance Test
Internal testing: used by internal personnel of the company, found defects and fixed them.
Public beta: Let users help with the test
Tip: Acceptance test, it is generally decided whether to use it according to the type of project
Unit testing: There are
too many bugs to test the program source code. Unit testing: Testing the program source code.
Integration testing: Also known as interface testing, testing the access addresses between modules.
System testing: testing the entire system, including functions, Compatibility, documentation and other testing
System testing: Test the entire system including functional, compatibility, documentation and other testing
Acceptance testing: Special projects
are mainly divided into internal testing, public testing, and use different groups of people to discover project defects
2.2 Code Visibility Division
Code Visibility: The degree of code visibility is divided
2.3 Summary
Black box testing: mainly for functions (stage division -> system test)
Gray box test: for interface testing (stage division -> integration test)
White box test: for Test the program source code (stage division -> unit test) black box test
: function, round test: interface test , the function is invisible White box test : all the code is visible, UI function is invisible, unit test The key core is functional testing , integration testing and gray-box testing, symmetric interface testing , unit testing and white-box testing, testing of code, automation testing, functional testing , performance testing, security testing, and special testing
3. Model
Role
Quality Model, Test Model
Quality Model, Test Model
3.1 Quality Model
Explanation: The quality model can tell us the key aspects that should be considered during testing
: function, performance, compatibility, ease of use, security
Conclusion: Whether testing hardware or software, the above points should be used to classify and verify
functionality : Requirements: 10 functions, function details, the number of functions is 10
Error handling conditions, the function is implemented correctly, the number of functions is 10
Performance:
Requirements: estimated daily online number of 20W, test server processing requests per second, server hardware Whether the configuration is satisfied
The estimated daily online number is 20W, and the test server processes the number of requests per second.
Compatibility:
Browser: Google, IE, Firefox, Oppen, Apple
Operating system: Win system: Win7, wind8, wind10, other
mobile phones: Resolution: Brand, System, Network, Other
Ease of Use:
Simple, Friendly, Smooth, Beautiful,
Brief, Friendly, Smooth, Beautiful,
Reliability:
No Response: No response occurs
Caton: Slow response time
Crashes: System crashes
Security: 4 Transmission Encryption, Storage Encryption
Portability:
Website Data Migration
Maintainability:
Quality Model: Function, Performance, Compatibility,
Fourth, the test process
Requirement review to ensure consistent understanding of the requirements of each department
Plan preparation: what to test, who will test, and how to test Use case design : Operational document to
verify whether the project meets the requirements Defect management Test report Factual test result documentation How to carry out software testing Requirements review Writing test plan
Requirements Analysis (Review)
Prerequisite: Read the requirements document once and record any unclear points.
Participants: front-end, back-end, testing, product purpose
:
1. Ensure that each department has a consistent understanding of the requirements
2. Each role checks and fills the gaps in the requirements
3. Understand some functional
tips of the software: Requirement analysis stage -> software Not yet implemented (just now)
Test Plan
Description: Documents that guide test execution (important)
what to test (target, scope)
who will test (personnel progress and arrangement)
how to test (test tools, test strategies)
use case design
Description: Documents guaranteed to accurately verify the execution of software test points.
1. Analyze requirements
2. Extract test points
3. Design use cases to cover test points
use case execution
Description: Implement the test
defect management
Submit -> Validate -> Close
testing report
1. Bug analysis and statistics
2. Problems encountered in the
test 3. Test summary (the advantages and disadvantages of this test)
1. What is a use
case ? _
4-1 Use case design writing format
Use Case Title, Project, Module , Precondition, Test Step, Test Data , Expected
Result The importance or influence of the use case P0-P4 (P0 is the highest) Preconditions: What are the preconditions for this use case to be executed Test steps: Describe the operation steps Test data: The data to be operated, can be empty if there is no prediction result Use case number , force title, project/module priority preconditions, test steps, test data, expected results Login button, 1. Account number: Empty 2. Password: 123455 Login failure: Prompt to be rooted or not to be empty Test case design: 1. Can design test points for exhaustive scenarios 2. Can design test points for limited boundary rules 3. Can Design test points for multi-conditional dependencies 4. Can design test points for project business. Among all test data, data sets with certain common characteristics are divided. Effective equivalence class: data set that meets the requirements. Invalid equivalence class: Data sets that do not meet the requirements Clear requirements: Requirements: 6-10-bit natural numbers 1. Clear requirements 2. Divide valid equivalence classes and invalid equivalence classes Valid 8 bits Invalid: 3 bits, 12 bits Extract data writing use case 12345678
123
12345512312312
Length 6-10 digits
Type: natural number
Effective: 8-digit natural number
1. Clear requirements
2. Determine valid equivalence and invalid equivalence
3. Design data writing use case
Area code
Prefix code
Suffix?
Area code
Combination if valid data can be combined
3. Design data writing use case
tel_001 Legal (area code is empty + other correct) phone p0 punch card verification phone 1 , enter the area code 2, enter the prefix, 3, enter the suffix 4. Click to verify
1. Area code: empty 2. The prefix 234, 3. The suffix 1234
is illegal (the prefix is a non- and non-starting 2-digit number) Target
: need to have A lot of data test input, but there is no way to be
exhaustive
5. Test Cases
Use cases: cases
used by users Use cases in life: The role of
use cases
1. Prevent missed testing
2.
Use case template
submission to measure whether the software passes -> Validation -> Close 1 1. Bug analysis and Statistics
2. Problems encountered in the
test 3. Test summary (advantages and weaknesses in this test)
123 1. Preventing missed tests
2.
Writing specifications for the eight major elements of the standard for measuring whether the software passes or not
Practice case black-
box testing: Do not focus on the source code for the function
Gray test: for the interface
White box test: test for the source code
Special: performance test, security
Quality model: 1. Function 2. Performance 3. Compatibility 4. Ease of use 5 Security
function, performance, compatibility , Ease of Use, Security
Requirements Review, Test Planning 3 Use Case Design 4 Use Case Execution 5 Defect Management
6 Test Report
Requirements Review: Product Manager, Development, Testing
Requirements Understanding, Knowing What Is Tested
Use Case Design: Design for Exhaustion
Use Case Execution
Defect Management
Test Report
Test Number
Use Case Title
Project Block
Priority
Precondition
Test Step
Test Data
Expected Condition
Preconditions, Preconditions: Operations before the operation
steps Test steps: Use case execution steps
Test data: Key data in the execution steps
Expected results: Use case execution results + different orange invisible results
Expected results: Use case execution results + different roles are invisible Result
Exercise case
Exercise review
Xin Xin WeChat Moments
1.
Success (1 picture)
2. Success (1 paragraph of text)
3. Failure (empty content)
6. Use case design method
Goal
1. Ability to design test points for exhaustive scenarios
2. Ability to design test points for limited boundary rules
3. Ability to design test points for multi-condition dependencies
4. Ability to design test points for project business
6.1 Ability to design test points for exhaustive scenarios
Exhaustive: Endless
Method: Equivalence Class Division
Introduction:
Case 1 (qq program)
Case 2 (telephone)
Requirements: 6~10 natural numbers
Case 2 (Phone)
7. Homework
