[Example] Design by carding

First, the purpose

• Unified test case specification written, write test cases to improve the readability of enforceability;
• Enhance the efficiency of the preparation of test cases

 

Second, the test requires combing

• Test mandatory elements: module name, name of the use case, the pre-condition (optional), steps, expected results, priority
• Test division:
  • Basic principles: the smallest functional modules are divided, the degree of protection covers use cases.
  • Use Case Category: P0 use cases, complete with cases
• p0 test: test basic functions and main functions, separately carded into use cases P0 canvas.
• Complete test case: according to the module can be divided comb.
• Requirements specification writing:
• A function of the normal process, write a test case;
• A plurality of abnormal flow function, the preparation of a plurality of separate test cases;
• Different inlet same function can be combined to prepare a test;
• The same function in different data required for the preparation of separate multiple test cases;
• Procedure to correspond with the expected results.

 

 

Third, the test case review

• Review steps: internal assessment Center -> Project Review Group
• Sponsor: Use Case designer
• Participants: test leader, project managers, developers and product managers
• Requirements: review process, focusing on recommendations put forward by participation, improve their test case, remove redundancy, modification and scene does not match, the end of the review, test designers need to be filled out in the minutes of the meeting on the cases reviewed km;
• Minutes:

　　     The minutes must contain: the name of the meeting, the meeting place, meeting time, the meeting participants (selected template New), meeting carding communication problem, the conference did not confirm or need follow-up question;

            Follow-up mode: @ meeting in the corresponding process, testers responsible for follow-up;

 

Fourth, the perfect test case

• Test cases must be updated at the end of the iteration, design test cases found ill-considered or omissions, the need to continue to supplement and perfect the testing process;
• After the update module, depending on the version needs to be perfect checklist documents, uploaded to the cloud disk module in accordance with the classification, and then need to be synchronized to the central group;
• Synchronization issues:

         Modified information, and the difference between the modified before modification;

         And the modified embodiment with the address stored in embodiment (screenshot or link address) with synchronization to the group project group.

 

Fifth, test case design

      Including functional testing, interface testing, compatibility testing, usability testing, abnormal testing, performance testing, and stress testing, when designing with consideration to try to deal with cases where the normal input, the boundary, the outliers systems. (Note: Such as a test basis, not quite sure of your own Baidu)

 

 

Six test case design principles (here more content online, find one)

• Test accuracy: the input data to verify that the user actually meet system requirements; test case should first test point to ensure that covers at least the functional requirements, and normal.

   For example: Log Function: Enter the correct account number and password 

• Fault tolerance (robustness) Test: The system can receive the correct data input and produces the correct (expected) output, input illegal data (the illegal type, does not meet the requirements of the data, overflow data, etc.), can give prompt and appropriate treatment. Think of myself as one pair of products the user did not understand the operation, during any operation.

  For example: login function, enter the correct account number and password, the login is successful. Enter an incorrect account number or password prompt information corresponding to the (prompt enter the correct phone number or password error);

• Boundary value analysis: determine a boundary where (exactly equal to, and slightly greater than and slightly less than the equivalence classes just above the boundary value), the main system for legitimate data input / illegal data during the test, mainly in the vicinity of the boundary value selected.

  For example: When testing the login function, login account to consider greater than 8/11 digit phone number; less than 8/11 bit cell phone number, phone number and other scenario is equal to 8/11 bit;

• Equivalence partition: all possible input data (valid and invalid) divided into several equivalence classes.

 For example: login account: number of Hong Kong, Macao numbers, numbers continent, empty account, unregistered cell phone numbers;

• Error guessing: mainly based on testing experience and intuition, referring to the previous system error occurs place.

• Understood (operation) of: understanding and ease of use of the system (friendly interface).

 For example: intro, tips page copy and so on;

• Regression testing: According to test all the test points test is completed, the test developers found the problem has been resolved, the next round of testing.

• Interface Test: Test each module where coordination and communication between each other, input and output data for consistency and correctness.

 For example: non-transmission parameters of the interface will necessarily pass, the parameter type, the parameter length;

• Compatibility Test: Compatibility test content includes not only the operating system installed software, the need for critical processes and functions point to be checked. What operating system compatibility and required tests, first of all depends on the user's commitment to software requirements, followed by the need for some common operating systems are compatible checks

 For example: version upgrade compatible between versions of the phone system compatible, compatible, compatible with the type of system