web测试（Web test）.docVIP

web测试（Web test） Web.Txt I envy in some elderly people envy them hand in hand all the way to the end. - pay the bill when they found themselves so valuable. Seen here in the previous article said, test points to accumulate various commonly used modules, and then to the time needed to be tested on the basis of these test points of test case design, I think this is a good way, decided to summarize. Not according to my practical experience, scattered things I learned at the forum and their imagination, summed up the following points, welcome to supplement. 1. landing Add 2. 3. query 4. delete 1. landing The username and password are in line with requirements (format requirements) The username and password does not meet the requirements (format requirements) The user name password does not meet the requirements, meet the requirements (format requirements) The password does not meet the requirements to meet the requirements, the user name (format requirements) The user name or password is empty The database does not exist in the user name, the password does not exist The existing database username, password error It does not exist in the database user name, password there To input data before the existence of space Input the correct username and password according to whether [enter] can log Add 2. The added data are reasonable, check the database is added with the corresponding data The required data set aside an empty According to boundary value equivalence test case design principles for the design of test cases other entry It does not meet the requirements of the place to have error Whether the table key support The preservation according to whether enter can And if that cannot be saved, but also to examine whether the database has a data 3. delete The delete existing data in a database, and then check whether delete database There is not a second to delete the data in the database, reading books or have error, and not in the database data is deleted The input of a mal