<Switch> ERP test case template

1 page
(1) Whether the page list is complete (whether all the required pages have been listed)
(2) Whether the page is displayed (whether the page exists at different resolutions and whether the page is displayed in different browser versions)
(3) Whether the page is correctly displayed and beautiful (whether the screen is refreshed correctly when the browser window is adjusted)
(4) whether the special page effects are displayed
(5) Whether the display of special page effects is correct

2. Page Element
(1) List of page elements (whether to list all the required elements, such as buttons, single quotes, check boxes, list boxes, hyperconnections, and input boxes)
(2) Whether the element is displayed (whether the element exists)
(3) Whether the page elements are correctly displayed
(4) shape and placement of page elements (such as buttons, list boxes, check boxes, input boxes, and hyperconnections)
(5) Whether the basic functions of page elements are implemented (such as buttons and hyperconnections)
(6) fault tolerance list of page elements (such as input box, time list, or calendar)
(7) Whether error tolerance of page elements exists
(8) error tolerance of page elements

3. Functions
(1) Whether data Initialization is performed
(2) Whether data Initialization is correct
(3) whether the data processing function is executed
(4) whether the data processing function is correct
(5) Whether to save the data
(6) Whether the data is correctly saved
(7) Whether it affects other functions
(8) If other functions are affected, will the system respond correctly?
(9) other errors
(10) all functions of the function module can be listed, sorted, and combined to test all functions of the module.
For example, if a function module has the most basic addition, deletion, modification, and query functions, perform the following tests:
Test a single function (ADD, modify, query, and delete)
Add --> Add (continuously add tests)
Add --> Delete
Add --> Delete --> Add (the newly added content is consistent with the deleted content)
Add --> modify --> Delete
Modify --> modify (continuous modification test)
Modify --> Add (the newly added content is consistent with the content before modification)
Modify --> Delete
Modify --> Delete --> Add (the newly added content is consistent with the deleted content)
Delete --> Delete (delete test continuously)

(This includes the implementation of background functions)
(11) The query function can be divided into two situations to verify the operation results.

(12) whether the query is correct.

(13) whether the display function is sorted.

1. The results are automatically displayed when the page is opened,
2. If you need to perform a manual query, the query is performed after other functions are completed.
4. Prompt information
(1) success or failure prompt
(2) operation result prompt
(3) Confirmation prompt
(4) dangerous operations and important operation tips
(5) return to the page displayed after the page prompt
5 Fault Tolerance
Note the following situations:
(1) Empty or non-empty
(2) uniqueness
(3) font length and format
(4) number, remarks, amount, date

(5) date and time (including incorrect format or correct format)
(6) special characters (for databases), single and double quotation marks (&)
6. Permission Section
Function permission: specifies the functions that a user can use and cannot use.
Data permission: Specifies the data that the user can process and cannot process. Yes
To merge to function test
Operation permission: In terms of logical relationships, the Operation Sequence and data processing status. Can combine
Test the function.
Permission change: can be merged to function test

(1) Whether the function permission exists
(2) Whether the function permission is correct
(3) whether the data permission exists
(4) whether the data permission is correct
(5) Whether the operation permission exists
(6) Whether the operation permission is correct
(7) list of functions that cause permission changes
(8) Changes in function permissions or data permissions, or both
(9) is the permission change correct?

7. keyboard operations
(1) Use of the tab key
(2) Use of the up and down arrow keys
(3) Use of the Enter key
(4) use the shortcut keys set by the system (if any)

8 other precautions during testing
(6) Integrity: whether it is a whole with no functional defects
(7) ease of use: easy to use
(8) Consistency: similar problems are handled in a similar way.
(9) prompt information: whether the prompt information is complete, correct, and detailed
(10) help information: whether to provide help information, the form of help information (page text, prompt information, and help files), and whether the help information is correct and detailed
(11) compatibility: including OS compatibility and application software compatibility, and hardware compatibility
(12) Scalability: whether there is room for upgrade and whether the interface is retained
(13) Stability: hardware and software configurations required for running, resource occupation, fault tolerance in case of problems, and data protection
(14) Running Speed: Speed and bandwidth usage

ERP system test case (Second Revision)
The second modification includes the following content:
1. function test: whether the required functions are met

(2) Functional Testing

Functional testing is the main content of acceptance testing. ERP function testing should include the following items: Query, add, delete, modify, and save operations of a single module; Data Input and Output; data processing operations, such as import and carry-over; precision of basic data definition; Accuracy of calculation, accuracy of online orders; data sharing capability; Identity Authentication and permission management; interface parameters and system control parameters; document circulation; whether a report can be printed and output.

First, the input fields of the test project should be comprehensive. A valid data input or illegal data input is required. For example, if the definition of basic data is to be tested as a number, you must enter both numbers for testing and non-numbers such as letters and spaces for testing. Numbers include integers, negative numbers, and decimals. Therefore, you must enter these different numbers to verify the accuracy of the numbers.

Second, divide equivalence classes to improve test efficiency. On the basis of considering the comprehensiveness of the test domain, it is necessary to divide the equivalence classes and select a few representative cases for testing to improve the test efficiency.

Third, use the boundary value for testing in a timely manner. For example, the number of pre-arranged orders is usually greater than 0, so the test data can be 0,-10000000, (a very large positive number ).

Fourth, submit the same transaction repeatedly.

Fifth, do not perform function operations in the regular order.
Sixth, perform normal operations and observe the exceptions of the output results. For example, the effect of deleting a record on Sorting; whether the status of the document changes after approval.

2. String Length check: Enter the content that exceeds the string length stated in the requirement to check whether the system checks the string length and whether an error occurs.
3. character type check: enter other types of content where the specified type of content is to be entered (for example, enter other types of characters where the integer type is to be entered) to check whether the system checks the character type, whether an error will be reported.
4. Check punctuation marks: the input content includes various punctuation marks, especially spaces, quotation marks, and enter keys. Check whether the system processes the punctuation correctly.
5. Chinese Character Processing: enter Chinese characters in a system that can enter Chinese characters to check whether garbled characters or errors may occur.
6. duplicate information, and whether the system correctly processes the entered content by inputting spaces before and after it.
2. Interface Test: the UI is correct, consistent, friendly, and easy to use.

(User Interface testing refers to the software from the end user's point of view. Software is hard to understand and is not easy to use because of Software defects. You can check the user interface from the following aspects:
1. Usability check: Make sure the software is easy to understand and easy to use.
2. consistency check:
A. Check whether the style of the system page is consistent, such as the size, color, and font of the text.
B. Whether the expression of the prompt information is consistent.
C. Check whether the order of buttons is consistent ..
D. Whether the field name, position, length, and type are consistent with the design document requirements.
3. friendliness check:
A. Prompt whether the information is friendly.
B. The system should give a warning and prompt information before the user executes the wrong operation.
C. Check the page resolution and check the friendliness of the system interface in various resolution browsing systems.
4. Page maximization check: whether the page is processed during the test of maximization/Minimization/restoration .)

The interface test includes the following aspects:

First, check whether the background and foreground colors are consistent and whether the color contrast is used properly.

Second, whether the visual styles of the icons, buttons, and dialog boxes of the software are consistent, and the screen resolution required for the aesthetic effect.

Third, whether the layout of window elements is reasonable and consistent.

Fourth, whether the information descriptions of various field titles are accurate.

Fifth, check whether operations such as shortcut keys, buttons, and mouse are consistent in the software.

Sixth, whether the display ratio and format of windows and reports can meet users' expectations.

7. Whether error messages caused by misoperations are friendly.

Eighth, whether the activity window and selected records are highlighted.

Ninth, whether there is help information and whether the menu navigation can be normally executed.

10. Check whether some special fields and special controls can be run.
3. Performance Testing

Performance testing mainly tests the software running speed and resource consumption. By adjusting the software and hardware configuration, network extension structure, workstation points, data volume, and service request count that ERP depends on, we can test the portability, operation rate, stability, and reliability of the software. Generally, automated testing tools such as winrunner and LR are used to assist in testing, and extreme testing is used to analyze and evaluate the software performance.

4. Other tests

First, load stress testing. It mainly includes concurrent performance testing, fatigue strength testing, big data testing, and speed testing. Generally, automated technologies are used for testing on clients, servers, and networks. In case design, representative and key business operations should be selected as the testing object based on the actual business.

Second, resume the test. By simulating hardware faults or intentionally causing software errors, the system detects the degree of damage to data and the degree of recoverable data.

Third, security testing. Detects the robustness of security protection policies, such as system encryption mechanisms and anti-virus functions, by means of illegal login, vulnerability scanning, and simulated attacks.

Fourth, compatibility testing. The cross-platform and portable features of the software are tested through hardware compatibility testing, software compatibility testing, and data compatibility testing.

 

ERP system test cases (Third Revision)

The following content is added:

1. Does not meet user operation habits. (For example, the shortcut key distribution is unreasonable, the shortcut key is not practical, there are too many shortcuts, or there is no shortcut key at all)

2. The interface information is mixed. Irrelevant interfaces are often displayed, and incorrect words are also displayed.

3. Reasonable UI layout.

4. The interface elements are uneven, and the text cannot be fully displayed.

5. Can you remember user settings or operation habits? You need to re-operate the initial environment every time you enter.

6. Whether to give the user a proper prompt when using incomplete Functions

7. Are there any prompts when an error occurs in the user operation.

8. Whether the version carries viruses.

9. Whether maintenance of the version will lose user information.

<Switch> ERP test case template