Method and system for managing test case through APP page entity visual module

Abstract

The invention belongs to the technical field of user interface and interactive design, and discloses a system for managing a test case by an APP page entity visualization module, and the system for managing the test case by the visualization module is composed of a navigation display module, a navigation operation module and a navigation icon module key assembly. And the user is supported to manage and maintain the test case of the APP page from a visual perspective. By directly visualizing the style of the corresponding function, the threshold for testers and other related personnel with low business familiarity to participate in function combing and execution is greatly reduced, a user can visually see and understand the appearance and operation mode of each function module without deeply understanding complex background logic or technical details, and the user experience is improved. Therefore, the operation convenience and the user experience friendliness are remarkably improved, the user is allowed to customize the module by supporting the splitting of the use case and the direct correspondence between the hierarchical module and the APP page, and the problem of name chaos caused by personal differences is effectively solved.

Description

Technical Field

[0001] The present invention belongs to the technical field of user interface and interaction design, and specifically relates to a method and system for managing test cases of an APP page entity visualization module. Background Art

[0002] APP (application) testing is a key step to ensure its correct functionality and high quality on mobile devices. This process relies on carefully designed test cases. There are various test case management strategies, including manual management (such as Excel), professional tools (such as TestLink, Zephyr, Xray) and automated scripting technology. nk, as a free and open source option, provides a complete test management solution, from planning to execution to reporting, all of which support multi-user collaboration, but the high learning cost and the lack of full life cycle management are its shortcomings. In contrast, Zephyr, as a professional test management tool, supports a variety of test types and has powerful reporting and analysis capabilities. However, although Zephyr's simple interface is a highlight, its unique terminology, layout and workflow may bring learning costs to new users, especially for testers with non-technical backgrounds or tight time. In addition, with the increasing richness of functions, the navigation of advanced functions may become complicated, and users need to go through multiple layers of menus to reach the required functions, which not only reduces work efficiency but also increases the chance of errors. Similarly, although the customization options enhance flexibility, its configuration complexity may discourage users who are not familiar with system configuration and make it difficult to fully utilize the tool's potential to optimize the test process. Therefore, it needs to be improved and optimized. Summary of the invention

[0003] The purpose of the present invention is to provide a method and system for managing test cases of an APP page entity visualization module to solve the problems raised in the above background technology.

[0004] In order to achieve the above-mentioned purpose, the present invention provides the following technical solutions: a system for managing test cases of an APP page entity visualization module, wherein the system for managing test cases of the visualization module is composed of key components of a navigation display module, a navigation operation module and a navigation icon module, which together support users to manage and maintain the test cases of the APP page from an intuitive perspective.

[0005] Preferably, the specific steps of the method for managing test cases by the visualization module include:

[0006] Step 1: Writing: including selecting related pages, specifying page elements, corresponding module splitting, and writing use cases;

[0007] Step 2: View: including selecting the related page, clicking the page element, expanding the module, and expanding the use case;

[0008] Step 3: Update the accumulation: including selecting the related pages, clicking the page elements, expanding the modules, and updating the use cases.

[0009] Preferably, the specific steps written in step 1 include:

[0010] A1, enter the system:

[0011] The user first logs in to the APP page entity visualization module management system; after the system verifies the user's identity, it displays the main operation interface;

[0012] A2, select the related page:

[0013] In the main operation interface, users use the browsing and search functions to find the relevant pages for which test cases need to be written;

[0014] A3, specify page elements:

[0015] The user selects a specific page element on the basic image using a mouse or touch screen;

[0016] A4, corresponding module splitting:

[0017] Users can split selected elements and element combinations into independent test modules based on test requirements;

[0018] A5, write a use case:

[0019] In the split modules, users start writing specific test cases.

[0020] Preferably, the specific steps of checking in step 2 include:

[0021] B1, select the related page:

[0022] Similar to writing a test case, the user first selects the associated page to be viewed;

[0023] B2, click on the page element:

[0024] On the page basic image, the user clicks on the page element they want to view;

[0025] B3, expand the module:

[0026] The system automatically expands the test module to which the element belongs based on the clicked element;

[0027] B4, expand the use case:

[0028] Within the module, users further click on a specific test case to expand and view detailed test steps and expected results.

[0029] Preferably, the specific contents of the use case developed in B4 include:

[0030] After successfully expanding the test module and browsing to the list of all test cases contained in it, the user can further drill down to view the details of a specific test case as needed; this step is triggered by clicking on a specific test case item in the list, and the system will respond and expand the detailed view of the test case;

[0031] C1, View detailed test steps:

[0032] In the expanded test case detail view, the first thing presented to the user is the detailed test steps of the test case;

[0033] C2, comparison of expected results:

[0034] The system displays the expected output or result of the test case;

[0035] C3, annotation, marking and export functions:

[0036] When you need to record additional information, mark important points, or export data for later use, add comments next to test steps and expected results to record personal insights, questions, or suggestions for improvement;

[0037] C4, considerations for enhancing user experience:

[0038] Provide friendly user interface design to ensure that information is reasonably laid out and easy to read; implement a quick-response interaction mechanism to reduce user waiting time.

[0039] Preferably, the specific steps of updating the accumulation in step 3 include:

[0040] D1, select the related page:

[0041] The user selects the associated page that needs to be updated for the use case;

[0042] D2, click on the page element:

[0043] Select the page element that needs to update the use case on the page;

[0044] D3, expand module:

[0045] The system expands the corresponding test module according to the selected element;

[0046] D4, update use case:

[0047] The user finds the test case that needs to be updated and clicks the Edit button to enter the editing mode.

[0048] Preferably, the specific contents of the navigation display module include:

[0049] S1. A corresponding selected icon is displayed below the navigation name; open the app and enter the page containing the navigation module; click any navigation item in the navigation module; observe whether a corresponding selected icon appears below the navigation item; verify whether the display style of the selected icon is consistent with the design document;

[0050] S2. Navigation name display control; simulate different navigation name data through the backend interface or database; verify whether the font, size, and color attributes of the navigation name meet the design requirements;

[0051] S3. Check the navigation interface request parameters; use the network packet capture tool and code to simulate sending a homenavigation interface request, and add the abtest parameter to the request parameters; observe whether the interface response is successful, and whether the response data contains content or logic related to the abtest parameter; verify whether the navigation function of the APP still works normally after adding the abtest parameter, without any abnormality or crash;

[0052] S4. After the navigation is updated, it automatically returns to the recommended selection state.

[0053] Preferably, the specific steps of automatically returning to the recommended selected state after the navigation is updated in S4 include:

[0054] E1, enter the non-"recommended" channel in the APP;

[0055] E2, simulate or trigger the update operation of the data returned by the navigation interface;

[0056] E3, observe whether the page automatically jumps back to the "Recommendation" channel;

[0057] E4, verify whether the selected status of other channels is correctly cleared during the jump process.

[0058] The beneficial effects of the present invention are as follows:

[0059] 1. The present invention greatly reduces the threshold for testers and other relevant personnel with low business familiarity to participate in function sorting and execution by directly visualizing the style of corresponding functions. Users can intuitively see and understand the appearance and operation mode of each functional module without in-depth understanding of complex background logic or technical details, thereby significantly improving the convenience of operation and the friendliness of user experience.

[0060] 2. The present invention supports the splitting of use cases and the direct correspondence between hierarchical modules and APP pages, and allows users to customize modules according to their own naming habits and names, effectively solving the problem of naming confusion caused by personal differences. This feature enables both novice and experienced users to quickly and accurately sort out functional modules, and continuously accumulate and improve the use case library in the process, thereby improving the overall work efficiency and accuracy of the team.

[0061] 3. Through the platform of the present invention, users can maintain the integrity of corresponding functions at any time. Whether adding, modifying or deleting functions, they can be immediately reflected in the visual interface. In addition, the platform also supports quick viewing of the complete content of the corresponding functions, so that users can quickly locate and understand relevant information when needed, without switching back and forth between multiple documents or systems, which greatly improves work efficiency and response speed. This real-time and comprehensive feature is of great significance for ensuring product quality and meeting user needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 It is a flow chart of the technical solution of the present invention;

[0063] Figure 2 This is a rendering of the use case module of the present invention;

[0064] Figure 3 The effect diagram of the use case of the present invention is shown;

[0065] Figure 4 Interface diagram used by TestL i nk;

[0066] Figure 5 This is the interface picture of Zephyr. DETAILED DESCRIPTION

[0067] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0068] like Figures 1 to 5 As shown, an embodiment of the present invention provides a system for managing test cases of an APP page entity visualization module. The system for managing test cases of a visualization module is composed of key components of a navigation display module, a navigation operation module and a navigation icon module, which together support users to manage and maintain test cases of APP pages from an intuitive perspective.

[0069] The specific steps of the method for managing test cases with a visualization module include:

[0070] Step 1: Writing: including selecting related pages, specifying page elements, corresponding module splitting, and writing use cases;

[0071] Step 2: View: including selecting the related page, clicking the page element, expanding the module, and expanding the use case;

[0072] Step 3: Update the accumulation: including selecting the related pages, clicking the page elements, expanding the modules, and updating the use cases.

[0073] Among them, the specific steps written in step one include:

[0074] A1, enter the system

[0075] The user first logs in to the APP page entity visualization module management system; after the system verifies the user's identity, it displays the main operation interface;

[0076] A2, select the related page:

[0077] In the main operation interface, users can use the browsing and search functions to find the relevant page for which test cases need to be written; click to select the page, and the system will load and display the basic image of the page and its module element layout;

[0078] A3, specify page elements:

[0079] The user selects a specific page element on the basic image by using a mouse or a touch screen; the system highlights the selected element and displays detailed information about the element (such as element ID, type, attributes, etc.);

[0080] A4, corresponding module split:

[0081] Users can split selected elements or element combinations into independent test modules according to test requirements. The system provides splitting tools or interfaces to help users quickly complete the splitting operation and record the boundaries and relationships of each module.

[0082] A5, write a use case:

[0083] In the split modules, users start writing specific test cases. The system provides a test case editor that supports input of test steps, expected results, preconditions, postconditions and other information. Users can save test cases and set their status (such as pending review, passed, failed, etc.).

[0084] The specific steps reviewed in step 2 include:

[0085] B1, select the related page:

[0086] Similar to writing test cases, users first select the associated pages they want to view. By navigating to a list or directory containing multiple associated pages through the system interface, users can quickly locate the associated pages they want to view based on identification information such as page name, number, and functional classification.

[0087] B2, click on the page element:

[0088] On the page basic image, the user clicks the page element that he wants to view; after the associated page is selected and displayed, the user needs to further locate and click the page element that he wants to view on the page basic image (usually a static or dynamic page screenshot); the page basic image provides a visual interface for the user, allowing the user to intuitively identify each element on the page;

[0089] B3, expand the module:

[0090] The system automatically expands the test module to which the element belongs according to the clicked element; users can view the basic information of the module and all the test cases it contains; when the user clicks a page element, the system will immediately respond to this operation and automatically expand the test module to which the element belongs according to the clicked element information; the expanded module view will display the basic information of the module, such as module name, description, creation time, modification time, etc.; at the same time, users can also see a list or overview of all the test cases contained in the module;

[0091] B4, expand the use case:

[0092] Within the module, users can further click on specific test cases to expand and view detailed test steps and expected results; the system supports annotating, marking or exporting test cases during the viewing process.

[0093] The specific contents of the use cases in B4 include:

[0094] After successfully expanding the test module and browsing to the list of all test cases contained in it, the user can further drill down to view the details of a specific test case as needed; this step is triggered by clicking on a specific test case item in the list, and the system will respond and expand the detailed view of the test case;

[0095] C1, View detailed test steps:

[0096] In the expanded test case detail view, the first thing presented to the user is the detailed test steps of the test case; these steps are listed in a clear and orderly manner, usually including the specific operations, input data, and any necessary configuration or settings for each step; the system may present these steps in the form of a numbered list, a flowchart, or a step wizard so that the user can easily follow and understand the test process; in addition, in order to enhance readability, the system may also support multimedia elements such as syntax highlighting, image insertion, or video demonstration;

[0097] C2, comparison of expected results:

[0098] The system displays the expected output or results for the test case; these expected results are critical to assessing whether the test was successful; users can compare the actual test results with the expected results to determine whether the software works as expected; the system may provide intuitive comparison tools such as difference highlighting, result summaries, or scoring systems to help users quickly identify any deviations or inconsistencies;

[0099] C3, annotation, marking and export functions:

[0100] When you need to record additional information, mark important points, or export data for subsequent use, you can add comments next to test steps and expected results to record personal insights, questions, or suggestions for improvement. At the same time, the system also supports the use of marking functions to highlight key steps, expected results, or problem areas. In addition, users can also choose to export the details of the test case to various formats (such as Word documents, Excel tables, or PDF files) for sharing within the team, archiving, or as part of the project documentation.

[0101] C4, considerations for enhancing user experience:

[0102] Provide a friendly user interface design to ensure that information is laid out reasonably and is easy to read; implement a quick-response interaction mechanism to reduce user waiting time; and provide personalized setting options to allow users to adjust view style, font size, etc. according to their preferences; these measures work together to improve user satisfaction and work efficiency.

[0103] Among them, the specific steps of updating accumulation in step three include:

[0104] D1, select the related page:

[0105] The user selects the associated page that needs to be updated for the use case;

[0106] D2, click on the page element:

[0107] Select the page element that needs to update the use case on the page;

[0108] D3, expand module:

[0109] The system expands the corresponding test module according to the selected element;

[0110] D4, update use case:

[0111] The user finds the test case that needs to be updated and clicks the Edit button to enter the editing mode. In the editing interface, the user can modify the test steps, expected results and other information, and save the updates; the system records the time, user and other information of the update operation for subsequent tracking and auditing.

[0112] Among them, the specific contents of the navigation display module include:

[0113] S1. A corresponding selected icon is displayed below the navigation name; open the app and enter the page containing the navigation module; click any navigation item in the navigation module (such as "Home", "Recommendation", etc.); observe whether the corresponding selected icon appears below the navigation item, and whether the indicator below the navigation name (such as highlight bar, underline, etc.) accurately points to the selected navigation item; verify whether the display style (such as color, shape, etc.) of the selected icon is consistent with the design document;

[0114] S2. Navigation name display control; simulate different navigation name data (including super long names, names containing special characters, pure English names, etc.) through the back-end interface or database; refresh the APP page to observe whether the navigation name in the navigation module is displayed as expected, without truncation, garbled characters or incomplete display; verify whether the font, size, color and other attributes of the navigation name meet the design requirements;

[0115] S3. Check the navigation interface request parameters; use network packet capture tools (such as Char es, Fiddler, etc.) and code to simulate sending a home navigation interface request, and add the abtest parameter to the request parameters; observe whether the interface response is successful, and whether the response data contains content or logic related to the abtest parameter; verify whether the navigation function of the APP still works normally after adding the abtest parameter, without any abnormality or crash;

[0116] S4. After the navigation is updated, it automatically returns to the recommended selection state.

[0117] Among them, the specific steps of automatically returning to the recommended selected state after the navigation in S4 is updated include:

[0118] E1, enter a non-"recommended" channel (such as the "new energy" channel) in the APP;

[0119] E2, simulate or trigger the update operation of the data returned by the navigation interface (such as simulating data changes through the backend service);

[0120] E3, observe whether the page automatically jumps back to the "Recommendation" channel, and whether the corresponding selection icon and indicator appear under the navigation item of the "Recommendation" channel;

[0121] E4, verify whether the selected status of other channels is correctly cleared during the jump process.

[0122] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0123] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A system for managing test cases of an APP page entity visualization module, characterized in that: The system for managing test cases with a visualization module is composed of key components: a navigation display module, a navigation operation module, and a navigation icon module, which together support users to manage and maintain test cases of APP pages from an intuitive perspective.

2. A method for managing test cases of an APP page entity visualization module, characterized in that: The specific steps of the method for managing test cases with a visualization module include: Step 1: Writing: including selecting related pages, specifying page elements, corresponding module splitting, and writing use cases; Step 2: View: including selecting the related page, clicking the page element, expanding the module, and expanding the use case; Step 3: Update the accumulation: including selecting the related pages, clicking the page elements, expanding the modules, and updating the use cases.

3. A method for managing test cases of an APP page entity visualization module according to claim 2, characterized in that: The specific steps written in the step 1 include: A1, enter the system The user first logs in to the APP page entity visualization module management system; after the system verifies the user's identity, it displays the main operation interface; A2, select the related page: In the main operation interface, users use the browsing and search functions to find the relevant pages for which test cases need to be written; A3, specify page elements: The user selects a specific page element on the basic image using a mouse or touch screen; A4, corresponding module splitting: Users can split selected elements and element combinations into independent test modules based on test requirements; A5, write a use case: In the split modules, users start writing specific test cases.

4. A method for managing test cases of an APP page entity visualization module according to claim 2, characterized in that: The specific steps checked in step 2 include: B1, select the related page Similar to writing a test case, the user first selects the associated page to be viewed; B2, click on the page element On the page basic image, the user clicks on the page element they want to view; B3, expand module The system automatically expands the test module to which the element belongs based on the clicked element; B4, expand the use case: Within the module, users further click on a specific test case to expand and view detailed test steps and expected results.

5. A method for managing test cases of an APP page entity visualization module according to claim 4, characterized in that: The specific contents of the use cases in B4 include: After successfully expanding the test module and browsing to the list of all test cases contained in it, the user can further drill down to view the details of a specific test case as needed; this step is triggered by clicking on a specific test case item in the list, and the system will respond and expand the detailed view of the test case; C1, View detailed test steps: In the expanded test case detail view, the first thing presented to the user is the detailed test steps of the test case; C2, comparison of expected results: The system displays the expected output or result of the test case; C3, annotation, marking and export functions: When you need to record additional information, mark important points, or export data for later use, add comments next to test steps and expected results to record personal insights, questions, or suggestions for improvement; C4, considerations for enhancing user experience: Provide friendly user interface design to ensure that information is reasonably laid out and easy to read; implement a quick-response interaction mechanism to reduce user waiting time.

6. A method for managing test cases of an APP page entity visualization module according to claim 2, characterized in that: The specific steps of updating accumulation in step 3 include: D1, select the related page: The user selects the associated page that needs to be updated for the use case; D2, click on the page element: Select the page element that needs to update the use case on the page; D3, expand module: The system expands the corresponding test module according to the selected element; D4, update use case: The user finds the test case that needs to be updated and clicks the Edit button to enter the editing mode.

7. A method for managing test cases of an APP page entity visualization module according to claim 2, characterized in that: The specific contents of the navigation display module include: S1. The corresponding selected icon is displayed below the navigation name; open the APP and enter the page containing the navigation module; Click any navigation item in the navigation module; Observe whether the corresponding selection icon appears under the navigation item; Verify whether the display style of the selected icon is consistent with the design document; S2. Navigation name display control; simulate different navigation name data through the backend interface or database; verify whether the font, size, and color attributes of the navigation name meet the design requirements; S3. Check the navigation interface request parameters; use network packet capture tools and code to simulate sending a homenavigation interface request, and add the abtest parameter to the request parameters; observe whether the interface response is successful, and whether the response data contains content or logic related to the abtest parameter; verify whether the navigation function of the APP still works normally after adding the abtest parameter, without any abnormality or crash; S4. After the navigation is updated, it automatically returns to the recommended selection state.

8. A method for managing test cases of an APP page entity visualization module according to claim 7, characterized in that: The specific steps of automatically returning to the recommended selected state after the navigation is updated in S4 include: E1, enter the non-"recommended" channel in the APP; E2, simulate or trigger the update operation of the data returned by the navigation interface; E3, observe whether the page automatically jumps back to the "Recommendation" channel; E4, verify whether the selected status of other channels is correctly cleared during the jump process.

Images