1. The lazy even to the end of late, this requires a good reflection and practical action
2. A few days ago in the busy new customers increasing demand module, beginning need to sort out a new test point, according to the previous test project issues and customer feedback, problems mainly concentrated on the interface compatibility issues, regardless of the browser or mobile client, have more or less the situation is not in place of the adapter interface appears.
Treatment methods: Web side: the problem is to collect feedback first appeared on which browser and browser version know.
You need to install more than one browser, and also need to verify different versions
Phone end: In addition to testing in the simulator and the real machine, but also need to be tested on more models [case conditions, the company can make use of internal strength], in addition to models, but also consider the version, in particular, the old version of the old model, the kind of small screen.
3. Test Interface
For newly added modules for test interface, the interface before the continuation of the testing process, the newly added back-end interface, we must understand the mutual dependence between the interface and the interface definitions in the field [for example: create a query and then get data like of], after a clear understanding, to use for field definition and interface scenarios to test design method, it is best to write a special interface test record documentation. After a good test design methods, began mass participation for a variety of combinations to test, the best interface screenshots, test records stored in the document, to facilitate follow-up inspection
In the case of interface testing does not make sense, the need for timely feedback in order to be better, to provide information and mass participation along with error message to the developers, released after the repair, it is best to understand the cause of the problem [Haha, a lot of companies phenomenon is the development will not say to you, or does not indicate the cause of the error happened after you raised in the reply Bug BUG management tools]
After the interface test is completed, the test records promptly organize, on a document management management tools to facilitate follow-up inspection.
Written in the last:
Sometimes developers say the cause of the problem of the interface for you, in fact, when you do not know why, since when engaged in software testing, you should allow yourself to learn a programming language,
In testing, it is best to subscribe to the code base permissions, you can view the changes to the code files after each commit to develop the code, and sometimes modify a logical need to involve several files.