A, web testing phase
Project -> Requirements Review -> case design and writing -> Use Cases Review -> test execution -> Test Report
Second, the demand stage
1. After the test project needs to get the document
Demand exposition
FIG prototype (and FIG UI)
Document Interface
Data Dictionary (the number of tables and caching mechanisms)
2. Requirements Review
Participation question mark before the meeting point, resolution of the question, and organize assessment results, send full
3. Design and preparation of cases
Written in a way to determine the test case
Example function type with
The method of preparation of test cases
4. Test Case Review
Participants: development, testing, requirements, project managers, led by testers.
This part of the development carried out before completion, according to perfect use case when mentioning the assessment point, perfect after mail to participants. In the project group, more often than developing the test will be more understanding of the needs, determine our understanding of the needs of the professional is certainly closer to the customer, the output product of our understanding of the needs of test cases, in a sense use cases It is a refinement of demand. And the development of the demand will be more inclined to understand the functions implemented, the program is the product. So to develop, test case needs to understand there is often inconsistent, development will not be so careful to understand the needs, unified development, testing, requirements demand a tripartite understanding.
5. Test Execution
(1) smoke testing: test personnel began to run critical test cases, test cases can be run according to the module, if more problems, to play back to back development.
(2) functional tests: Full run test cases, defect management tool to submit bug
Test form:. A field of the form data, and the integrity of the form input box length restrictions
b. Some common sense logic verification, such as date of birth and occupation, length of service is appropriate, matching the location of the provinces and other cities Jane, if set to the default value, but also a test.
Navigation Test: navigation tests, that is, between different pages jump, or buttons, dialog boxes, lists, and windows, etc., by considering these factors to determine whether an application is easy to navigate: whether intuitive? Are the main module of the system can be accessed via the home page or arrive? Whether the site needs additional help stop internal map or search engines? Another focus is the page structure, navigation, menus, etc. are the same web-style navigation system, to ensure that users can rely on intuition or simple judgment can find what they want. (Reference blog http://www.cnblogs.com/imyalost/p/5622867.html)
UI test: can be understood as UI tests, including pictures, animations, borders, colors, fonts, backgrounds, buttons, etc.
a picture should have a clear purpose, representatives; Image size as small as possible, generally use the JPG or GIF
Use b. The whole page style and whether the system has been
c. background color, font, with reasonable
d. Test content display
Overall interface test: user experience, user browser is sick, the overall style is consistent
Link Test: mainly distribution of competences, whether different people permission to share links to the normal filter
(Three) regression testing: According to the records during test execution bug and failed to carry out use cases, whether the verification has been revised update is good, when necessary, be assessed according to the number of bug amounts of whether the need to record the bug again running about process systems
(4) Compatibility testing:
. A platform compatibility: In a lot of operating systems such as Windows, Unix, Linux, macintosh etc; which users use the system depends on the user, so the system compatibility testing is very necessary.
. B browser compatible: the browser is the core component web client, different browsers, for Java, JavaScript, css or HTML specifications have different support;
(5) Safety tests:
6. Test report and Operation Manual
Test reports for each company using the template may vary, but the focus is reflected in the test results and test distribution module bug appeared, but also concerned about the state of bug resolved, as long as the template according to statistical needs.
The main operating manual is written for people looking to use the system, requiring a specific detailed description of what action is what role any module can be clear, step by step, accompanied by screenshots and text.
Functional testing ideas