Software test case management methods, devices and electronic equipment

Abstract

This disclosure provides a software test case management method, apparatus, and electronic device, relating to the field of artificial intelligence technology, particularly natural language processing and intelligent search technology. The specific implementation scheme is as follows: The software to be tested and its corresponding test case set are obtained; the test cases in the test case set are configured with hierarchical information, including usage scenarios, functional points, and test points; upon receiving a test case review request, the target review role is determined based on the review object identifier in the request; the content to be reviewed is determined based on the target review role and the test case set; the content to be reviewed is provided to the review object corresponding to the review object identifier for review processing, thereby avoiding providing a large number of test cases to the review object, shortening review time, improving review efficiency, and ensuring the quality of the software and the project to which the software belongs.

Description

Technical Field

[0001] This disclosure relates to the field of artificial intelligence technology, particularly to the fields of natural language processing and intelligent search, and especially to a software test case management method, apparatus, and electronic device. Background Technology

[0002] In current software test case management systems, multiple test cases are listed during the design phase of the software to be tested, categorized by name, steps, and expected results. During the review phase, reviewers at different levels face a large number of test cases, resulting in lengthy review times, low efficiency, and negatively impacting both software quality and the quality of the project to which the software belongs. Summary of the Invention

[0003] This disclosure provides a software test case management method, apparatus, and electronic device.

[0004] According to one aspect of this disclosure, a software test case management method is provided. The method includes: acquiring software to be tested and a set of test cases corresponding to the software; the test cases in the test case set are configured with hierarchical information; the hierarchical information includes usage scenarios, functional points, and test points; upon receiving a test case review request, determining a target review role based on a review object identifier in the test case review request; determining the content to be reviewed based on the target review role and the test case set; and providing the content to be reviewed to the review object corresponding to the review object identifier for review processing.

[0005] According to another aspect of this disclosure, a software test case management device is provided. The device includes: a first acquisition module, configured to acquire software to be tested and a set of test cases corresponding to the software; the test cases in the test case set are configured with hierarchical information; the hierarchical information includes usage scenarios, functional points, and test points; a first determination module, configured to determine a target review role based on a review object identifier in a test case review request upon receiving a test case review request; a second determination module, configured to determine the content to be reviewed based on the target review role and the test case set; and a providing module, configured to provide the content to be reviewed to the review object corresponding to the review object identifier for review processing.

[0006] According to another aspect of this disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the software test case management method proposed above in this disclosure.

[0007] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided that stores computer instructions for causing a computer to execute the software test case management method proposed in this disclosure above.

[0008] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the software test case management method proposed above in this disclosure.

[0009] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0011] Figure 1 This is a schematic diagram based on the first embodiment of the present disclosure;

[0012] Figure 2 This is a diagram illustrating the hierarchical architecture in software;

[0013] Figure 3 This is a schematic diagram according to the second embodiment of the present disclosure;

[0014] Figure 4 This is a schematic diagram according to the third embodiment of the present disclosure;

[0015] Figure 5 This is a schematic diagram illustrating the determination of the regression range in the software;

[0016] Figure 6 This is a diagram illustrating the review process in software test case management.

[0017] Figure 7 This is a schematic diagram of the architecture of a software test case management system;

[0018] Figure 8 This is a schematic diagram according to the fourth embodiment of the present disclosure;

[0019] Figure 9 This is a block diagram of an electronic device used to implement the software test case management method of the embodiments of this disclosure. Detailed Implementation

[0020] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0021] In current software test case management systems, multiple test cases are listed during the design phase of the software to be tested, categorized by name, steps, and expected results. During the review phase, reviewers at different levels face a large number of test cases, making it difficult to identify the content requiring review to determine test coverage. This results in lengthy review times, low efficiency, and negatively impacts both software quality and the quality of the project as a whole.

[0022] To address the aforementioned issues, this disclosure proposes a software test case management method, apparatus, and electronic device.

[0023] Figure 1 The diagram illustrates a first embodiment of this disclosure. It should be noted that the software test case management method of this disclosure can be applied to a software test case management device, which can be configured in an electronic device to enable the electronic device to perform software test case management functions. The following embodiments use an electronic device as an example for illustration.

[0024] Among them, electronic devices can be any device with computing capabilities, such as personal computers (PCs), mobile terminals, servers, etc. Mobile terminals can be, for example, in-vehicle devices, mobile phones, tablets, personal digital assistants, wearable devices, smart speakers, and other hardware devices with various operating systems, touch screens, and / or displays.

[0025] like Figure 1 As shown, this software test case management method may include the following steps:

[0026] Step 101: Obtain the software to be tested and the corresponding set of test cases; the test cases in the set of test cases are set with hierarchical information; the hierarchical information includes usage scenarios, functional points and test points.

[0027] In this embodiment of the disclosure, the software includes at least one use scenario; each use scenario includes at least one functional point; each functional point includes at least one test point; and each test point includes one test case. The hierarchical architecture diagram of the software can be illustrated as follows: Figure 2 As shown, in Figure 2In the software, there are N scenarios (use scenarios); each scenario (use scenario) has N functional points; and each functional point has N test points.

[0028] In this embodiment of the disclosure, the usage scenario is determined according to the corresponding usage requirements of the software; the functional points in the usage scenario are determined according to the process nodes in the usage flow of the software in the usage scenario; and the test points under the functional points are determined according to the situations that may be encountered during the execution of the process nodes corresponding to the functional points.

[0029] Taking shopping software as an example, usage scenarios include purchasing daily necessities, food, and electronics. In the daily necessities purchase scenario, functionalities include account login, selecting daily necessities, adding items to the cart, and placing an order. For account login, test cases include normal login, incorrect account login, and incorrect password login.

[0030] Specifically, by combining the software's usage requirements, process nodes in the usage flow, and possible situations encountered during the execution of process nodes, test cases in the corresponding test case set of the software are set in layers according to usage scenarios, functional points under usage scenarios, and test points under functional points. This makes it easier for users to understand the purpose of each test case and the logical relationship between each test case, thereby improving the efficiency of test case management.

[0031] In the embodiments of this disclosure, among the functional points set in multiple usage scenarios, there are identical functional points; or, there are no identical functional points. Among the test points set under multiple functional points, there are identical test points; or, there are no identical test points.

[0032] Because some use cases are similar, such as the purchase of daily necessities and the purchase of food, the same functionalities may exist in some of these scenarios. For example, both the purchase of daily necessities and the purchase of food include an account login function.

[0033] In this context, the same functionalities set up in multiple use cases can have different dependencies or relationships depending on their location within those scenarios. This facilitates understanding the relationships between functionalities and other functionalities, improves subsequent reviews, and ultimately enhances the efficiency of test case review.

[0034] Step 102: Upon receiving a test case review request, determine the target review role based on the review object identifier in the test case review request.

[0035] In this embodiment of the disclosure, the electronic device may perform step 102 as follows: query the role database according to the review object identifier, obtain the review role corresponding to the review object identifier in the role database, and determine the review role corresponding to the review object identifier as the target review role.

[0036] The role database can include review roles corresponding to each review object identifier in each software. Specifically, for each software, the review roles set in the role database include at least one of the following: management role, development role, and testing role; the management role is used to perform reviews at the use case level; the development role is used to perform reviews at the function point level; and the testing role is used to perform reviews at the test point level.

[0037] Different software programs can have the same review roles based on their functions; or they can have different review roles.

[0038] The management role, which performs reviews at the usage scenario level, reviews whether the usage scenarios covered in the test case set are comprehensive and cover all usage scenarios in the software. The development role, which performs reviews at the function point level, reviews whether the function points covered in the test case set for all or some usage scenarios are comprehensive and cover all function points in the software for that usage scenario.

[0039] Among them, the test role, which performs the review at the test point level, refers to reviewing whether the test points under that function point in the test case set are comprehensive and whether they cover all test points under that function point in the software, for all or some function points.

[0040] In this embodiment of the disclosure, the number of review roles corresponding to a review object identifier can be one or more. That is, a review object corresponding to a review object identifier can have multiple review roles at the same time to perform reviews at different levels.

[0041] The setup of multiple review roles, and the different review roles used to perform reviews at different levels, enables electronic devices to identify the corresponding review objects and provide content at the appropriate level for review. This avoids providing a large number of test cases, which would otherwise require the review objects to select the content to be reviewed from a large number of test cases, thereby further improving review efficiency.

[0042] Step 103: Determine the content to be reviewed based on the target review role and the set of test cases.

[0043] In this embodiment of the disclosure, different review roles are used to perform reviews at different levels. By combining the target review role and the test case set, the level that needs to be reviewed can be determined. Based on the level that needs to be reviewed and the test case set, the content that needs to be reviewed can be determined, and then the content to be reviewed can be determined.

[0044] The content to be reviewed includes, for example, specific use cases in the software, specific functionalities in a specific use case, and specific test points for a specific functionality.

[0045] Step 104: Provide the content to be reviewed to the review object corresponding to the review object identifier for review processing.

[0046] In this embodiment of the disclosure, after step 104, the electronic device may further perform the following process: obtain the review result corresponding to the content to be reviewed; when the review result includes content to be supplemented at the target level, perform update prompt processing based on the content to be supplemented at the target level.

[0047] The number of items to be supplemented can be one or more. For example, if the target level is the use case, the review result may include the need to supplement a certain use case; if the target level is the function point, the review result may include the need to supplement a certain function point under a certain use case; if the target level is the test point, the review result may include the need to supplement a certain test point under a certain function point.

[0048] In this process, the electronic device acquires the content to be supplemented at the target level and provides update prompts, which facilitates relevant objects, such as development objects, to adjust the corresponding test case set of the software, such as adding test cases, to ensure the comprehensiveness of the test case set during testing and further improve the testing efficiency of the software.

[0049] The software test case management method of this disclosure involves acquiring the software to be tested and the corresponding test case set. The test cases in the test case set are configured with hierarchical information, including usage scenarios, functional points, and test points. Upon receiving a test case review request, a target review role is determined based on the review object identifier in the request. The content to be reviewed is determined based on the target review role and the test case set. The content to be reviewed is provided to the review object corresponding to the review object identifier for review processing. This avoids providing a large number of test cases to the review object, shortens review time, improves review efficiency, and ensures the quality of the software and the project to which the software belongs.

[0050] To accurately determine the content to be reviewed and obtain the content suitable for the review object corresponding to the review object identifier, the target review role can be combined to determine the target test cases and target levels. Then, the content of the target level set on the target test cases in the test case set can be obtained to determine the content to be reviewed. For example... Figure 3 As shown, Figure 3 This is a schematic diagram based on the second embodiment of the present disclosure. Figure 3 The illustrated embodiment may include the following steps:

[0051] Step 301: Obtain the software to be tested and the corresponding set of test cases; the test cases in the set of test cases are set with hierarchical information; the hierarchical information includes usage scenarios, functional points and test points.

[0052] Step 302: Upon receiving a test case review request, determine the target review role based on the review object identifier in the test case review request.

[0053] Step 303: Based on the target review role, determine the target test cases and target levels in the test case set.

[0054] In this embodiment of the disclosure, the process of the electronic device performing step 303 may be as follows: obtaining the test case configuration corresponding to the target review role; the test case configuration includes the test cases that the target review role is interested in and the levels that are interested in the test cases; determining the interested test cases as target test cases; and determining the interested level information as target levels.

[0055] Specifically, the test cases that the target review role focuses on refer to the specific levels involved in those test cases that the target review role needs to review. The levels of focus within a test case refer to the content of that level within the test case that the target review role needs to review.

[0056] The test case configurations for each review role can be pre-configured or modified according to the needs of the reviewer. Multiple reviewers can use the same review role. To facilitate personalization among multiple reviewers, different test case configurations can be provided for reviewers using the same review role, based on their review habits. In other words, a relationship is established between the test case configuration, the reviewer identifier, and the corresponding review role.

[0057] In this case, taking the review object corresponding to the review object identifier as the development object as an example, the corresponding review role can be a development role. There can be multiple development objects, used to review and process functionalities in different use cases. For example, the first development object reviews and processes functionalities in the first use case; the second development object reviews and processes functionalities in the second use case; the third development object reviews and processes functionalities in the third use case, and so on.

[0058] Within the same use case, there can be multiple development objects. Different development objects may have different review habits; for example, one development object might only review features specific to the use case, while another might review both features and test cases within the same use case. Therefore, different test case configurations can be set for different review object identifiers under the same review role.

[0059] The configuration of test cases for different review roles allows electronic devices to determine different target test cases or different target levels for different review object identifiers. This enables the provision of different review content to the review objects corresponding to different review object identifiers, thus providing the most suitable review content to the review object and avoiding the provision of a large amount of content that is not closely related to the review, such as specific test cases. This further shortens the review time, improves the review efficiency, and further improves the efficiency of software testing.

[0060] Step 304: Determine the content to be reviewed based on the target level content set on the target test case.

[0061] In one example of this disclosure, the electronic device performing step 304 may be as follows: when there are multiple contents at the target level and the contents of the target upper-level layers to which the multiple target levels belong are the same, the contents of the multiple target levels are fused to obtain fused content; and the fused content is determined as the content to be reviewed.

[0062] If multiple target levels belong to the same target upper level, for example, if they are levels under the same usage scenario, all content of the target level set according to the target test cases can be merged, that is, the content of all functional points can be merged to obtain the content to be reviewed.

[0063] For example, taking the target level as the functional point, the content set in the target level of multiple target test cases are account login, daily necessities selection, and order placement in the daily necessities purchase scenario. The content to be reviewed by merging them can be, for example, "The daily necessities purchase scenario has three functional points: account login, daily necessities selection, and order placement."

[0064] In cases where multiple target levels belong to the same upper-level target, the content of multiple target levels under that upper-level target is merged. This facilitates the reviewers in reviewing the content of multiple target levels under that upper-level target to determine the test coverage of that target level, thereby further improving review efficiency.

[0065] In another example of this disclosure embodiment, the electronic device performing step 304 may, for example, acquire multiple target upper-level layers when there are multiple target layers of content and the content of the target upper-level layers to which the multiple target layers belong is different; for each target upper-level layer, perform fusion processing on the content of the target layer belonging to the target upper-level layer to obtain sub-review content; and combine multiple sub-review content to obtain the content to be reviewed.

[0066] Taking the target level as a functional point as an example, the content set in the target level of multiple target test cases are account login and daily necessities selection in the daily necessities purchase scenario, and food selection and ordering in the food purchase scenario. Then, one sub-review content is determined based on account login and daily necessities selection in the daily necessities purchase scenario, for example, it can be "There are two functional points set in the daily necessities purchase scenario: account login and daily necessities selection"; another sub-review content is determined based on food selection and ordering in the food purchase scenario, for example, it can be "There are two functional points in the food purchase scenario: food selection and ordering".

[0067] In cases where multiple target levels belong to different upper-level target contents, different sub-review contents are generated according to the contents of the upper-level target contents. This makes it easier for reviewers to review and process the sub-review contents of different upper-level target contents, thereby further improving review efficiency.

[0068] Step 305: Provide the content to be reviewed to the review object corresponding to the review object identifier for review processing.

[0069] It should be noted that for details regarding steps 301 to 302 and step 305, please refer to [the relevant documentation / reference]. Figure 1 Steps 101 to 102 and step 104 in the illustrated embodiment will not be described in detail here.

[0070] The software test case management method of this disclosure involves acquiring the software to be tested and the corresponding test case set. The test cases in the test case set are configured with hierarchical information, including usage scenarios, functional points, and test points. Upon receiving a test case review request, a target review role is determined based on the review object identifier in the request. Based on the target review role, target test cases and target hierarchies in the test case set are determined. The content to be reviewed is determined based on the content of the target hierarchies set on the target test cases. The content to be reviewed is provided to the review object corresponding to the review object identifier for review processing. This method provides appropriate content to be reviewed to the review object, avoiding providing a large number of test cases, shortening review time, improving review efficiency, and ensuring the quality of the software and the project to which the software belongs.

[0071] In this way, by combining the content of the adjusted levels, the regression scope can be accurately determined, avoiding the omission or duplication of test cases, and further improving testing efficiency. For example... Figure 4 As shown, Figure 4 This is a schematic diagram based on the third embodiment of the present disclosure. Figure 4 The illustrated embodiment may include the following steps:

[0072] Step 401: Obtain the software to be tested and the corresponding test case set; the test cases in the test case set are set with hierarchical information; the hierarchical information includes usage scenarios, functional points and test points.

[0073] Step 402: Upon receiving a test case review request, determine the target review role based on the review object identifier in the test case review request.

[0074] Step 403: Determine the content to be reviewed based on the target review role and the set of test cases.

[0075] Step 404: Provide the content to be reviewed to the review object corresponding to the review object identifier for review processing.

[0076] After step 404 in this embodiment, the electronic device may also perform the following process: after the review is passed, each test case in the test case set is executed to obtain test results; based on the test results, abnormal usage scenarios, abnormal functional points or abnormal test points in the software are determined; and the software is adjusted according to the abnormal usage scenarios, abnormal functional points or abnormal test points.

[0077] The process for determining whether an electronic device has passed a review can be as follows: obtain the review result corresponding to the content to be reviewed; if the review result includes supplementary content at the target level, the review is deemed unsuccessful and an update prompt needs to be made based on the supplementary content at the target level; if the review result does not include supplementary content, the review is deemed successful.

[0078] Abnormal use cases include, for example, use cases to be added, use cases to be modified, and use cases to be deleted. Abnormal functional points include, for example, functional points to be added, functional points to be modified, and functional points to be deleted. Abnormal test points include, for example, test points to be added, test points to be modified, and test points to be deleted.

[0079] In this process, electronic devices, based on test results, identify abnormal usage scenarios, abnormal functionalities, or abnormal test points in the software, and then adjust and process the software to improve the efficiency of software adjustment, thereby further improving the efficiency of software testing.

[0080] Step 405: Obtain the first-level content that has changed in the software; the first-level content includes at least one of the following: usage scenario content, function point content, and test point content.

[0081] This includes: Use case content, such as the name and identifier of the use case that has changed; Function point content, such as the name and identifier of the function point that has changed; A change in a function point can refer to a change in the test point under that function point, or a change in the function point itself; and Test point content, such as the name and identifier of the test point that has changed. A change in a test point can refer to a change in the test case under that test point, or a change in the test point itself.

[0082] The number of first-level content changes in the software can be one or more.

[0083] Step 406: Determine the regression scope based on the first-level content and the test case set.

[0084] In this embodiment of the disclosure, the regression scope may include test cases that need to be re-executed. Correspondingly, the process of the electronic device performing step 406 may, for example, be to determine the first level to which the first level content belongs, and the first usage scenario to which the first level belongs; and to combine the test cases in the test case set that are set with the first usage scenario to obtain the regression scope.

[0085] Where the first level of content pertains to a use case, test cases in the test case set that are set to the first level can be used as test cases in the regression scope. Where the first level of content pertains to a function point or test point, determine the first use case to which the function point or test point belongs; test cases in the test case set that are set to the first use case are used as test cases in the regression scope.

[0086] The first level of content refers to the first level to which the first level of content belongs, that is, the first level that contains the first level of content. For example, the first level is a functional point; the first level of content includes, for example, account login, daily necessities selection, adding daily necessities to the shopping cart, placing an order, etc.

[0087] In this process, by combining the hierarchical relationship between usage scenarios, functional points, and test points, as well as the first level of content that has changed in the software, the first usage scenario is determined. Then, the test cases set with the first usage scenario are determined as test cases in the regression scope. Due to the decoupling relationship between usage scenarios, determining the regression scope based on the usage scenario hierarchy can reduce the number of test cases in the regression scope, avoid missing test cases that need to be re-executed, avoid manually determining the regression scope, improve the efficiency of determining the regression scope, and thus further improve the efficiency of software testing.

[0088] The following example illustrates this. For example... Figure 5 The diagram shown illustrates the determination of the regression range in the software. Figure 5 In the process, step 501: For the software, developers can modify function a (functional point) and function b during development and perform system annotation processing. Step 502: The electronic device monitors the software through annotation and determines that function a has changed. For function a, the electronic device automatically identifies scenario (usage scenario) A' containing function a and scenario A. Step 503: The electronic device determines that function b has also changed. For function b, the electronic device automatically identifies scenario B containing function b. Step 504: The electronic device selects test cases (test cases) for scenario A', scenario A, and scenario B and re-executes them.

[0089] Step 407: Re-execute at least one test case in the regression scope to obtain the test results.

[0090] It should be noted that for details of steps 401 to 404, please refer to [the relevant documentation / reference]. Figure 1 Steps 101 to 104 in the illustrated embodiment will not be described in detail here.

[0091] The software test case management method of this disclosure involves obtaining the software to be tested and a set of test cases corresponding to the software. The test cases in the test case set are configured with hierarchical information, including usage scenarios, functional points, and test points. Upon receiving a test case review request, a target review role is determined based on the review object identifier in the test case review request. The content to be reviewed is determined based on the target review role and the test case set. The content to be reviewed is provided to the review object corresponding to the review object identifier for review processing. The method also involves obtaining the first-level content that has changed in the software. The first-level content includes at least one of the following: usage scenario content, functional point content, and test point content. A regression range is determined based on the first-level content and the test case set. At least one test case within the regression range is re-executed to obtain test results. The hierarchical setting of usage scenarios, functional points, and test points for test cases allows for accurate determination of the regression range when the software changes, thereby improving the accuracy and efficiency of determining the regression range when the software changes, further improving software testing efficiency, and ensuring the quality of the software and the project to which the software belongs.

[0092] The following example illustrates this. For example... Figure 6 The image shown is a diagram illustrating the review process in software test case management. Figure 6 The process includes the following steps: Step 601: Reviewers log in to the software test case management system (located on an electronic device). Step 602: The system automatically identifies roles, that is, it queries the role binding data (role database) based on the reviewer's identifier (review object identifier) ​​to determine the target review role. Step 603: Based on the target review role, a specific software and version within a project are selected (determining the target test cases and target levels within the software). Step 604: The system, based on the specific software and version within a project, and the corresponding relationship between the role and the test case levels that the role focuses on (test case configuration), obtains the role-specific review test cases and pushes them to the reviewers. Step 605: The reviewers conduct the review process to determine whether the review is passed; if the review is passed, the review ends; if the review is not passed, the test cases are modified and the data is entered into the system.

[0093] The following example illustrates this. For example... Figure 7 The image shown is a schematic diagram of the architecture of a software test case management system. Figure 7The software test case management system may include: a database (701), a test case design module (702), a test case review module (703), a test case execution module (704), a data analysis and statistics module (705), and a test report module (706). The database (701) stores test cases, test case configurations, and role databases. The test case design module (702) interacts with developers to design test cases. The test case review module (703) interacts with reviewers to review test cases. The test case execution module (704) executes test cases from the software's test case set or regression scope based on execution requests. The test report module (706) generates a test report for the software based on the execution results after test case execution. The data analysis and statistics module (705) tracks the number of executions, execution time, and execution status during test case execution.

[0094] To implement the above embodiments, this disclosure also provides a software test case management device. For example... Figure 8 As shown, Figure 8 This is a schematic diagram according to the fourth embodiment of the present disclosure. The software test case management device 80 may include: a first acquisition module 801, a first determination module 802, a second determination module 803, and a provision module 804.

[0095] The system includes a first acquisition module 801, used to acquire the software to be tested and a set of test cases corresponding to the software; the test cases in the test case set are configured with hierarchical information, including usage scenarios, functional points, and test points; a first determination module 802, used to determine the target review role based on the review object identifier in the test case review request when a test case review request is received; a second determination module 803, used to determine the content to be reviewed based on the target review role and the test case set; and a providing module 804, used to provide the content to be reviewed to the review object corresponding to the review object identifier for review processing.

[0096] As one possible implementation of this disclosure, the software includes at least one usage scenario; each usage scenario includes at least one functional point; each functional point includes at least one test point; and each test point includes one test case.

[0097] As one possible implementation of this disclosure, the usage scenario is determined based on the usage requirements corresponding to the software; the functional points in the usage scenario are determined based on the process nodes in the usage flow of the software in the usage scenario; and the test points under the functional points are determined based on the situations that may be encountered during the execution of the process nodes corresponding to the functional points.

[0098] As one possible implementation of this disclosure, the first determining module 802 is specifically used to: query the role database according to the review object identifier, obtain the review role in the role database corresponding to the review object identifier; and determine the review role corresponding to the review object identifier as the target review role.

[0099] As one possible implementation of this disclosure, the review roles in the role database include at least one of the following: management roles, development roles, and testing roles; the management roles are used to perform reviews at the use case level; the development roles are used to perform reviews at the function point level; and the testing roles are used to perform reviews at the test point level.

[0100] As one possible implementation of this disclosure, the second determining module 803 includes a first determining unit and a second determining unit; the first determining unit is used to determine the target test case and the target level in the test case set according to the target review role; the second determining unit is used to determine the content to be reviewed according to the content of the target level set on the target test case.

[0101] As one possible implementation of this disclosure, the first determining unit is specifically used to: obtain the test case configuration corresponding to the target review role; the test case configuration includes the test cases that the target review role is interested in and the levels that are interested in the test cases; determine the interested test cases as the target test cases; and determine the interested level information as the target level.

[0102] As one possible implementation of this disclosure, the second determining unit is specifically used to, when there are multiple contents at the target level and the contents of the target upper-level to which the multiple target levels belong are the same, perform fusion processing on the contents of the multiple target levels to obtain fused content; and determine the fused content as the content to be reviewed.

[0103] As one possible implementation of this disclosure, the second determining unit is further configured to: obtain multiple target upper-level layers when the number of contents at the target level is multiple and the contents of the target upper-level layers to which the multiple target levels belong are different; for each target upper-level layer, perform fusion processing on the contents of the target level belonging to the target upper-level layer to obtain sub-review contents; and combine multiple sub-review contents to obtain the contents to be reviewed.

[0104] As one possible implementation of this disclosure, the apparatus further includes: a second acquisition module and an update prompt module; the second acquisition module is used to acquire the review result corresponding to the content to be reviewed; the update prompt module is used to perform update prompt processing based on the content to be supplemented at the target level when the review result includes the content to be supplemented at the target level.

[0105] As one possible implementation of this disclosure, the apparatus further includes: a third acquisition module, a third determination module, and an adjustment processing module; the third acquisition module is used to execute each test case in the test case set after the review is passed, and obtain test results; the third determination module is used to determine abnormal usage scenarios, abnormal functional points, or abnormal test points in the software based on the test results; the adjustment processing module is used to adjust the software according to the abnormal usage scenarios, abnormal functional points, or abnormal test points.

[0106] As one possible implementation of this disclosure, the apparatus further includes: a fourth acquisition module, a fourth determination module, and a fifth acquisition module; the fourth acquisition module is used to acquire first-level content that has changed in the software; the first-level content includes at least one of the following: usage scenario content, function point content, and test point content; the fourth determination module is used to determine a regression range based on the first-level content and the test case set; the fifth acquisition module is used to re-execute at least one test case in the regression range to obtain test results.

[0107] As one possible implementation of this disclosure, the fourth determining module is specifically used to: determine the first level to which the first level content belongs, and the first usage scenario to which the first level belongs; and combine the test cases in the test case set that are set with the first usage scenario to obtain the regression range.

[0108] As one possible implementation of this disclosure, among the functional points set in multiple usage scenarios, there are identical functional points; or, there are no identical functional points; among the test points set under multiple functional points, there are identical test points; or, there are no identical test points.

[0109] The software test case management device of this disclosure acquires the software to be tested and the corresponding test case set. The test cases in the test case set are configured with hierarchical information, including usage scenarios, functional points, and test points. Upon receiving a test case review request, the device determines the target review role based on the review object identifier in the request. Based on the target review role and the test case set, the device determines the content to be reviewed. The content to be reviewed is then provided to the review object corresponding to the review object identifier for review processing. This avoids providing a large number of test cases to the review object, shortens review time, improves review efficiency, and ensures the quality of the software and the project to which the software belongs.

[0110] In the technical solutions disclosed herein, the collection, storage, use, processing, transmission, provision, and disclosure of users' personal information are all carried out with the consent of the users, and all comply with the provisions of relevant laws and regulations, and do not violate public order and good morals.

[0111] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0112] Figure 9 A schematic block diagram of an example electronic device 900 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0113] like Figure 9 As shown, device 900 includes a computing unit 901, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 902 or a computer program loaded from storage unit 908 into random access memory (RAM) 903. RAM 903 may also store various programs and data required for the operation of device 900. The computing unit 901, ROM 902, and RAM 903 are interconnected via bus 904. Input / output (I / O) interface 905 is also connected to bus 904.

[0114] Multiple components in device 900 are connected to I / O interface 905, including: input unit 906, such as keyboard, mouse, etc.; output unit 907, such as various types of monitors, speakers, etc.; storage unit 908, such as disk, optical disk, etc.; and communication unit 909, such as network card, modem, wireless transceiver, etc. Communication unit 909 allows device 900 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0115] The computing unit 901 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 901 performs the various methods and processes described above, such as software test case management methods. For example, in some embodiments, the software test case management method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and / or installed on device 900 via ROM 902 and / or communication unit 909. When the computer program is loaded into RAM 903 and executed by the computing unit 901, one or more steps of the software test case management method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform software test case management methods by any other suitable means (e.g., by means of firmware).

[0116] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0117] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0118] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0119] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0120] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0121] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0122] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0123] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A software test case management method, the method comprising: Obtain the software to be tested, and the set of test cases corresponding to the software; Based on the business logic relationships of the software, obtain the hierarchical information of the test cases in the test case set; the hierarchical information includes usage scenarios, functional points, and test points. Upon receiving a test case review request, the role database is queried based on the review object identifier to obtain the review role corresponding to the review object identifier in the role database. The review role corresponding to the review object identifier is determined as the target review role; wherein, the role database includes review roles corresponding to different review object identifiers in different software, and different review roles are used to perform reviews at different levels; Based on the target review role, determine the target test cases and target levels in the test case set; Based on the content of the target level set in the target test cases, determine the content to be reviewed; The content to be reviewed is provided to the review object corresponding to the review object identifier for review processing. The method further includes: Acquire the first-level content that has changed in the software; the first-level content includes at least one of the following: usage scenario content, functional point content, and test point content; Determine the first level to which the content of the first level belongs, and the first use case to which the first level belongs; The test cases in the test case set that contain the first use case are combined to obtain the regression range; Re-execute at least one test case in the regression range to obtain test results; The step of determining the content to be reviewed based on the content of the target level set on the target test case includes: When there are multiple contents at the target level, and the contents of the target upper levels to which the multiple target levels belong are different, multiple target upper levels are obtained; For each target's upper level, the content belonging to the target's upper level is merged to obtain sub-review content; The content to be reviewed is obtained by combining multiple sub-review contents.

2. The method according to claim 1, wherein, The software includes at least one use case; each use case includes at least one function point; each function point includes at least one test point; and each test point includes one test case.

3. The method according to claim 1 or 2, wherein, The usage scenario is determined based on the usage requirements corresponding to the software. The functional points in the usage scenario are determined based on the process nodes in the usage flow of the software in the usage scenario. The test points under the function points are determined based on the situations that may be encountered during the execution of the process nodes corresponding to the function points.

4. The method according to claim 1, wherein, The review roles in the role database include at least one of the following: management roles, development roles, and testing roles; The management role is used to perform reviews at the usage scenario level; The development role is used to perform feature point level reviews; The testing role is used to perform reviews at the test point level.

5. The method according to claim 1, wherein, The step of determining the target test cases and target levels in the test case set based on the target review role includes: Obtain the test case configuration corresponding to the target review role; the test case configuration includes the test cases that the target review role is interested in and the levels of interest in the test cases; The test cases of interest are identified as the target test cases; The information of interest at a certain level is determined as the target level.

6. The method according to claim 1, wherein, The step of determining the content to be reviewed based on the content of the target level set on the target test case includes: When there are multiple contents at the target level, and the contents of the target upper level to which the multiple target levels belong are the same, the contents of the multiple target levels are fused to obtain fused content. The fused content is identified as the content to be reviewed.

7. The method according to claim 1, wherein, After providing the content to be reviewed to the review object corresponding to the review object identifier, the method further includes: Obtain the review results corresponding to the content to be reviewed; When the review results include content to be supplemented at the target level, an update prompt is made based on the content to be supplemented at the target level.

8. The method according to claim 1 or 7, wherein, The method further includes: After the review is approved, each test case in the test case set is executed and the test results are obtained. Based on the test results, identify abnormal usage scenarios, abnormal functionalities, or abnormal test points in the software. The software is adjusted and processed according to the abnormal usage scenarios, abnormal functional points, or abnormal test points.

9. The method according to claim 2, wherein, Among the functionalities set in multiple use cases, there are identical functionalities; or, there are no identical functionalities. Among the test points set under multiple function points, there are identical test points; or, there are no identical test points.

10. A software test case management device, the device comprising: The first acquisition module is used to acquire the software to be tested and the set of test cases corresponding to the software. Based on the business logic relationships of the software, obtain the hierarchical information of the test cases in the test case set; the hierarchical information includes usage scenarios, functional points, and test points. The first determining module is used to, upon receiving a test case review request, query the role database based on the review object identifier to obtain the review role corresponding to the review object identifier in the role database; and determine the review role corresponding to the review object identifier as the target review role; wherein, the role database includes review roles corresponding to different review object identifiers in different software, and different review roles are used to perform reviews at different levels; The second determining module is used to determine the content to be reviewed based on the target review role and the test case set; A module is provided to provide the content to be reviewed to the review object corresponding to the review object identifier for review processing. The device further includes: a fourth acquisition module, a fourth determination module, and a fifth acquisition module; The fourth acquisition module is used to acquire the first-level content that has changed in the software; the first-level content includes at least one of the following: usage scenario content, function point content, and test point content. The fourth determining module determines the first level to which the first level content belongs, and the first usage scenario to which the first level belongs; it then combines the test cases in the test case set that contain the first usage scenario to obtain the regression range. The fifth acquisition module is used to re-execute at least one test case in the regression range to obtain test results; The second determining module includes a first determining unit and a second determining unit; The first determining unit is configured to determine the target test cases and target levels in the test case set based on the target review role; The second determining unit is used to determine the content to be reviewed based on the content of the target level set on the target test case; The second determining unit is further configured to obtain multiple target upper-level layers when the number of contents in the target layer is multiple and the contents of the target upper-level layers to which the multiple target layers belong are different. For each target's upper level, the content belonging to the target's upper level is merged to obtain sub-review content; The content to be reviewed is obtained by combining multiple sub-review contents.

11. The apparatus according to claim 10, wherein, The software includes at least one use case; each use case includes at least one function point; each function point includes at least one test point; and each test point includes one test case.

12. The apparatus according to claim 10 or 11, wherein, The usage scenario is determined based on the usage requirements corresponding to the software. The functional points in the usage scenario are determined based on the process nodes in the usage flow of the software in the usage scenario. The test points under the function points are determined based on the situations that may be encountered during the execution of the process nodes corresponding to the function points.

13. The apparatus according to claim 10, wherein, The review roles in the role database include at least one of the following: management roles, development roles, and testing roles; The management role is used to perform reviews at the usage scenario level; The development role is used to perform feature point level reviews; The testing role is used to perform reviews at the test point level.

14. The apparatus according to claim 10, wherein, The first determining unit is specifically used for, Obtain the test case configuration corresponding to the target review role; the test case configuration includes the test cases that the target review role is interested in and the levels of interest in the test cases; The test cases of interest are identified as the target test cases; The information of interest at a certain level is determined as the target level.

15. The apparatus according to claim 10, wherein, The second determining unit is specifically used for, When there are multiple contents at the target level, and the contents of the target upper level to which the multiple target levels belong are the same, the contents of the multiple target levels are fused to obtain fused content. The fused content is identified as the content to be reviewed.

16. The apparatus according to claim 10, wherein, The device further includes: a second acquisition module and an update notification module; The second acquisition module is used to acquire the review result corresponding to the content to be reviewed; The update prompt module is used to provide update prompts based on the content to be supplemented at the target level when the review results include such content.

17. The apparatus according to claim 10 or 16, wherein, The device further includes: a third acquisition module, a third determination module, and an adjustment processing module; The third acquisition module is used to execute and process each test case in the test case set after the review is passed, and to obtain the test results. The third determining module is used to determine abnormal usage scenarios, abnormal functional points, or abnormal test points in the software based on the test results. The adjustment processing module is used to adjust the software according to the abnormal usage scenario, the abnormal function point, or the abnormal test point.

18. The apparatus according to claim 11, wherein, Among the functionalities set in multiple use cases, there are identical functionalities; or, there are no identical functionalities. Among the test points set under multiple function points, there are identical test points; or, there are no identical test points.

19. An electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 9.

20. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1 to 9.

21. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 9.

Images