review
APP special test (compatibility, install, uninstall, upgrade, crossing event, the PUSH message, the performance of other types)
Project environment (development environment, test environment, quasi-production environment, production environment)
APP closed beta publishing platform (dandelion, fir.im) support apk, ipa
APP online publishing platform (Android, IOS)
Agile development model (customer needs, iterative, step by step)
SCRUM model (three roles, PO, SM, DEV Team, four meetings, sprint, backlog)
APP testing process (needs assessment, test plans, test cases, test execution and BUG tracking, test report)
learning target
-
Grasp the point Like Comment Function Point written Cases
-
Function Point grasp upload an avatar to prepare patients with
-
Master personal authentication information written in cases of points
-
Familiar with the test plans and reports prepared by APP
-
Learn fiddler weak network testing
-
Learn fiddler phone capture
Real-name authentication function - needs assessment
-
Fuzzy demand, unclear
-
Demand is not complete
-
Demand can be optimized to improve
Dark horse headlines - content of the test plan included
-
Overview of the test (objective, scope)
-
Task scheduling and rounds arrangements (containing the person in charge of the task)
-
Test program (strategy)
-
Risk assessment test
-
Some standard test
Write a review to write test cases
-
Demand split test point
-
Test Example looking design point method
-
Additional test points: related business, special angle
-
-
The test points according to the needs written embodiment, a test point with at least one embodiment
Show reviews written test
-
Demand split test point
-
Test Example looking design point method
-
Additional test points: related business, special angle
-
-
The test points according to the needs written embodiment, a test point with at least one embodiment
Thumbs write test cases
-
Demand split test point
-
Test Example looking design point method
-
Additional test points: related business, special angle
-
-
The test points according to the needs written embodiment, a test point with at least one embodiment
Edit your avatar to write use cases
-
Demand split test point
-
Test Example looking design point method
-
Additional test points: related business, special angle
-
-
The test points according to the needs written embodiment, a test point with at least one embodiment
Personal real-name authentication information - write use cases
Explicit use of the process, to draw a flow chart
Written cases, one path is a flowchart of a use case (6)
And performing a defect tracking Example
Example execution
-
Conduct smoke tests before the test to avoid testing resources are wasted.
-
Soon found BUG, high severity BUG early detection.
-
Priority test high priority use cases, the risk is relatively large selection of use cases for testing.
-
Preparation of test reports
-
Test outline (after test results)
-
Defect Analysis
-
On-line risk
-
Summary, the proposed
What is a good test case?
-
Simple, efficient, clear
-
Coverage, avoid large leakage test
-
Step ordered
-
Reasonable priority
-
The only use case title
in principle
-
To fully test cases covering design, to avoid leakage test (especially serious BUG, obvious BUG)
-
A limited test cases, we find more and more serious software flaw
other requirements:
-
Test case to consider the efficiency of the implementation, to avoid unnecessary difficulties and obstacles
-
To refine the test case description is accurate, complete and clear, easy to understand
-
Test cases to find BUG (type) not seen before
-
Based on the user's actual scene Design Example
-
To avoid redundancy test case
Ethereal phone
Premise: fiddler and cell phone on the same network
-
fiddler configuration allows access to: tools - options - connections-- tick allow remote ..
-
-
Open mobile phone browser to access the fiddler in the computer tpshop website, complete capture
Fiddler's weak network testing
-
开关：rules---performance--simulate modem speeds
-
Custom speed setting rules --- customize rules
