Web (performance test/interface test/compatibility test/security test)
1. Web performance test: (stress test, load test, connection speed test)
1. Stress test:
concurrent test (for example, 500 people log in to the mailbox at the same time)
2. Load test:
Design the test application according to the scenario.
For example:
100 users log in to mailboxes,
200 users view news,
300 users view technology
3. Connection speed test:
①The speed at which users connect to the Web application system varies according to the way they access the Internet. They may be dialing up by phone or surfing the Internet through broadband. ②If the
response time of the Web system is too long (for example, more than 5 seconds), the user ③Some pages have a timeout
limit. If the response speed is too slow, the user may have to log in again before browsing the content.
④The connection speed is too slow, which may also cause data loss, which makes users lose less than real page
summary:
| Test content | Performance Testing |
| connection speed test | Login link time, page refresh time, etc. |
| load test | Under the condition of "full load" of the system, test the bearing capacity of the system |
| pressure test | Get the limit of correct operation of the system (momentary peak) |
2. Web interface test: (navigation test, graphics test, content test, overall interface test)
1. Navigation test:
①Easy and quick access to the information users need
②You can clearly know the web application where the page is located on any page Position in the system
③The logical structure of the page is clear and well-organized
④Easy to return to the previous state or the main page
2. Graphics test:
①Make sure that the graphics have a clear purpose
②The graphics cannot be displayed
③The download speed of the graphics is slow
④The pictures with important information are missing
⑤The font style of all pages is consistent ⑥The
background color should match the font color and foreground color
Size and Mass Affect Performance
3. Content testing:
Check the correctness, accuracy and relevance of the information provided by the web application system
4. Overall interface test:
consistent design style
summary:
| Test content | interface test |
| navigation test | is it easy to navigate |
| Is the navigation intuitive | |
| Whether the main part of the web system can be accessed through the home page | |
| Does the web system require site maps, search engines, or other navigational aids | |
| graphics test | Make sure the graphics have a clear purpose and that images or animations are not cluttered together to avoid wasting transfer time |
| Verify that all page font styles are consistent | |
| The background color should match the font color and foreground color | |
| The size and quality of the picture is also a very important factor, generally using JPG or GIF compression | |
| content testing | Content testing is used to verify the correctness, accuracy and relevance of the information provided by the web application system |
| overall interface test | Do users feel comfortable when browsing the web application system, and do they intuitively know where the information they are looking for is? |
| Is the design style of the entire web application system consistent? |
3. Web compatibility test: (platform (operating system) test, browser test, resolution test)
summary:
| Test content | Client Compatibility Testing |
| platform test | Before the release of the Web system, it is necessary to test the compatibility of the Web system under various operating systems |
| browser test | One way to test browser compatibility is to create a compatibility matrix. In this matrix, test the adaptability of browsers from different vendors and versions to certain components and settings |
| resolution test | Whether the interface controls can be displayed normally under different resolutions |
4. Web security test:
①Register first, then log in
②Login password control
③After the user logs in within a certain period of time (for example, 15 minutes), if the user does not click on any page, do you need to log in again to use normally?
④Logs
⑤Can be placed on the server side and edit script
summary:
| Test content | security test |
| navigation test | User login |
| Does the web application system have a timeout limit | |
| In order to ensure the security of the web application system, log files are crucial | |
| When using secure sockets, also test that the encryption is correct and check the integrity of the information | |
| Scripts on the server side often constitute security vulnerabilities. To test the problem of placing and editing scripts on the server side without authorization |
