First column conclusion:
Encountered over key projects, not just static pages to compare the measured features, compatibility, data, etc.,
Project managers first need to inform the test, how important this project, it realized a test to distinguish between ordinary project, which is the responsibility of the project manager.
Secondly, send test before, we need to be confirmed to be among the leadership of pages reviewed and finalized, and propaganda materials may be reviewed battalion sector.
Reach this point, to mention test.
In this case, the test must be aware of the importance of the project. Should be added to the "style, to increase the range of compatibility, version compatibility, each click", unavoidably test
If it is to use multiple clients, make sure that the problem will be fully resolved locally, can not go to the customer's environment and then modify, or will cause high maintenance costs.
Also realize, bug can not be arbitrarily closed. Testing should strictly require a higher level than the average project, not tested by the firm can not deliver.
-----------------------------------------------------------------------------------------------------------------------------
The circumstances surrounding the start:
Project, there are points of common projects and key projects, so they have different testing standards.
But encountered over key projects, or when tested in accordance with the previous standard, the risk factor it straight up!
Our general project, comparison test only static pages to see if the implementation of the site is consistent with the static pages.
Then according to the test function, data compatibility, js error, which is enough.
I personally, do not ask for the style, and some colleagues were measured very carefully.
I generally think the overall style is no problem on the OK, or indeed watching a dislike to mention bug.
But it super-key projects, can not be so casual style, even the return of the icon at the top position are required, must look good, standard, can be used not just on the line.
Style is just a test on the one hand to note, the frightening thing is,
Super unreasonable design of key projects, the demand did not review was afraid.
During the test, put a bunch of bug, reply to the implementation of that product bug is not modified, so the design without modification, to be here and then modify the customer's environment, test data without modification.
The recovery of their nature, are the requirements and design aspects of a problem. Since when have you should avoid products page bug, design projects;
Since we know that many customers will use, it should solve all the problems locally;
Since we know that the focus of the project is over, you should do the needs assessment and pages;
Since we know that more is to show clients, you should test the configuration information related to the topic, and after a data review.
If these are not done, the measured mention mention is white, still have to rework restructuring.
This is the oversight on the project process.