Original Transfer: https: //blog.csdn.net/jinganglong123/article/details/51122713
After receiving the test head of the test tasks, testing should be done according to the following process specifications.
2.1 Test requirements analysis
product development leader after the completion of the preparation of a product's function interface documentation, test interfaces at issue in the corresponding person in charge after verification. Test leader to get the interface documentation need to do work in the following two aspects. On the one hand, testers want to understand the meaning and usage of the interface functions and document the various fields involved in the interface of each interface. On the other hand, testers should be fully communicate with developers clearly understand and value each interface to the protocol specification and scope of each field.
After each test personnel to complete the preparation of test cases, required to submit to the test case review case will take the test lead audit or review the organization's leader, before the start of the follow-up work after the case of passing the examination.
Having regard to the urgency of the agility test time, started to intervene when the needs analysis from the development will be held kickoff (T-7).
2.2 test plan
interface test person in charge of arrangements with the test leader or project manager to communicate test plan. When a single interface to interface documentation involved too, by the head of the test according to relevance and the complexity of partitioning interface interface functions distributed to different testers to test and develop the test time and daily testing effort.
2.3 Design test cases
after the division of tasks interface test, the person in charge for the test interface to be based interface documentation, test cases written interfaces, and clear which cases can be automated, in which cases the need for manual testing. Provide guidance for the subsequent preparation of automated test scripts to ensure comprehensive testing. Case design interfaces test points need to refer to the following section of this guide raised. Case need to do to cover all the test points, and for certain special interface, taking into account the special nature of the interface, the preparation of test cases targeted.
After the completion of the preparation of test cases, to conduct case assessment, the assessment should perform through testing.
2.4 Preparation of the test environment
Required interface test automation tool JMeter installation, java environment configuration and other personnel responsible for their own to complete the test. Interface testing required for the background environment, the situation is the absence of a separate test environment, need to be tested in the development environment, environmentally responsible by the corresponding developer responsible for the maintenance and development needs with the person in charge of testing personnel, to ensure a stable and beta versions of the environment correct. If a separate test environment, test environment, maintenance personnel need to get the latest beta version deployed in a test environment from that development manager, and safeguard the initial configuration parameters and initial test data.
2.5 implementation of the test
after the preparatory work complete, according to the plan can be implemented to test. Test implementation of the recommendations on priority manual testing, manual testing all the cases the interface again, so that one can strengthen testers understand all the details of the interface, on the other hand there is the interface you can quickly find the bug, timely feedback to the developers to modify . To be major bug development has been resolved, the interface to carry out the case of each field configuration has been steady job automation script recording, writing and so on, the case can be automated testing to the preparation of test scripts, and follow the script written specification, the organizational structure of a good script, convenient post-script maintenance and management. Scripting scripting specifications refer to the following specification section.
According to the test during the testing phase, the test case of a defect and deepen understanding of the interface, test cases might be supplemented or modified, testers need timely maintenance of good test cases, to ensure that each case is accurate, easy late regression testing.
After the test is completed each interface, submit test reports. And test related documents to collate summary.
2.6 Test results of the assessment
of the stage for the final phase of testing, test team leader responsible for organizing the test results of the review meeting. Meeting in order to review the results of each test were personnel (including case, test scripts, bug list, test reports and other output test substance). Identify problems and deficiencies promptly corrected, standardized testing. The test results of the assessment by the summary note was saved, form part of the company's assets test.
2.7 continue to optimize the testing process
After the interface automated testing for a period of time, to be regularly tested to summarize. To improve the problems identified, the test guidelines to improve on the process of ongoing optimization tests.
Interface specification test-related document management
3.1 Document Scope test
Interface test automation main types of documents need to be managed as follows:
Interface documentation, test documentation, test report (result) documentation, test scripts (jmx type), minutes of meetings, reviewing documents and other test-related documents.
3.2 Test documentation instructions for creating
documentation requirements class (eg: Interface documentation) at the beginning of the test provided by the developer to the test, testers write use cases, the document does not regulate areas that need immediate feedback to the developers based interface documentation, urging modified to provide a standardized interface documentation.
After the document is a test case tester got Interface documentation, began to understand better the needs of the preparation of the document, the latter will continue to optimize test cases documents subject to assessments. Upon completion of the preparation of test documentation, test preparation to start the script, the script prepared on the basis of use cases from the test case documentation.
Test scripts are executed in the form of output test test test personnel, the scripting required to meet regulatory requirements of the following documents to write a script, so to facilitate post script maintenance and management.
Test Report document is a tester after completion of the test, a summary report of the results of the test phase, prepared in accordance with the requirements specification template provided by the company and submitted to the test head of the audit, issued the corresponding product or project and correct the development, business, leadership and other related personnel.
Meeting minutes, documents and other documents are reviewed throughout the test generated based on needs of the project, the documents to be placed under the requirements document for test work instructions and specifications testers.
3.3 test document filing requirements
after the end of the test task, testers need to organize a variety of related test documents, uploaded to the appropriate directory under SVN server. The formation of test assets throughout the test group. It requires each tester attention to the links after the end of the test must archive all types of test documents.
It is strongly recommended test groups in each area has its own directory management SVN, testers testing is complete project or product, because the product or project has its own directory SVN, testing, development manager will be required as test cases, test reports, test documents uploaded to the SVN corresponding item. But after the test, testers need to complete the final test related documentation (Interface documentation, test documentation, test report (result) documentation, test scripts (jmx type), meeting minutes, review documents, etc.) by type archive SVN to manage their own directory under the test group, the test document management is controlled by the test group, the test group to form their own assets.
The following examples explain the test group of test documentation Beijing archiving requirements, the rest of the test group reference may be made, depending on the situation of their own project test document prepared for the archives.
Interface Test Points
4.1 Interface Usability
whether the interface usability testing main interface is available, the existence of the interface, protocol type interface, test cases should include:
〖〗 R1 interfaces document based on a given address and protocol interfaces to access methods to the interface.
〗 〖R2 uses the wrong method can not be accessed in accordance with the protocol interface address.
R3 〖〗 use the correct method can not be accessed in accordance with the protocol interface address wrong.
4.2 The number of input and output parameters and naming
input and output parameters and the number of input and output parameters named major test of the interface contains the number and name of each parameter is correct, the test case should include:
〖〗 R1 interface documentation check input parameters based on The number and name, and whether the document consistent.
〗 〖R2 interfaces based on the number of documents to check whether output parameters as well as names and documents consistent (be careful to check the output parameters of normal and abnormal parameters).
R3〗 〖enter the wrong parameter name, the interface error, and an error message is returned.
4.3 input parameters to lose items
to lose the main input parameter test item interface with the optional input parameter requirements losing, the test case should include:
〖〗 R1 is not sequentially input interface document in accordance with all entries for losing check whether the interface gives an error message is returned.
If R2〗 〖interface document according to sequentially check all entries selected outputs of input parameters may not have the correct data interface to return, without error message.
4.4 input parameters legality of
the legitimacy of the legitimacy of the main input parameters for input parameters to check specifications, test cases should include:
〖〗 R1 based interface documentation, with clear requirements (eg: only by numbers select values selectable in the following, only the alphabet, the length of the maximum number of the format of the time format) the input parameters, check meets these requirements.
R2〗 〖interface document basis, not explicitly required input parameters, the test sequence length long, containing special characters, like the case of full-width half-width. Check whether the interface error, giving an error message is returned.
4.5 output parameters of the correctness of the contents of
the correctness of the contents of the output parameters of the main contents of the output parameters of the background and whether real data consistency checking, test case should include:
〖〗 R1 consider a variety of combinations of input parameters, in order to test these contents of the fields where the returned interface composition data is correct, check to the specific contents of each field. Generally more be checked by the data with back-end database.
R2〗 〖consider various combinations of the input parameters, the test data sequentially in the combinations of these interfaces in the returned item relates to the input parameter, and the initial values are the same inputs.
4.6 interface functional verification
interface function to verify that the main function of the specific interface operation of the normal operation of inspection, test case should include:
〖〗 R1 enter the correct parameters, check the interface corresponding to achieve the correct operation of back-office functions. For example: a command interface for boot is transmitted, the interface corresponding to the background system starts properly and return the correct parameters.
R2〗 〖parameter input error, check whether the interface corresponding to the back-office functions to be achieved is not running.
4.7 interface documentation normative
interface documentation normative mainly on the development of interface documentation provided is accurate specification check, test case should include:
〖〗 R1 interfaces document has accurately named for input and output parameters, vague absence.
〗 〖R2 interface documentation for each parameter have a clear description of the type, whether optional or losing, whether there is a default value.
〗 〖R3 interface documentation for each input parameter entry must clearly good basic conditions, such as how much the longest and only digits or letters, can not contain special characters.
〗 〖R4 for an interface if there are multiple types of output parameters or a combination of the number of parameters and named differently, this case, to set out clearly in the interface document, and appeared clear that this type of output parameters of the conditions.