Start a lot of sorting out the Web tests for dry sharing
Web Test Guide--"test html--static Web"
First, the encoding in HTML
- Missing closed markers are a common bug in Web testing, and there is also a common mistake of missing closed greater than the symbol ">".
- Not all open markers have a corresponding closing tag character. For example, <br>, which simply tells the browser to insert a breakpoint in the text.
- Comment Marker "<!--" to "--".
- Non-standard code can cause problems and is the source of many bugs.
- comply with external coding standards.
- Maintain internal coding standards.
- HTML is not case-sensitive.
Second, testing the design on the web
- Cleanliness is the most important thing.
- Test The ease of design (using prototypes to test ease of use, writing effective links, testing Web site search capabilities, developing effective error messages)
- Design user interaction
- Test performance (control using extra tokens)
Three, a typical form
- Form markers: Contains the table's method-(what the form does) and the form behavior (form action-points to the implemented code). This method is typically post, but it can also be a get. The form is usually started with code similar to <form method= "POST" action= "Scrīpt.js" >. A form line refers to a link to a script that can process the data entered. The link can be a relative or absolute path to the script file on the server.
- Form element: An arbitrary number of elements after this form marker.
- The method used to submit: The final point of the form is the ability to submit information. End the form with the </FORM> closed marker.
- The code for the uploaded form is similar to <form method= "POST" action= "upload.cgi" >file path:<input type= "File" name= "filepath" >
You can use the Firefox plugin HTML Validator to check if the syntax is canonical
Check for closed labels
