Summarized as follows:
1. closed-loop business
In writing test cases, we must find out the needs, from start to finish can draw a flow chart, at the time of writing, each process must be involved, they also should be written in accordance with written procedures, to prevent the omission.
2. Functional dig deep
When writing with the embodiment, each test point to a small, we will move out of the method of designing (equivalence classes, boundary value, cause and effect diagram, orthogonal decomposition, estimation errors, etc.) according to, for example, two input blocks have sign-on function What test points should fully and to analyze other function points and so on
3. Big Data
What is big data? That is, when making the test data, in general, made on several data, the data display is normal to see pass by, this will cause prone to bug when data is too large. A few examples:
a. The user name is displayed
We register a nickname for the "abc" of the user, the user information is displayed in the upper right corner of the page under normal circumstances are normal. If we register a nickname as "12,345,678 ninety" user, in the upper right corner of the page to see how the display style is causing confusion?
b. flip function (app loading tabs function)
A page, the default data per page 10, then we have to build at least 30 data to measure whether the page data is normal, non-current to measure whether the search page data is normal, to measure per page (10, 20, 50 bar) down is normal
3. CRUD function associated i.e.
Development colleagues in the development of a business function, general logic is CRUD, we measured the time should follow this logic to the test, all the data all, must be twice CRUD, why twice?
a. often occur after data is deleted, re-create the same data, the data will prompt already exists, there is no real explanation before data is deleted
b. To add a data investigation, after which the data must be deleted check, test whether it is deleted
c. Increase piece of data, then an increase of the same data, re-test to see whether
d. an increase in the data, and then modify the data before and after the modification of the modified search
There is a very important association test , in which we add, search, delete after the operation, we must see whether the local data associated with the change. For example, modify user information, provided that information is displayed where the user must test to see whether you also want to modify.
These are the small sum up, we have nothing to add comments, we grow together.