1. First look at the scope of changes, if the scope of changes is small, you can retest
2. If the scope of the change is large, you can discuss with the product to complete the change in the next version, or delay the release to extend the test time
3. If you can’t get the test time, work overtime to complete it, and write down the demand change in the test report to avoid back-ups
Software testing process (how to carry out the test)
Requirements review
Is the demand reasonable
Whether the demand is measurable
Test Plan
people
time
Business point (what functions to test)
Resources (what tools to use)
Test design (some companies don’t have time to do it)
Test case
Fully test
Test execution
Test environment build, test tool build
bug submission
New version released
New function test
Regression Testing
Test report summary
Summary: requirements review, test plan, test case design, execution test, test report
testing method
According to whether to view the code is divided into: black test, white box test, gray box test
White box testing (structural testing, logic-driven testing)
Disadvantages: relatively expensive, unable to detect missing logic in the code
Advantages: It can detect every branch and path of the code, reveal the errors hidden in the code, and test the code more thoroughly
Checking the internal logic of the program and testing all paths is an exhaustive path testing method
Black box testing (functional testing, data-driven testing)
Do not check the logic inside the code, only check whether the program function is used normally according to the requirements specification, whether the program receives input data properly and generates correct output information
Test method: equivalence class division (effective equivalence, invalid equivalence), boundary value division, causality diagram method, scene method
Advantages: easy to implement, no need to focus on internal implementation
Disadvantages: relatively low coverage
Gray box testing
A comprehensive testing method that combines black box testing and white box testing, a method of designing test cases based on the external performance of the program and the internal logic of the program
Divided by development stage: unit test, integration test, system test (smoke test, regression test), acceptance test
Unit testing (initial stage of development)
Object: Code Module
Task: module interface test, module partial data structure test, module boundary condition test, all data path test in the module (usually white box test)
Advantages: Errors can be found as early as possible, reducing the cost of modification
Integration testing (after unit testing)
Object: Unit tested module
Task: It is expected that the problems existing between the broken source interfaces will be returned through the test, and finally the tested units will be combined into software that meets the design requirements
System test
Perform testing activities on integrated software and hardware systems
System testing is the most important, because system testing is the stage when the overall function of the product is relatively complete and can best reflect the defects of the product.
Acceptance Test
User-oriented testing, testing for the core business testing process
Regression Testing
A test performed when the old version of the bug is fixed to confirm whether the modification introduces a new error
Comparison between integration test and system test
Testing perspective: Integration testing focuses on testing from a technical perspective, while system testing focuses on testing from a business perspective.
Test content: Integration test is to test the interface between each unit module, system test is to test the function and performance of the entire system;
Pay attention to: response time, throughput, number of concurrency, number of responses that can be completed per second, cpu occupancy rate, power consumption, network
Test Moments
function test:
Interface/Ease of Use Test : Whether it meets the requirements, beautiful and convenient
Interruption test : switch between front and back, lock screen and unlock screen, reconnect after disconnection, SMS call interruption, plug in and out of headset or data cable
Network test : network of the three major operators, network switching (wifi, 4g, 2g), no network test, weak network test (delay, packet loss)
Compatibility test : Android mobile phone terminal, Apple mobile phone terminal, pad terminal, etc.
Safety test :
Performance testing : response time, throughput, memory usage, etc.
Test a bag
Do you have any specific requirements for luggage?
Function test : size, thickness, capacity, load-bearing of each surface, etc., whether the pull rod is flexible to retract, and whether it is convenient to unlock and unlock
Interface test : whether the material, color and pattern meet the requirements
Usability test : Whether the handle of the pull rod is non-slip, whether the zipper opens and closes is dragged
Compatibility : Does the box roller support sand, mud, etc.
Safety test : Whether the material is non-toxic, whether the corners are smooth and without edges or corners
Stress test : long time load
The difference between web testing and app testing
The difference between web and app
The web is a b/d architecture, based on the browser; the app is a c/s architecture, based on the client. As long as the server is updated in the web, the client will be automatically updated, and the app cannot guarantee that the client is updated in time, because the update of the app requires the user to actively complete it. If the server is modified in the app, it means that the client user uses it. All new versions used by users are subject to regression testing.
Performance aspect
Web pays attention to response speed, app also looks at battery, traffic, cpu, memory
Compatibility
Web is based on the browser, mainly depends on computer hardware, computer system, app depends on mobile phone or tablet, focus on whether the system is Android or ios, and care about resolution and screen size
Divided into several stages, each stage has obvious stratification, the result of each stage will be used as the input of the next stage, emphasizing the document. You can see the results after the entire cycle is almost complete, and then test
Disadvantages: no iteration and feedback, unable to adapt to the changing needs of users, and the cost of later changes is relatively large
Agile model
Work in a short iterative cycle, emphasizing fastness, delivering some results each time, emphasizing the development of software instead of documentation, allowing customers to participate, and quickly responding to new needs
Features: Take user needs as the center, and each iteration cycle needs to be tested
V model and W model
V: Put testing after requirements analysis, system design and coding
W: Test activities and development are carried out simultaneously. The test object is not only the program, but also the requirements and design
Understanding of the test
Testing is to more likely find product defects and avoid major problems after going online; inspection of development results
Discover and locate the cause of the BUG as deeply as possible, to a certain extent assist in the development and find a solution to the problem
Why test
Why not develop and test
Compared with development, the development intensity of testing is not that great, and the career life span is also longer.
As far as the testing industry is concerned, it belongs to a sunrise industry, and now there is a big gap. Nowadays, more and more attention is paid to the quality of software, and the testing industry is still very developed.
For myself, I think my personality and abilities are more in line with the needs of the test.
Why not do safety testing
The security industry requires very in-depth security knowledge. At present, our school’s training of information security is actually more focused on the computer. There are not many courses in security. First, it is not competitive in the development industry, but it is also our own. Not much interested
How to write test cases
Use case number
Use case title
Function module name
Precondition
Input data
Steps
expected outcome
priority
Results of the
Executor
As a software test engineer, what qualities and abilities should be possessed
Hard skills
Computer knowledge: operating system, computer network, and at least one programming language
Test knowledge: various test theories, test methods, test case writing
Business analysis capabilities: including familiarity with the hidden requirements and functions of the product
soft skill
Communication skills, patience, responsibility, patience