Software Test notes

Qtp

Qtp: Automated functional testing tool for functional regression testing
Free testers from complicated and ineffective test cases. You can complete the test without any errors after setting the script.
Functional Tests and scripts can be reused.

Qtp usage process
1. Recording test scripts
Generally, you can specify a program for recording.
2. Enhance the test script
Checkpoint: you can right-click to create a checkpoint
There can be multiple checkpoints (PPT)
Parameterization: Import valid or invalid use cases to the data table.
Qtp strictly follows the data table content.
3. debug the test script
VBScript language
4. Run the test script.
Run
5. Analyze the test results to find out the problem.
Click to view results
6. Generate Test report

LoadRunner

1. Start-> LoadRunner-> Application
-> Virtual user Generator
2. File-> New-> select Web (HTTP/html)
3. In the pop-up start recording
To test the website
4. After you click OK, ie will be automatically opened and
Floating Bar, complete the operation in IE,
Stop recording in the suspended bar after completion
5. It takes some time to process the script.
Save
6. Start-> LoadRunner-> Application
-> Controller
7. modify the number of people or zombie address in the upper left corner.
8. Set the test policy in the lower left corner.
You can see
9. Switch to the run tab at the bottom
10. Click Start scenario on the new page.
11. You can observe the running status during the running process.
12. After running, you can click results in the menu.
Select analyze results to Generate Test report

Integration Test(Integration Testing) checks whether the interfaces between software units are correct on the premise that each software unit has passed the unit test.

Also known as assembly testing, Joint Testing, subsystem testing or component Testing

Integration testing has evolved into functional testing and performance testing (time for processing data using methods and concurrency of methods)

Integration Testing: 1. Data Transmission and exchange between units
2. Data Error concealed in the unit, and whether the data is extended after integration
3. Is the function module correctly implemented?

The integration test is for the outline design.

The root worker integration granularity is divided:
Integration test between modules
Subsystem integration test
Integration test between subsystems

Integration Test policy:
1. incremental test mode
Top-down
Bottom-up
Sandwich
Improved sandwich: uses a mix of top-down and bottom-up policies to integrate them gradually, without leaving each module alone.
The association between each module is a comprehensive integration test

2. Non-incremental test mode
Great: test all modules separately and then merge them for a test. This is only suitable for small systems, because there is no test between fine-grained modules.

Two considerations should be paid to the Case Design During the white-box test in the integration test.
1. Cover all functions
2. overwrite all interfaces as much as possible,

It is necessary to examine the functional coverage rate and interface coverage rate.

System Test

Use manual or automatic means to test the system to meet user needs

Performance test:
Stress Testing: continuous pressurization Based on Design Performance
Obtain the data that causes the system to crash.
Load Testing: when designing performance, run the system
Check whether the system performance meets the requirements
Regular performance tests: run when the performance is lower than the Design Performance
Program to view the system performance
The preceding multi-thread parallel testing is used.
Using automated tools

Capacity Test:
Maximum database capacity,
The maximum data throughput per second of the system,
Maximum number of threads
Automated testing tools are usually used
Robustness test:
Test the fault tolerance and self-repair capabilities of the system.
Main tests: 1. Try... catch
2. Call modules that may generate exceptions
Affected?
3. External damage: Network disconnection and software dependency disabling

Compatibility:
Dependent software: for example, the web is stored in different browsers.
Operating System: WINXP, Win2k, win2k3, win2k8
Hardware: different sound cards, video cards, CPU

Installation:
1. Install according to user manual (optional)
2. Installation Method (simplified, custom, and typical)
3. manual and automatic
4. Consider unexpected events (the first installation failed or canceled,
Power failure during installation, network disconnection)
5. check whether there are unnecessary folders or files after installation.
6. Whether the uninstallation is complete

Configuration:
1. Hardware: CPU size, memory, sound card, and video card
2. Software: whether the associated software is available or not
3. Network: bandwidth, Internet type
The minimum installation requirement of a software is the result of the configuration test.

Document test:
Three documents and design documents (test completed before the development phase)
User Manual (for System Testing)
Manage documents (generated throughout the software lifecycle
Project management Documentation)
The test has a national standard

Gui test:
The test has a national standard
The options include form, menu, mouse, and data input.

Acceptance Test:
Informal Acceptance Test (internal test) Alpha test
Beta testing (external testing)
Formal acceptance test (User-led ):
Acceptance Test plan and project acceptance guidelines

System Testing Process:
1. Plan
2. Write Use Cases
3. Execution case
4. defect report
System participants:
Mainly Software testers
Other personnel assistance

System Testing mainly includes performance and functions