Test case design for CNZBA

[FenWangNZ]

The new invoice creation function requirements are as follows:

• There is a cancel button after opening
• The editable field of customer information cannot exceed 50 characters (special characters are allowed), not empty
• The email contains email verification. If you make a mistake, there will be an exception prompt immediately below the text box
• A field number that can be empty
• The date can be selected from today and the time after today
• The item field of invoice detail is non-empty, 50 characters
• The amount is adjusted manually or through the spinner, and finally rounded to the nearest 2 decimal places
• Click Save after filling in, the new creation is successful, and the user stays on the current invoice detail page
• The invoice with an amount of 0 is saved as draft, the invoice detail page has a delete button, and the status is draft
• The invoice with an amount greater than 0 is saved as draft, the invoice detail page has a delete button, finalise&send invoice button, and the status is draft

Test point design (including function, UI, database test)

Verification of the initialization page (layout and information)

Valid test cases (the values of valid characters can be scattered in different categories)

• Enter valid characters in each required field, the number field is empty, the invoice amount is 0, save. Created successfully
• Enter valid characters in each required field, the number field is not empty, and the invoice amount is 0, save. Created successfully
• Enter valid characters in each required field, the number field is empty, and the invoice amount is not 0, save it. Created successfully
• Enter valid characters in each required field, the number field is not empty, and the invoice amount is not 0, save. Created successfully

Invalid verification: whether there is a warning message, whether the warning message is indicative (put it in the exception use case)

• Enter empty values in editable fields
• Input 51 arbitrary characters in the editable field
• Email input special characters (such as *&%#!~_-+=()^$`';:"/?><.,[]|{})
• The invoice item is empty
• Enter 51 arbitrary characters for invoice item
• Enter the amount with more than 2 decimal places 5.344434
• Amount input 8.999
• Amount enter 8.010
• Amount input 8.0
• Amount input 8
• The amount is negative
• The amount is in characters
• The amount is adjusted by spinner to see if it changes
• Amount input 1000000000000

Other:

• Uniqueness: Whether the invoice field is unique and conforms to the invoice number generating rules --- put it in the forward test case
• Shortcut keys: tab key（ as a separate use cases）
• Can copy and paste be used, and use operations such as copy and paste to force input data that is not allowed in the text box. For example, the amount can only be entered in numbers, but after copy and paste, see if you can enter text-a separate use case
• Database verification: Use automated scripts to keep adding new entries, depending on the number of entries that the database can support-individual use cases
• Performance: Test the response time of saving invoices--not a functional test case
• UI (Universal Checkpoint)
• Open the new page whether the cancel button exists and whether the initial value is correct
• Check whether the invoice item list can be arranged neatly when multiple new items are added
• Whether the corresponding button appears after adding
• Whether the multi-line characters are displayed properly, whether there are scroll bars, etc.

Summary:

• Just prepare whatever the test point according to the requirement
• Merge if they are the same

[FenWangNZ]

modify the test design point after discussion with Stephen