Mobile application testing position
IT technology position: Develop front-end product artificial intelligence operation and maintenance big data
1. How to learn software testing:
A. Computer related knowledge
Operating system (windows mac linux)
Database (mysql)
Programming language (python, java)
B. Test theory, test method
First find a job that doesn’t require automated testing (8k)
C. Automated testing
A->B->Defect report, defect management, web automation selenium, interface testing postman, interface automation jmeter
2. Test basics
Use technical means to verify that software meets requirements
Use the least manpower, material and financial resources to find and fix problems in the software, thereby reducing business risks
3. Test mainstream skills
function test
automated test
Interface testing
Performance Testing
4. Common test categories
a) Divided by stages
Unit testing : testing the program source code. (development)
Integration testing : also called interface testing, tests the access addresses between modules
System testing : testing the entire system including functionality, compatibility, documentation, etc.
Acceptance testing : Mainly divided into internal testing and public testing, using different groups of people to discover project defects
2) Divided by code visibility
Black box testing: the code is invisible and mainly tests the program functions
Gray box testing: part of the code is visible, mainly testing the program interface
White box testing: All code is visible, mainly test program source code
Automated testing belongs to functional testing
Performance testing, security testing and special testing
5. Test strategy
Smoke test: Before large-scale testing, verify the main functions of the program to ensure that the program is testable (what should be done before testing? Pass the smoke test)
6. Model
a) Quality model
Functional performance combined with ease of use and safety
b) Test model
Software development process The role of software testing in the development process
Advantages: Testing intervenes early and testing runs throughout the entire cycle
Disadvantages: Unfamiliar requirements cannot cover all functions
Development process: requirements analysis, outline design, detailed design, coding, integration, implementation and delivery
Testing process: unit testing, integration testing, system testing, acceptance testing
7. Software testing process
a) Demand analysis (ensure that all departments have a consistent understanding of the needs, and identify and fill gaps in the needs from different perspectives)
b) Test plan (who will test what and how)
Testing goals and scope, personnel schedule arrangement, testing strategy, testing tools
c) Use case design (design documents for executing tests)
d) Use case execution (documentation of test execution)
e) Defect management (submit for verification and closure)
f) Test report (test target, test process, defect statistics, defect analysis, test summary)
test case
Use cases: cases used by users
Execution documentation designed for test projects
effect:
a) Prevent missed measurements
b) Standards for conducting testing
Use case test writing format
Eight elements:
-
Use case number: project + module + number
-
Use case title: expected results + steps
-
Module/Project: Project or module to which it belongs
-
Preconditions: operations before executing the use case
-
Priority: Indicates the importance or influence of the use case (P0~P4), P0 is the highest
-
Test steps: describe the steps
-
Test data: Operation data (if not available, it can be left empty)
-
Predicted results: expected results
Design use case methods include:
-
Observation
-
Equivalence classes, boundary values
-
Decision table, cause and effect diagram
-
Flow chart, scenario method
-
Wrong guessing, etc.