Software testing method, device, storage medium and computer equipment

Abstract

The present invention discloses a software testing method, device, storage medium and computer equipment, which relate to the field of information technology, and mainly lies in being able to effectively test software, thereby improving the efficiency and accuracy of software testing. The method comprises: receiving a test instruction corresponding to the software to be tested, wherein the test instruction comprises identification information corresponding to the software to be tested; based on the identification information, determining the software type to which the software to be tested belongs, and constructing a test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the test template; based on the test template, obtaining various test information corresponding to the software to be tested; generating a test request form corresponding to the software to be tested according to the storage path and the various test information; and sending the test request form to the tester terminal. The present invention is applicable to testing software.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a software testing method, device, storage medium and computer equipment. Background Art

[0002] After the software is developed, it needs to be submitted to testers for software testing. Through testing, defects in some of the software's intended functions can be discovered, the software quality can be evaluated, and it can be determined whether the software meets the conditions for release.

[0003] At present, after the software development is completed, the content to be tested is usually communicated to the tester by sending an email. However, this testing method requires developers to edit the test content according to their own logic and send it to the tester. Since the content and format of the test edited by different developers vary, it may be difficult for the tester to understand the test content, resulting in multiple communications between the two parties regarding the questions about the test content, which in turn leads to low software testing efficiency. In addition, during the testing process, it is very likely that the tester will make an incorrect test due to misunderstanding of the test content, resulting in an inability to effectively test the software. Summary of the invention

[0004] The present invention provides a software testing method, device, storage medium and computer equipment, which are mainly capable of effectively testing software and improving the efficiency and accuracy of software testing.

[0005] According to a first aspect of the present invention, there is provided a software testing method, comprising:

[0006] Receiving a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested;

[0007] Based on the identification information, determine the software type to which the software to be tested belongs, and construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested;

[0008] Based on the test template, obtaining various test information corresponding to the software to be tested;

[0009] Generate a test request form corresponding to the software to be tested according to the storage path and the various test information;

[0010] The test request form is sent to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0011] According to a second aspect of the present invention, there is provided a software testing device, comprising:

[0012] A receiving unit, configured to receive a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested;

[0013] A construction unit, configured to determine the software type to which the software to be tested belongs based on the identification information, and to construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested;

[0014] An acquisition unit, configured to acquire various test information corresponding to the software to be tested based on the test template;

[0015] A generating unit, configured to generate a test request form corresponding to the software to be tested according to the storage path and the various test information;

[0016] The sending unit is used to send the test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0017] According to a third aspect of the present invention, there is provided a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0018] Receiving a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested;

[0019] Based on the identification information, determine the software type to which the software to be tested belongs, and construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested;

[0020] Based on the test template, obtaining various test information corresponding to the software to be tested;

[0021] Generate a test request form corresponding to the software to be tested according to the storage path and the various test information;

[0022] The test request form is sent to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0023] According to a fourth aspect of the present invention, there is provided a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the following steps are implemented:

[0024] Receiving a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested;

[0025] Based on the identification information, determine the software type to which the software to be tested belongs, and construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested;

[0026] Based on the test template, obtaining various test information corresponding to the software to be tested;

[0027] Generate a test request form corresponding to the software to be tested according to the storage path and the various test information;

[0028] The test request form is sent to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0029] According to a software testing method, apparatus, storage medium and computer equipment provided by the present invention, compared with the current method of conveying test content by sending emails to testers, thereby notifying testers to test software, the present invention receives test instructions corresponding to the software to be tested, and the test instructions include identification information corresponding to the software to be tested; and based on the identification information, determines the software type to which the software to be tested belongs, and constructs a test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the test template; at the same time, based on the test template, obtains various test information corresponding to the software to be tested; then generates the software to be tested according to the storage path and the various test information. The test request form corresponding to the software to be tested is finally sent to the tester terminal, so that the tester can test the software to be tested based on the test request form, thereby constructing a test template corresponding to the software type to which the software to be tested belongs, and obtaining various test information corresponding to the software to be tested based on the test template. At the same time, a test request form is generated based on the storage path and the various test information, and finally the test request form is sent to the tester for software testing. This can avoid the situation where multiple communications with testers occur due to uneven formats of test content edited by developers, thereby improving the efficiency of software testing. At the same time, it can also avoid the situation where testers misunderstand the test content and conduct incorrect tests on the software, thereby improving the accuracy of software testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0031] Figure 1 A flow chart of a software testing method provided by an embodiment of the present invention is shown;

[0032] Figure 2 Another software testing method flow chart provided by an embodiment of the present invention is shown;

[0033] Figure 3 A schematic diagram of the structure of a software testing device provided by an embodiment of the present invention is shown;

[0034] Figure 4 A schematic diagram showing the structure of another software testing device provided by an embodiment of the present invention is shown;

[0035] Figure 5 A schematic diagram of the physical structure of a computer device provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0036] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other without conflict.

[0037] At present, the method of software testing in which developers edit test contents by themselves and send them to testers via emails will result in low efficiency of software testing. In addition, it is likely that test errors will occur due to testers' misunderstanding of the test contents, resulting in low accuracy of software testing.

[0038] In order to solve the above problems, the embodiment of the present invention provides a software testing method, such as Figure 1 As shown, the method includes:

[0039] 101. Receive a test instruction corresponding to software to be tested, where the test instruction includes identification information corresponding to the software to be tested.

[0040] For the embodiment of the present invention, in order to overcome the defects of low efficiency and low accuracy of software testing in the prior art, the embodiment of the present invention constructs a test template corresponding to the software type to which the software to be tested belongs, and based on the test template, obtains various test information corresponding to the software to be tested. At the same time, a test request form is generated based on the storage path and the various test information, and finally the test request form is sent to the tester for software testing, which can avoid the situation where multiple communications with the tester occur due to the uneven format of the developer editing the test content, thereby improving the efficiency of software testing, and can also avoid the situation where the tester misunderstands the test content and performs incorrect tests on the software, thereby improving the accuracy of software testing. The embodiment of the present invention is mainly applied to the scenario of testing software, and the execution subject of the embodiment of the present invention is a device or equipment capable of testing software, which can be specifically set on the client or server side.

[0041] Specifically, the software testing system is downloaded to the client from the company's official website in advance. No installation is required. The software testing system can be opened by double-clicking directly. After opening the software testing system, the testing main interface will be displayed directly. Click the software type option in the testing main interface, and a drop-down menu corresponding to different software types will appear. Select the software type to which the software to be tested belongs in the drop-down menu to display an exclusive testing interface corresponding to the software type, and click the new test template logo at the preset position in the exclusive testing interface. At this time, the testing system will display the test template corresponding to the software type to the tester, that is, display the test template corresponding to the software to be tested to the tester, wherein the storage path corresponding to the software to be tested is displayed in the test template. Based on the test template, the tester fills in various test information corresponding to the software to be tested in the test template, generates a corresponding test form after filling in, and then sends the test form to the tester. The tester tests the software to be tested based on the test form, which can avoid multiple communications with the tester due to the uneven formats of the test content edited by the developer, thereby improving the efficiency of software testing.

[0042] 102. Based on the identification information, determine the software type to which the software to be tested belongs, and construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested.

[0043] For the embodiment of the present invention, before the tester conducts the test, the software to be tested needs to be stored in the test software library corresponding to the software type to which it belongs. Different software types correspond to different test software libraries, and different test software libraries correspond to different storage paths. After receiving the test instruction corresponding to the software to be tested and determining the identification information carried by the test instruction, based on the identification information, it is checked which type of software the software to be tested belongs to, and based on the software type, test templates corresponding to different software types are constructed, that is, the test template corresponding to the software to be tested is constructed, wherein the storage path corresponding to the software to be tested is displayed in the test template. For example, if the software to be tested is WeChat, it can be determined through the WeChat icon that WeChat belongs to social software, then a test template corresponding to the social software is constructed, and based on the test template, various test information corresponding to the software to be tested is obtained. At the same time, according to the storage path and the various test information, a test request form corresponding to the software to be tested is generated, and finally the test request form is sent to the tester, so that the tester can test the software to be tested based on the test request form, which can avoid the situation where multiple communications with the tester occur due to the uneven formats of the test content edited by the developer, thereby improving the efficiency of software testing.

[0044] 103. Based on the test template, obtain various test information corresponding to the software to be tested.

[0045] For the embodiment of the present invention, the test template includes a storage path corresponding to the software to be tested, and various test title items related to the test content. When it is necessary to obtain various test information corresponding to the software to be tested, the tester needs to fill in the corresponding test information at the corresponding position of each test title item, and generate a test request form corresponding to the software to be tested based on the storage path and the various test information. Finally, the test request form is sent to the tester's terminal. The tester downloads the software to be tested based on the storage path recorded in the test request form, and then tests the software to be tested according to the various test information. This avoids the situation where the tester misunderstands the email content due to the uneven format of the test content edited by the developer himself, and then performs an incorrect test on the software, thereby improving the accuracy of software testing.

[0046] 104. Generate a test request form corresponding to the software to be tested according to the storage path and the various test information.

[0047] For the embodiment of the present invention, after the developer has filled in various test information in the test template, he / she checks whether the various test information is filled in accurately. After checking that they are correct, he / she clicks the button with the word "Submit" in the test template interface to generate a test submission form corresponding to the software to be tested. At this time, the tester can log in to the software testing system to see the test submission form corresponding to the software to be tested, and test the software to be tested according to the storage path and various test information recorded in the test submission form. This can avoid the situation where the tester misunderstands the test content written by the developer according to his / her own logic, and is unable to effectively test the software to be tested.

[0048] 105. Send the test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0049] For the embodiments of the present invention, after generating a test submission form corresponding to the software to be tested according to the storage path and the various test information, the tester corresponding to the software to be tested logs in to the software testing system and sees the test submission forms corresponding to different software to be tested. According to the date and the corresponding tester recorded thereon, the test submission form corresponding to the tester can be found. Finally, based on the storage path and the various test information corresponding to the software to be tested recorded in the test submission form, the software to be tested is tested. This can avoid the situation where multiple communications with the tester occur due to the uneven formats of the test content edited by the developers, thereby improving the efficiency of software testing. At the same time, it can also avoid the situation where the tester misunderstands the test content and performs incorrect tests on the software, thereby improving the accuracy of software testing.

[0050] According to a software testing method provided by the present invention, compared with the current method of conveying the test content by sending an email to the tester, thereby notifying the tester to test the software, the present invention receives a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested; and based on the identification information, determines the software type to which the software to be tested belongs, and constructs a test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the test template; at the same time, based on the test template, obtains various test information corresponding to the software to be tested; and then generates a test request form corresponding to the software to be tested according to the storage path and various test information; Finally, the test request form is sent to the tester terminal so that the tester can test the software to be tested based on the test request form. A test template corresponding to the software type to which the software to be tested belongs is constructed, and based on the test template, various test information corresponding to the software to be tested is obtained. At the same time, a test request form is generated based on the storage path and the various test information, and finally the test request form is sent to the tester for software testing. This can avoid the situation where multiple communications with the tester occur due to the uneven formats of the test content edited by the developer, thereby improving the efficiency of software testing. At the same time, it can also avoid the situation where the tester misunderstands the test content and performs incorrect tests on the software, thereby improving the accuracy of software testing.

[0051] Further, in order to better illustrate the process of testing the software, as a refinement and extension of the above embodiment, the embodiment of the present invention provides another software testing method, such as Figure 2 As shown, the method includes:

[0052] 201. Receive a test instruction corresponding to the software to be tested, where the test instruction includes identification information corresponding to the software to be tested.

[0053] For the embodiment of the present invention, if it is necessary to test the software to be tested, first open the software testing system, and select the software type to which the software to be tested belongs in the main interface of the software testing system, and then click the new test template identifier to generate a test instruction corresponding to the software to be tested. Then, the software testing system determines the software type to which the software to be tested belongs according to the identification information corresponding to the software to be tested carried in the test instruction, and determines the test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the testing template, and the tester fills in various test information in the test template, and generates a test form corresponding to the software to be tested based on the storage path and the various test information, and finally sends the test form to the tester terminal, and the tester tests the software to be tested according to the content recorded in the test form.

[0054] 202. Based on the identification information, determine the software type to which the software to be tested belongs, and when the test instruction is a common-end test instruction, construct a common-end test template corresponding to the software type, wherein the common-end test template displays a storage path corresponding to the software to be tested.

[0055] Among them, the common end test instruction is a test instruction issued by a non-developer. For the embodiment of the present invention, the content of the test performed by the developer and the non-developer on the software to be tested may be different. Therefore, when the non-developer performs a test on the software to be tested, the common end test template corresponding to the software to be tested is selected. The common end test template includes the test title items for the non-developer to perform the test. Specifically, when the non-developer wants to test the software to be tested, the software test system is opened, and the software type to which the software to be tested belongs is selected in the main interface of the test system. An exclusive test main interface corresponding to the software type appears. In the exclusive test main interface, a new test template logo is clicked, and a template option interface corresponding to the software type is displayed. The template option interface includes a common mode option and a development end exclusive mode option. Selecting the common mode option will display the common end test template, wherein the common end test template displays the storage path corresponding to the software to be tested, and the storage path is the storage path corresponding to the software type to which the software to be tested belongs. The non-developer fills in the test information corresponding to each test title item based on each test title item existing in the common end test template.

[0056] 203. When the test instruction is a development-end test instruction, construct a development-end test template corresponding to the software type, wherein the development-end test template displays a storage path corresponding to the software to be tested.

[0057] The development-end test instruction is a test instruction issued by a developer. For an embodiment of the present invention, if a developer wants to test the software to be tested, the developer selects a development-end test template corresponding to the software to be tested, and the development-end test template includes a test title item for the developer to perform the test. Specifically, when the developer wants to test the software to be tested, the developer opens the software test system, selects the software type to which the software to be tested belongs in the main interface of the test system, and an exclusive test main interface corresponding to the software type appears. In the exclusive test main interface, the developer clicks on a new test template logo, and a template option interface corresponding to the software type is displayed. The template option interface includes a normal mode option and a development-end exclusive mode option. Selecting the development-end exclusive mode option displays a development-end test template, wherein the development-end test template displays a storage path corresponding to the software to be tested, and the storage path is the storage path corresponding to the software type to which the software to be tested belongs. The developer fills in various test information corresponding to each test title item based on various test title items existing in the development-end test template.

[0058] 204. Based on the common-end test template or the development-end test template, obtain various test information corresponding to the software to be tested.

[0059] For the embodiment of the present invention, after constructing the common-end test template or the development-end test template corresponding to the software to be tested, it is necessary to obtain various test information corresponding to the software to be tested based on the common-end test template or the development-end test template. Based on this, step 202 specifically includes: if the test template is the common-end test template, then obtain the corresponding product information, test project information, modification point information, test suggestion information, requirement file information, priority information, release plan information and tester information of the software to be tested; if the test template is the development-end test template, then obtain the corresponding product information, test project information, test file information, file version information, modification point information, deletion or addition of dependent file information, dependent file version information, requirement file information, priority information, release plan information and tester information of the software to be tested.

[0060] The test project information is equivalent to the title of the email we usually send, and the requirement file information refers to the development requirement file corresponding to the initial stage of the software to be tested.

[0061] Specifically, if the tester selects the common-end test template, the test title items corresponding to the common-end test template will be displayed. Each test title item includes a product title item, a test project title item, a modification point title item, a test suggestion title item, a requirement document title item, a priority title item, a release plan title item and a tester title item. The tester fills in the product information corresponding to the software to be tested, such as 360 Security Guard, in the position corresponding to the product title item, and fills in the test project information corresponding to the software to be tested, such as "need to test a certain product", in the position corresponding to the test project title item, and fills in the modification point information corresponding to the software to be tested in the position corresponding to the modification point title item, that is, the tester has modified a part of the code of the software to be tested, and fills in the modified code part to the position corresponding to the modification point title item, and in the test template Fill in the test suggestion information corresponding to the software to be tested at the position corresponding to the proposal title item, click at the position corresponding to the requirement file title item to display a computer file list, select the requirement file corresponding to the software to be tested in the file list, and the requirement file will be stored in the common end test template, click the drop-down menu option at the position corresponding to the priority title item, and various priority options will be displayed, and the priority corresponding to the software to be tested, for example, level one, will be selected from the various priority options, click the date icon at the position corresponding to the release plan title item, and a date table will be displayed, and the release date corresponding to the software to be tested will be selected in the date table, and finally click the drop-down menu icon at the position corresponding to the tester title item, and various testers will be displayed in the drop-down menu, and at this time, the tester corresponding to the software to be tested will be selected from the various testers.

[0062] Furthermore, if the tester selects the development-side test template, the various test title items corresponding to the development-side test template will be displayed. Each test title item includes a corresponding product title item, a test project title item, a test file title item, a file version title item, a modification point title item, a deletion or addition of a dependent file title item, a dependent file version title item, a requirement file title item, a priority title item, a release plan title item and a tester title item. The tester shall fill in the product information of the software to be tested, the test title information, the test file information, the requirement file information, the priority information, the release plan information and the tester information corresponding to the software to be tested in the positions corresponding to the product title item, the test project title item, the test file title item, the requirement file title item, the priority title item, the release plan title item and the tester title item, and at the same time, fill in the version corresponding to the test file in the position corresponding to the file version title item, and fill in the software modification point corresponding to the software to be tested in the position corresponding to the modification point title item. If the software to be tested has dependent files, then in the Click the drop-down menu icon in the Delete or Add Dependent File title item, and the Add option and the Delete option will be displayed in the drop-down order. If the software to be tested has dependent files, select the Add option in the drop-down order at this time, fill in the dependent files in the corresponding positions, and fill in the corresponding versions of the dependent files in the positions corresponding to the dependent file version title item. If the software to be tested has been tested before this test, and dependent files have been added to the software to be tested in the previous test process, but the software to be tested has no dependent files during the test of the software to be tested this time, then it is necessary to select Delete in the drop-down order, and fill in the dependent files and dependent file versions to be deleted in the corresponding positions. In this way, based on the common end test template or the development end test template, the corresponding test information of the software to be tested is obtained, and based on the various test information, the test submission form corresponding to the software to be tested is generated and sent to the tester terminal. Finally, the tester tests the software to be tested based on the test submission form.

[0063] 205. Generate a test request form corresponding to the software to be tested according to the storage path and the various test information.

[0064] For the embodiment of the present invention, if the test information corresponding to the common-end test template is obtained based on the common-end test template, then the common test order corresponding to the software to be tested is generated based on the storage path and the test information corresponding to the common-end test template; if the test information corresponding to the development-end test template is obtained based on the development-end test template, then the development test order corresponding to the software to be tested is generated based on the storage path and the test information corresponding to the development-end test template; the generated common test order or the development test order is displayed in the main interface of the test system; the main interface of the test system displays the various software to be tested. The test request forms corresponding to the software are arranged in chronological order in the main interface of the testing system. The longer the testing time is, the later the test request form is arranged. The test request forms in the main interface of the testing system are displayed in the form of priority, testing time, tester, testing content, current progress, test manager, release plan, etc. When the tester logs in to the testing system, he can see the test request forms displayed in the main interface of the testing system, find the test request forms corresponding to the tester based on the test manager corresponding to each test request form, and finally the tester tests the software to be tested based on the test information recorded in the test request forms.

[0065] Furthermore, after generating the test submission form, if the software to be tested is changed again and needs to be tested again, or the tester has omitted one or several test information in the previous test submission form, it is necessary to update the test submission form. Based on this, the method includes: when receiving a new test information instruction corresponding to the software to be tested, generating a test submission form details interface corresponding to the software to be tested, and based on the test submission form details interface, constructing a new test information template corresponding to the software to be tested; based on the new test information template, obtaining new modification file information, new modification point information, new test suggestion information and new requirement file information corresponding to the software to be tested; based on the new modification file information, the new modification point information, the new test suggestion information and the new requirement file information, updating the test submission form corresponding to the software to be tested.

[0066] For the embodiment of the present invention, in order to facilitate the tracing of the historical modification points corresponding to each software to be tested, the test information corresponding to the same software to be tested needs to be recorded in a test request form, so that when the test request form corresponding to the software to be tested is opened, the historical test request information corresponding to the software to be tested can be seen. Based on this, when it is necessary to add the test request information corresponding to the software to be tested, select the test request form corresponding to the software to be tested in the main interface diagram of the test request system, click on the test request form, and the test request form details interface can be displayed. The test request form details interface contains a test flow chart corresponding to the software to be tested, and the flow chart records the various stages of the software to be tested from the review before development to the project release, and displays the current status of the software to be tested through a preset mark, so as to remind the tester to arrange the test in time. At the same time, the first preset position of the test request form details interface contains the test project information, current progress information, tester information, priority information and release plan information corresponding to the software to be tested, and the second preset position of the test request form details interface contains the storage path information, tester information, test time information, modification file information, modification point information, test suggestion information, requirements corresponding to the software to be tested. The test personnel can modify the current progress information, the test personnel information, the priority information and the release plan information at the first preset position. At the same time, the third preset position in the test submission form details interface also includes a new test information mark. Click the new test information mark to display the new test information template. The new test information template includes a new modified file title item, a new modified point title item, a new test suggestion title item and a new requirement file title item. Based on the above title items, the new modified file information, the new modified point information, the new test suggestion information and the new requirement file information are filled in the corresponding positions of the above title items respectively. Finally, click the submit mark in the new test information template to update the test submission form. The updated test submission form records all historical test information. At the same time, the main interface of the test submission system shows the updated test submission form. Click the test submission form to display the updated test submission form details interface. The information at the first preset position in the updated test submission form details interface does not change, and the new test information is displayed below the original information at the second preset position.

[0067] 206. Send the test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0068] For the embodiment of the present invention, after generating the test request form corresponding to the software to be tested, the test request form needs to be sent to the tester terminal so that the tester can test the software to be tested based on the test request form. Based on this, step 204 specifically includes: generating a test notification corresponding to the software to be tested based on the test request form corresponding to the software to be tested; calling a preset communication tool interface to send the test notification to the tester terminal so that the tester can view the test request form based on the test notification and test the software to be tested.

[0069] Among them, the preset communication tool can be specifically email. Specifically, after the test request form is generated in the test request system, the test request system will generate a test notification based on the test request form, and automatically send the test notification to the tester corresponding to the software to be tested via email. Based on the email notification, the tester will log in to the software testing system, and click on the test request form in the main interface of the software testing system. Then, the tester will see the storage path and various test information corresponding to the software to be tested recorded in the test request form details interface. The tester can download the software to be tested based on the storage path recorded in the test request form details interface, and then perform the test according to the storage path recorded in the test request form details interface. The software to be tested is tested according to the recorded test information. If the tester can test the software to be tested immediately, the current status at the first preset position in the test order details interface will be set to start testing. At the same time, if the tester needs to be replaced due to other important test tasks or resignation, the tester at the first preset position can be changed to the handover tester. At the same time, the tester can also modify the release plan time according to the test progress. All information modified by the tester will be automatically notified to the tester via email, so that the tester can timely understand the current test status of the software to be tested.

[0070] Furthermore, after the tester receives the test notification and tests the software to be tested, the method also includes: obtaining a test report form corresponding to the software to be tested; when receiving a release instruction corresponding to the software to be tested, based on the release confirmation information and test conclusion information in the test report form, releasing the software to be tested.

[0071] Specifically, when the tester has finished testing the software to be tested, the current progress at the first preset position in the test details interface is set to test completion, and then the submission icon in the test details interface is clicked. At this time, the test system will automatically display a test report template, and the test report template contains a release confirmation title item and a test conclusion title item, wherein the release confirmation title item includes a general title item and a development title item, and the general title item contains subtitles such as "Is the online test data clear, and does the interface or page need to be put online first?", "Has the product or operation passed the verification?" and "Has the file signature passed, and has the version been upgraded?" Based on the test results, fill in "Yes" or "No" at the corresponding position of "Is the online test data clear, and does the interface or page need to be put online first?". If the product or operation passes the verification, then check the corresponding position of "Has the product or operation passed the verification?". If the file signature passes and the version is upgraded, then Tick ​​the corresponding position of "Whether the file signature is passed and the version is upgraded". At the same time, the development title item includes operations such as "Whether the new pop-up window needs to be whitened by 360", "Use the depends tool under XP to view file dependencies", "Overwrite installation, whether the product is normal based on functions after V3 upgrade", etc. If the software to be tested does not require the above operations, fill in the words "not required" in the corresponding position. At the same time, based on the test results, the tester fills in the test conclusion corresponding to the software to be tested in the position corresponding to the test conclusion title item. After filling in, click the submit button in the test report template to generate the test report form. At the same time, the testing system will automatically send the test report notification to the testing personnel via email. Based on the test report notification, the testing personnel check the test report form in the testing system. If the test conclusion title item in the test report form shows the words "test passed", the testing personnel can arrange the release of the software to be tested.

[0072] Furthermore, after the software to be tested is released, in order to be able to view the released software to be tested in the testing system, it is necessary to back up the released software to be tested to the testing system. Based on this, the method also includes: generating an MD5 value corresponding to the released software to be tested; and backing up the released software to be tested based on the MD5 value and software version corresponding to the software to be tested.

[0073] Specifically, after the development of each software to be tested is completed, its corresponding MD5 value will be generated. Different software to be tested corresponds to different MD5 values. After the software to be tested is released, log in to the software testing system and click the backup file icon in the main interface of the software testing system to display the backup file template. The backup file template contains a file MD5 value title item, a file version title item and an upload file title item. Fill in the MD5 value and software version corresponding to the software to be tested in the positions corresponding to the file MD5 value title item and the file version title item, and click the position corresponding to the upload file title item to display a computer file list. Select the software to be tested that needs to be uploaded in the file list. Finally, click the submit icon in the backup file template to complete the backup of the software to be tested.

[0074] According to another software testing method provided by the present invention, compared with the current method of conveying the test content by sending emails to testers, thereby notifying testers to test the software, the present invention receives test instructions corresponding to the software to be tested, and the test instructions include identification information corresponding to the software to be tested; and based on the identification information, determines the software type to which the software to be tested belongs, and constructs a test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the test template; at the same time, based on the test template, obtains various test information corresponding to the software to be tested; and then generates a test submission form corresponding to the software to be tested according to the storage path and various test information. ; Finally, the test request form is sent to the tester terminal, so that the tester can test the software to be tested based on the test request form, thereby constructing a test template corresponding to the software type to which the software to be tested belongs, and based on the test template, obtaining various test information corresponding to the software to be tested. At the same time, a test request form is generated based on the storage path and the various test information, and finally the test request form is sent to the tester for software testing. This can avoid the situation where multiple communications with the tester occur due to the uneven formats of the test content edited by the developer, thereby improving the efficiency of software testing. At the same time, it can also avoid the situation where the tester misunderstands the test content and performs incorrect tests on the software, thereby improving the accuracy of software testing.

[0075] Further, as Figure 1 The specific implementation of the present invention provides a software testing device, such as Figure 3 As shown, the device includes: a receiving unit 31, a constructing unit 32, an acquiring unit 33, a generating unit 34 and a sending unit 35.

[0076] The receiving unit 31 may be configured to receive a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested.

[0077] The construction unit 32 may be configured to determine the software type to which the software to be tested belongs based on the identification information, and to construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested.

[0078] The acquisition unit 33 may be configured to acquire various test information corresponding to the software to be tested based on the test template.

[0079] The generating unit 34 may be configured to generate a test request form corresponding to the software to be tested according to the storage path and various test information.

[0080] The sending unit 35 may be used to send the test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0081] In a specific application scenario, in order to construct a test template corresponding to the software type, such as Figure 4 As shown, the construction unit 32 can be specifically used to construct a common-end test template corresponding to the software type if the test instruction is a common-end test instruction, wherein the common-end test template displays the storage path corresponding to the software to be tested; if the test instruction is a development-end test instruction, then construct a development-end test template corresponding to the software type, wherein the development-end test template displays the storage path corresponding to the software to be tested.

[0082] In a specific application scenario, in order to obtain various test information corresponding to the software to be tested, the acquisition unit 33 can be specifically used to obtain the product information, test project information, modification point information, test suggestion information, requirement file information, priority information, release plan information and tester information corresponding to the software to be tested if the test template is the ordinary end test template; if the test template is the development end test template, then obtain the product information, test project information, test file information, file version information, modification point information, deletion or addition of dependent file information, dependent file version information, requirement file information, priority information, release plan information and tester information corresponding to the software to be tested.

[0083] In a specific application scenario, in order to update the test submission form, the device further includes: an updating unit 36.

[0084] The construction unit 32 can also be used to generate a test order details interface corresponding to the software to be tested when receiving a new test information instruction corresponding to the software to be tested, and construct a new test information template corresponding to the software to be tested based on the test order details interface.

[0085] The acquisition unit 33 may also be used to acquire, based on the newly added test information template, newly added modified file information, newly added modification point information, newly added test suggestion information and newly added requirement file information corresponding to the software to be tested.

[0086] The updating unit 36 ​​may be configured to update the test request form corresponding to the software to be tested based on the newly added modification file information, the newly added modification point information, the newly added test suggestion information and the newly added requirement file information.

[0087] In a specific application scenario, in order to send the test request form to the tester so that the tester can test the software to be tested based on the test request form, the sending unit 35 includes a generating module 351 and a sending module 352 .

[0088] The generating module 351 may be configured to generate a test notification corresponding to the software to be tested based on the test request form corresponding to the software to be tested.

[0089] The sending module 352 can be used to call a preset communication tool interface to send the test notification to the tester terminal, so that the tester can view the test request form based on the test notification and test the software to be tested.

[0090] In a specific application scenario, in order to publish the software to be tested based on the test report form, the device further includes: a publishing unit 37 .

[0091] The acquisition unit 33 may also be used to acquire a test report sheet corresponding to the software to be tested.

[0092] The release unit 37 may be configured to release the software to be tested based on the release confirmation information of the software to be tested and the test conclusion information of the software to be tested in the test report sheet when receiving the release instruction corresponding to the software to be tested.

[0093] In a specific application scenario, in order to back up the software to be tested, the device further includes: a backup unit 38 .

[0094] The generating unit 34 may also be used to generate an MD5 value corresponding to the released software to be tested.

[0095] The backup unit 38 may be used to back up the released software to be tested based on the MD5 value and software version corresponding to the software to be tested.

[0096] It should be noted that for other corresponding descriptions of the functional modules involved in the software testing device provided in the embodiment of the present invention, reference can be made to Figure 1 The corresponding description of the method shown will not be repeated here.

[0097] Based on the above Figure 1 The method shown, accordingly, an embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the following steps are implemented: receiving a test instruction corresponding to the software to be tested, the test instruction including identification information corresponding to the software to be tested; based on the identification information, determining the software type to which the software to be tested belongs, and constructing a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested; based on the test template, obtaining various test information corresponding to the software to be tested; generating a test request form corresponding to the software to be tested according to the storage path and the various test information; and sending the test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0098] Based on the above Figure 1 The method shown and Figure 3 The embodiment of the device shown in the figure, the embodiment of the present invention also provides a physical structure diagram of a computer device, such as Figure 5 As shown, the computer device includes: a processor 41, a memory 42, and a computer program stored in the memory 42 and executable on the processor, wherein the memory 42 and the processor 41 are both arranged on a bus 43, and when the processor 41 executes the program, the following steps are implemented: receiving a test instruction corresponding to the software to be tested, the test instruction including identification information corresponding to the software to be tested; based on the identification information, determining the software type to which the software to be tested belongs, and constructing a test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the test template; based on the test template, obtaining various test information corresponding to the software to be tested; generating a test request form corresponding to the software to be tested according to the storage path and the various test information; and sending the test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

[0099] According to the technical solution of the present invention, the present invention receives a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested; determines the software type to which the software to be tested belongs based on the identification information, and constructs a test template corresponding to the software type, wherein the storage path corresponding to the software to be tested is displayed in the test template; at the same time, based on the test template, obtains various test information corresponding to the software to be tested; then generates a test request form corresponding to the software to be tested according to the storage path and the various test information; and finally sends the test request form to the tester terminal so that the tester tests the software to be tested based on the test request form. Thus, by constructing a test template corresponding to the software type to which the software to be tested belongs, and based on the test template, obtains various test information corresponding to the software to be tested, at the same time, generates a test request form based on the storage path and the various test information, and finally sends the test request form to the tester for software testing, the situation that multiple communications with the tester occur due to uneven formats of the test content edited by the developer is avoided, the efficiency of software testing is improved, and the situation that the tester performs incorrect tests on the software due to misunderstanding of the test content is avoided, the accuracy of software testing is improved.

[0100] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0101] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A software testing method, characterized in that: include: Receiving a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested; Based on the identification information, determine the software type to which the software to be tested belongs, and construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested; Based on the test template, obtaining various test information corresponding to the software to be tested; Generate a test request form corresponding to the software to be tested according to the storage path and the various test information; When receiving a new test information instruction corresponding to the software to be tested, generating a test order details interface corresponding to the software to be tested, and constructing a new test information template corresponding to the software to be tested based on the test order details interface; Based on the newly added test information template, obtain the newly added modification file information, newly added modification point information, newly added test suggestion information and newly added requirement file information corresponding to the software to be tested; Based on the newly added modification file information, the newly added modification point information, the newly added test suggestion information and the newly added requirement file information, updating the test request form corresponding to the software to be tested; The updated test request form is sent to the tester terminal so that the tester can test the software to be tested based on the test request form.

2. The method according to claim 1, characterized in that: The constructing of a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested, includes: If the test instruction is a common end test instruction, constructing a common end test template corresponding to the software type, wherein the common end test template displays a storage path corresponding to the software to be tested; If the test instruction is a development-end test instruction, a development-end test template corresponding to the software type is constructed, wherein the development-end test template displays a storage path corresponding to the software to be tested.

3. The method according to claim 2, characterized in that The obtaining, based on the test template, various test information corresponding to the software to be tested includes: If the test template is the common end test template, obtain the product information, test project information, modification point information, test suggestion information, requirement file information, priority information, release plan information and tester information corresponding to the software to be tested; If the test template is the development-end test template, then obtain the product information, test project information, test file information, file version information, modification point information, deletion or addition of dependent file information, dependent file version information, requirement file information, priority information, release plan information and tester information corresponding to the software to be tested.

4. The method according to claim 1, characterized in that The step of sending the updated test request form to a tester terminal so that the tester can test the software to be tested based on the test request form includes: Based on the test request form corresponding to the software to be tested, generating a test notification corresponding to the software to be tested; The preset communication tool interface is called to send the test notification to the tester terminal, so that the tester can view the test request form based on the test notification and test the software to be tested.

5. The method according to claim 4, characterized in that After sending the test request form to the tester terminal, the method further includes: Obtaining a test report sheet corresponding to the software to be tested; When a release instruction corresponding to the software to be tested is received, the software to be tested is released based on the release confirmation information and the test conclusion information in the test report.

6. The method according to claim 5, characterized in that After the software to be tested is released based on the release confirmation information and the test conclusion information in the test report, the method further includes: Generate the MD5 value corresponding to the released software to be tested; The released software to be tested is backed up based on the MD5 value and software version corresponding to the software to be tested.

7. A software testing device, characterized in that: include: A receiving unit, configured to receive a test instruction corresponding to the software to be tested, wherein the test instruction includes identification information corresponding to the software to be tested; A construction unit, configured to determine the software type to which the software to be tested belongs based on the identification information, and to construct a test template corresponding to the software type, wherein the test template displays a storage path corresponding to the software to be tested; An acquisition unit, configured to acquire various test information corresponding to the software to be tested based on the test template; A generating unit, configured to generate a test submission form corresponding to the software to be tested according to the storage path and the various test information; when receiving a new test information instruction corresponding to the software to be tested, generate a test submission form details interface corresponding to the software to be tested, and construct a new test information template corresponding to the software to be tested based on the test submission form details interface; based on the new test information template, obtain new modification file information, new modification point information, new test suggestion information and new requirement file information corresponding to the software to be tested; based on the new modification file information, the new modification point information, the new test suggestion information and the new requirement file information, update the test submission form corresponding to the software to be tested; The sending unit is used to send the updated test request form to the tester terminal so that the tester can test the software to be tested based on the test request form.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images