Eight steps to improve the professionalism of test cases _ software Testing

　 Test case writing is not easy, write a professional test case, is the content that all testers consider, in fact the writing of use cases can be done by some ideas, many mature companies in order to enhance the professional use case, there will be their own use case library, including processes, concerns, as well as their own definition of templates. Today as a Test veteran of me after years of experience precipitation summed up a set of test case writing ideas, this idea has a total of eight steps, experience validation almost all functional testing can be based on this architectural approach, will maximize the professional level of use case design first step, UI experience test 1. Style, style, Whether the color coordinates 2. The layout of the interface is neat and coordinated (ensure that all are displayed, try not to use scroll bar 3.) 　　Interface operation, title description is appropriate (describe ambiguous, note whether there are typos). 4. Whether the operation is in line with people's conventional habits (there is no similar function of the control to put together, easy to operate) 5. The prompt interface conforms to the specification (should not display the English cancel, OK, should display Chinese confirmation etc.) 6. Whether each control in the interface is aligned to 7. Whether the date control can be edited 8. The length of the date control is reasonable, in order to modify the time can be all displayed as Quasi 9. Query results list column width is reasonable, label description is reasonable 10. The query results list is too wide and does not have a horizontal scrolling hint 11. For text with longer information, the text box has no automatic vertical scroll bar 12. Data entry control is convenient 13. There is no Support tab key, the order of the key to be organized, not random jump 14. There is no relevant hotkey 15 available. The prompt description of the control is correct 16. Whether the module calls are unified, and whether the same module calls the same interface 17. When you move a page with the scroll bar, the control for the page displays normal 18. The correct format for the date should be xxxx-xx-xx or xxxx-xx-xxxx:xx:xx 19. Does the page have an extra button or label 20. Whether the window title or icon is unified with the menu bar 21. If the window is maximized or minimized, 22 can be switched correctly. For normal functions, users can use 23 without having to read the user's manual. When performing risk operations, are there any prompts for confirmation, deletion, etc. 24. Operation Order is reasonable 25. 　　Correctness check: Check the page for form, button, table, header, footer, hint information, as well as other text spelling, sentence syntax, etc. is correct. 　　26. The system should warn the user before performing the wrong action. 27. Page Resolution check, in eachThe resolution browsing system checks the interface friendliness of the system. 　　28. Rationality check: Do delete, update, add, Cancel, back and other operations, check the information returned to the page is reasonable. 　　29. Check whether localization is passed: English version should not have Chinese information, English translation is accurate, professional. 30. Background Gray Freeze second step, functional integrity Test 1. Test with all default values 2. Traverse test based on all product documentation and help document Description 3. Enter Judgment 4. All interfaces appear to be and no logic, to test 5. Exception handling 6. Sensitive Word 7 Traverse all flowchart paths according to the flowchart of the requirements document 8. Depending on the content of the program, the logical point of traversing if elif else switch is to traverse 9. Interface various control tests the third step, business process testing business process, generally involves multiple modules of data, so in the business process testing, the first 　　First of all to ensure the correctness of the function of a single module, the second to the various modules passed between the data to test, which is often prone to problems, the test must be designed to test different data. If a functional module has the most basic additions and deletions to check the function, you need to carry out the following tests: 1. Single function test (add, modify, query, delete) 2. Increase--> increase--> increase (continuous increase test) 3. Add--> Delete 4. Add--> Delete--&G 　　t; Add (the new additions are consistent with the deletion) 5. Add--> Modify--> Delete 6. Modify--> Modify--> Modify (continuous Modify test) 7. Modify--> Increase (new additions are consistent with previous revisions) 8. Modify--> Delete 　　9. Modify--> Delete--> Add (new additions are consistent with deletion) 10. Delete--> Delete--> Delete (continuous delete test) step fourth, fault tolerance test 1. Enter data that is not allowed by the system as input. 　　2. Stop a related module or subsystem to verify the impact on the current system. 　　3. configuration file deletion or configuration error. 　 　4. Database injection error data. 　　The fifth step, the routine test 1. The system runs continuously (7*24), verifies whether the memory leaks, the system other resources existence leaks 2. If it's an emergency line, you can run for two days a night or a weekend. General pressure is very large, the number of database connections, memory leakage problems will be exposed faster but the deadlock may not be reflected, so to see the importance of the system, such as 12306 stabilityThe best 7*24 hours are the sixth step, performance test 1. Connection speed test the speed at which users connect to a Web application varies according to the way the internet is being used, perhaps by phone dialing or broadband Internet access. When downloading a program, the user can wait a long time, but if only access to a page will not be so. 　　If the web system response time is too long (for example, more than 5 seconds), the user is left without the patience to wait. In addition, some pages have a time-out limit, if the response speed is too slow, the user may not have time to browse the content, you need to land again. 　　Moreover, the connection speed is too slow, also may cause the data to lose, causes the user not to have the real page. 2. Load test Load tests are designed to measure the performance of a web system at a certain load level to ensure that the Web system works properly within the requirements range. The load level can be the number of users who simultaneously access the web system at one time, or the number of online data processing. For example: How many users can the Web application system allow to be online at the same time. If this amount is exceeded, what will happen. 　　Whether a Web application can handle a large number of users ' requests for the same page. 3. The stress test load test should be scheduled to be tested in the actual network environment after the web system is published. 　　Because an in-house employee, especially a project team, is always limited, and the number of requests that a web system can process at the same time goes far beyond that, the result is correct and trustworthy only if you put it on the Internet and accept the load test. Stress testing is a reflection of the actual destruction of a Web application system and the testing system. Stress testing is the test of the system's limitations and failure recovery capabilities, that is, test the Web application system will not crash, under what circumstances will crash. 　　Hackers often provide incorrect data loads until the Web application crashes, and then gain access when the system restarts. The stress test areas include forms, landing and other information transmission page seventh, interactive experience Test 1. The control of the system interface can be traversed through the TAB key, and the order is reasonable 2. The entrance and operation of the main function is easy to understand 3. Whether the interface is reasonably well laid out and the function is easy to find and use 4. Operation Step 5. Operating habits 6. Have sufficient prompt information, and the information text description accurate eighth step, compatibility test compatibility test is not only refers to the interface in different operating systems or browsers compatible, some functional aspects of testing, but also to consider compatibility, including operating system compatibility and application software compatibility, may also include 　　Hardware compatibility such as Ajax, jquery, JavaScript, and so on, should take into account compatibility issues in different browsers. In addition to these tests mentioned above, there are algorithm testing, configuration testing, security testing, etc.And so on, in the work of continuous summary and analysis, to form their own functional testing framework, when you do this job, for yourself for the Test team is a valuable thing, your test ideas will become more comprehensive.
End.
More Popular articles: http://www.51testing.com