TW201719410A - Software testing system - Google Patents

Abstract

A software testing system, which used for testing a tested software, is provided. The system comprises a planning management module and a testing module. The planning management module plans a test case and a test set related to the tested software. The testing module obtains the test case and the test set from the planning management module to test defects of the tested software. The testing module integrates a screenshot unit, a video recording unit and an audio recording unit that perform screenshot, video recording or audio recording for the tested software to produce defect information, so as to modify the defects of the tested software based on the defect information. Thereby, the invention can enhance management effectiveness, testing efficiency and quality of the tested software.

Description

Software test system

The present invention relates to a software testing system technology, and more particularly to a software testing system that can improve testing efficiency.

At present, when testing the software to be tested, the tester usually needs to set up multiple sets of test tools to complete the test work, and the test tools include a screenshot tool (such as Word editing software), a video recording tool, a recording tool, and a file recording tool (such as Excel). Trial balance), email, etc.

However, in addition to the large number of test tools, the tester has to spend a lot of time to repeatedly switch between the test tools or their screens to take screenshots of the defects of the software to be tested. Video recording, recording, recording, email notification, etc., make the testing work of the tester often interrupted, so that it is not easy to focus on the testing work of the software to be tested, and the test software of the software to be tested is not efficient, so it is difficult to produce Good quality software.

What's more, often due to the urgency of the test schedule and the limited resources of the test, the tester changed the test procedure of the software to be tested by means of "word-by-word". Although this method can quickly correct the problem of the software to be tested, For a long time, the source of the problem with the software to be tested cannot accumulate enough information for future reference. Therefore, it is difficult to improve the management performance of the software to be tested, and the waste of test manpower and the heavy work of the test work are hard to improve. Test the quality of the software.

Therefore, how to overcome the problems of the prior art mentioned above has become a problem that is currently being solved.

The invention provides a software testing system for testing a software to be tested, the system comprising: a planning management module, which is a test case and a test set for the software to be tested; and a test module, which is managed by the plan. The test case and the test set are obtained in the module, and the defect of the software to be tested is tested according to the test case and the test set, and the test module is integrated with a screenshot unit, a video unit and a recording unit, to be tested The defect of the software is subjected to screenshot, video recording or recording to generate defect information, and the defect of the software to be tested is corrected according to the defect information.

The planning management module can plan the test requirements and test defects of the software to be tested to transmit the test defect form to the test module, and the test module loads the content and the attachment of the defect information into the test module. Test the defect in the table.

The software test system can include an integration platform that connects the planning management module and the test module to integrate or exchange information of the planning management module and the test module through the integration platform. Moreover, the integration platform may have a database for importing, exporting or storing the content of the planning management module and the test module, the form template or the defect information through the database.

The planning management module may have a downloading unit for downloading, by the downloading unit, a template template of at least one of a test requirement, a test case, a test defect, and a test set of the software to be tested in the integrated platform to the planning management mode. group.

The planning management module may have an importing unit for importing information about at least one of the testing requirements, test cases, test defects and test sets of the software to be tested in the planning management module through the importing unit to The integration platform.

The planning management module may have a exporting unit for reversing information about at least one of the testing requirements, test cases, test defects and test sets of the software to be tested in the integrated platform to the plan through the exporting unit Management module.

The planning management module may have a report generating unit to generate a test report or test dashboard for the software to be tested through the report generating unit.

The test module can have a test set list to provide test information, test history, test steps or step execution status of the test software through the test set list. The test module may also have a defect list to provide defect information or defect status statistics of the software to be tested through the defect list.

The screenshot unit, the video unit and the recording unit of the test module are located on the floating toolbar.

The screenshot unit of the test module can capture a picture about the defect of the software to be tested, and mark the picture on the picture to generate an image file of the defect information, and then the test module transmits the picture file to the plan. In the management module, the defect of the software to be tested is corrected according to the image file.

The video unit of the test module can record a picture of the occurrence process of the defect of the software to be tested to generate a video file of the defect information, and then the test module transmits the video file to the planning management module, Correcting the defect of the software to be tested according to the video file.

When the video unit of the test module records the screen of the software to be tested, the recording unit of the test module can synchronously record the description sound about the defect of the software to be tested, and combine the description sound into the video file to generate The video file of the defect information is transmitted by the test module to the planning management module, and the defect of the software to be tested is corrected according to the video file.

The software testing system can include a transceiver module for transmitting defect information of the software to be tested to a predetermined electronic mailbox through the transceiver module, and correcting defects of the software to be tested according to the defect information.

It can be seen from the above that the software test system of the present invention can plan the test cases and test sets of the software to be tested through the planning management module, and integrate the screenshot, video and recording unit through the test module to retrieve the defect information of the software to be tested. And further correcting the defect of the software to be tested according to the defect information. Thereby, the invention can improve the management performance, test efficiency and quality of the software to be tested.

At the same time, on the planning management side, the planning management module can be used by the planning management personnel to plan the testing requirements, test cases, test defects and test sets of the software to be tested, so that the test personnel can quickly understand the test workload, execution progress and effectiveness. Eli allocate test resources and meet the requirements of the test plan.

Moreover, on the software test surface, the test module can provide an integrated tool for reducing test operations (All in One), so that the tester can get rid of the test techniques such as screenshots, videos, recordings, and file records. And his paintings The problem of repeated switching between faces is to replace multiple sets of test tools of the prior art through a set of test modules of the present invention.

In addition, in the communication aspect of the test execution, the planning management module can serve as a communication platform between the planning management personnel and the testing personnel, and the testing personnel transmits the defect information of the software to be tested through the testing module. The planning management personnel can immediately obtain the defect information (such as image file, video file, video file or text file) of the software to be tested through the planning management module, the integration platform or the email, which is beneficial to quickly correct the software to be tested. defect.

1‧‧‧Software Test System

10‧‧‧ Planning Management Module

11‧‧‧Test requirements

11a, 11b, 11c‧‧‧ options

12‧‧‧ test cases

12a, 12b, 12c‧‧‧ options

13‧‧‧Test defects

13a, 13b, 13c‧‧‧ options

14‧‧‧Test set

14a, 14b, 14c‧‧‧ options

15‧‧‧Download unit

16‧‧‧Importing unit

17‧‧‧Exporting unit

18‧‧‧Report generating unit

181‧‧‧ test report

181a, 182a, 183‧‧‧ options

182‧‧‧Test Dashboard

182b‧‧‧Test job logbook

182c‧‧‧Defect type distribution map

182d‧‧‧Defect status map

19a, 19b‧‧‧ windows

20‧‧‧Test module

20a, 20b, 20c‧‧‧ options

21‧‧‧Screen unit

211‧‧‧ picture file

212‧‧‧ mark

213‧‧‧Border

22‧‧‧Video unit

22a, 22b, 23a‧‧‧ options

221‧‧‧ video files

222‧‧‧ audio and video files

23‧‧‧Recording unit

24‧‧‧Defect information

241‧‧‧Content

242‧‧‧Annex

243‧‧‧Annex information

25‧‧‧Test Set List

251‧‧‧Test Information

252‧‧‧Test history

253‧‧‧Test steps

254‧‧‧Step execution status

26‧‧‧Defect list

26a‧‧‧Project

261‧‧‧Defect status statistics

27, 271‧‧‧ Floating Toolbar

28‧‧‧ Test results

29‧‧‧Window

30‧‧‧ Integration platform

301‧‧‧Database

40‧‧‧ transceiver module

401‧‧‧Email

50‧‧‧Software to be tested

501‧‧‧ Defects

502‧‧‧ screen

60‧‧‧ storage module

1 is a block diagram showing a software testing system of the present invention; and FIGS. 2A to 2I are schematic diagrams showing an embodiment of a planning management module of the software testing system of the present invention; and FIGS. 3A to 3H. A schematic diagram of an embodiment of a test module of the software test system of the present invention, wherein the 3F-1 and 3F-2 diagrams show different embodiments of the start recording unit, and the 3G-1 and 3G-2 diagrams are shown. A schematic diagram showing different embodiments of defect information input.

The other embodiments of the present invention will be readily understood by those skilled in the art from this disclosure.

It is to be understood that the structure, the proportions, the size, and the like of the present invention are intended to be used in conjunction with the disclosure of the specification, and are not intended to limit the invention. The qualifications are not technically meaningful, the modification or proportion of any structure Changes in the relationship or the size of the relationship should be within the scope of the technical contents disclosed in the present invention without affecting the effects and the achievable effects of the present invention.

In the meantime, the words "a", "module" and "unit" as used in the specification are merely for convenience of description, and are not intended to limit the scope of the invention, and the relative relationship changes. Or, if it is not specifically changed, it is considered to be within the scope of the invention. Also, the term "connected" as used in this specification may denote a coupling, an electrical connection, a signal connection, a wired connection, a wireless connection, a direct connection or an indirect connection.

1 is a block diagram showing a software testing system 1 of the present invention. As shown in the figure, the software testing system 1 is used to test a software to be tested 50 (such as a software program or a web page), and mainly includes a planning management module 10 and a testing module 20.

The planning management module 10 can be a file recording software (such as Excel AddIn), an editing software, a planning management webpage, or a planning management platform. The testing module 20 can be a test software or a test program. The planning management module 10 and the testing module 20 can be respectively installed in the electronic device of the planning management personnel and the electronic device (not shown) of the testing personnel. The planning management personnel can be planning personnel, management personnel, and development. The person or the modified person, etc., the electronic device can be a server, a computer or a mobile device or the like. However, the invention is not limited thereto.

The planning management module 10 can plan a test case 12 and a test set 14 for the software 50 to be tested. The test module 20 can obtain the test case 12 and the test set directly or indirectly from the planning management module 10. 14. Defect 501 of the software to be tested 50 is tested according to the test case 12 and the test set 14. At the same time, the test module 20 can integrate the screenshot unit 21, the video unit 22 and the recording unit 23 for the tester to take a screenshot, video or record the defect 501 of the software to be tested 50 to generate defect information 24, and the test The module 20 can transmit the defect information 24 to the planning management module 10, and the planning management personnel can correct the defect 501 of the software to be tested 50 according to the defect information 24 in the planning management module 10. However, in other embodiments, the planning manager may also modify the defect 501 of the software to be tested 50 according to the defect information 24 in the integration platform 30 or the email 401 described below.

The planning management module 10 can also plan the test requirement 11 and the test defect 13 of the software to be tested 50 to transmit the table of the test defect 13 to the test module 20, and the test module 20 can provide the defect to the test module 20 The content 241 and the attachment 242 of the information 24 are loaded into the table of the test defect 13, wherein the attachment 242 can be the picture file 211, the video file 221, the video file 222 or the text file of the defect information 24.

The software testing system 1 can include an integration platform 30 that can be connected to an electronic device having the planning management module 10 and another electronic device having the testing module 20 via a wired network, a wireless network, or the like. The information of the planning management module 10 and the testing module 20 is integrated or exchanged through the integration platform 30.

The integration platform 30 can be a server or a computer having a database 301 for importing, exporting or storing the content, form template or defect information of the planning management module 10 and the testing module 20 through the database 301. Wait, And the planning manager can correct the defect 501 of the software to be tested 50 through the defect information 24 in the integration platform 30. The server can be a data server, a web server, a cloud server or a mail server.

2A to 2I are schematic views showing an embodiment of the planning management module 10 of the software testing system 1 of the present invention.

As shown in FIG. 2A and FIG. 1 above, the planning management module 10 may have a downloading unit 15 for transmitting the testing requirement 11 of the software platform 50 to be tested in the integration platform 30 through the downloading unit 15 ( A table template of at least one of option 11a), test case 12 (option 12a), test defect 13 (option 13a), and test set 14 (option 14a) is downloaded to the plan management module 10.

The planning management module 10 can have an import unit 16 for testing the test requirement 11 (option 11b) and the test case 12 of the software 50 to be tested in the planning management module 10 through the import unit 16 ( Information of at least one of option 12b), test defect 13 (option 13b) and test set 14 (option 14b) is imported into the integration platform 30.

The planning management module 10 may have an export unit 17 for transmitting the test requirement 11 (option 11c) and the test case 12 (option 12c) of the software 50 to be tested in the integration platform 30 through the export unit 17. The information of at least one of the test defect 13 (option 13c) and the test set 14 (option 14c) is exported to the plan management module 10.

For example, as shown in FIG. 2A and FIG. 2B, the plan manager can select the option 11a "test requirement form" of the download unit 15 of FIG. 2B, and the domain list from the window 19a (Domain List). List with the project In the (Project List), the option "TEST" and the option "Test_Claire" are sequentially selected, and the option "OK" is selected from the window 19a, and the table of the test request 11 in the integration platform 30 can be obtained through the download unit 15. The template is downloaded to the planning management module 10.

Moreover, as shown in FIG. 2A and FIG. 1 above, the planning manager can input the information of the test requirement 11 from the form template of the test requirement 11, such as a storage path, a requirement number, a demand name, a requirement description, and a priority. Level or analyst, etc. Then, the tester can select option 11b "Test Requirements" of the import unit 16 of FIG. 2A to transmit the information about the test requirement 11 of the software 50 to be tested in the planning management module 10 through the import unit 16. Import into the integration platform 30.

As shown in FIG. 2C and FIG. 1 above, the plan manager can select the option 11c "test requirement" of the export unit 17 of FIG. 2A to communicate the relevant information in the integration platform 30 through the export unit 17. The information of the test requirement 11 of the test software 50 is sent to the plan management module 10. Then, the planning manager can modify or add the information of the test requirement 11, but cannot delete the original information of the test requirement 11.

As shown in FIG. 2D and FIG. 1 above, the planning manager may select option 12c "test case" of the exporting unit 17 of FIG. 2A to transmit the relevant information in the integrated platform 30 through the exporting unit 17. The information of the test case 12 of the test software 50 is sent out to the form of the plan management module 10. The information of the test case 12 may include test requirements, storage path, case number, case name, initial conditions, test steps, input data or expected results.

As shown in FIG. 2E and FIG. 1 above, the plan manager can select the option 13c of the export unit 17 to “export Defect” to transmit the software to be tested in the integration platform 30 through the export unit 17. The defect information 24 of the test defect 13 of 50 is remitted to the form of the plan management module 10. The defect information 24 of the test defect 13 may include a defect identification code (Defect ID), a summary, a description, a problem classification, a severity level, a priority level, a status, a tester, a test date, or a developer, etc., and may include The image file 211, the video file 221, the video file 222, or the text file of the software to be tested 50 is attached 242.

As shown in FIG. 2F and FIG. 1 above, the planning manager may first select the option 14a of the downloading unit 15 "Download TestSet Form" to download the software 50 to be tested in the integration platform 30 through the downloading unit 15. The form template of the test set 14 is downloaded to the planning management module 10. Then, the planning manager can input the contents of the test set 14 in the form template of the test set 14, such as a storage path, a test set name, a startup video, or a test case. Then, the planning manager can select the option 14b of the importing unit 16 to "import TestSet" to generate the window 19b, and enter the domain (Project) and the project name (Project name) in the window 19b, and then from the window The option "OK" is selected in 19b, and the contents of the test set 14 can be imported into the integration platform 30 through the import unit 16.

As shown in FIG. 2G and FIG. 1A to FIG. 2A above, the planning management module 10 may have a report generating unit 18 to generate a test report about the software 50 to be tested through the report generating unit 18. . For example, the planning manager may select the option of report generation unit 18 of Figure 2A. 181a "Test Report" to generate information on test report 181 of Figure 2G, such as case number, case name, initial condition, test procedure, input data, expected result, test date, execution status or attachment 242.

As shown in FIGS. 2H to 2I and FIG. 1 to FIG. 2A above, the report generating unit 18 can also generate a test instrument panel 182 relating to the software 50 to be tested. For example, the planning manager can select the option 182a "Test Dashboard" of the report generating unit 18 of FIG. 2A, and select and display the test job logbook 182b of the software 50 to be tested from the option 182a "Test Dashboard". (Fig. 2H), defect trend growth map, defect type distribution map 182c (Fig. 2I), defect state distribution map 182d (Fig. 2I), defect severity map, or coverage rate graph.

Further, in the above FIGS. 1 and 2A, the report generation unit 18 may have the function of a case transfer test set (option 183) to convert the test case 12 into the test set 14.

3A to 3H are schematic views showing an embodiment of the test module 20 of the software test system 1 of the present invention.

As shown in FIG. 3A and FIG. 1 above, the tester can input the address, the user name (UserName) and the password (Password) on the window 29 of the test module 20, and select option 20a "Connect". The test module 20 is connected to the integration platform 30. At the same time, the tester can input the domain (Project), Project, and select "Setup Time" and option 20b "Login" to log in to the test module 20.

As shown in Figures 3B to 3C and Figure 1 above, the test module 20 may have a test set 25 (Test Lab) 25 to provide test information (Test Info) 251, test run Info 252, and test step 253 of the test software 50 through the test set list 25. Or step execution Info (Step Run Info) 254. Moreover, the test module 20 can also have a defect list 26 to provide defect information 24 or defect status statistics 261 of the software to be tested 50 through the defect list 26. For example, the tester can select item 26a of the defect list 26 to view a summary of the defect information 24, a defect type, a severity level, or a priority.

As shown in FIG. 3D and FIG. 1 above, the test set list 25 of the 3D map integrates the information of the test case 12 of the 2D chart and the test set 14 of the 2F chart. When preparing the test software 50 to be tested, the tester can select the test case 12 of the test software 50 in the test set list 25 (test set 14), for example, [97] import test case, [61] login, [62] Export test case _All Time, etc., and select option 20c of test module 20 to generate floating tool column 27 (or floating window). The floating tool row 27 can be zoomed to a smaller or predetermined size and can be moved to a suitable position of a display interface (such as a screen of an electronic device) to reduce the space occupying the display interface, so that the tester can interactively view the test. Software 50 and related information.

As shown in FIG. 3E and FIG. 1 above, the screenshot unit 21, the video unit 22, and the recording unit 23 (FIG. 3F-1) of the test module 20 are located on the floating tool row 27. The tester can capture the picture 502 (such as the square frame 213) of the defect 501 of the software to be tested 50 through the screenshot unit 21 to generate the image file 211 of the defect information 24, and then the test module. The image file 211 is transmitted to the planning management module 10 in the manner of the attachment 242, and the planning management personnel corrects the defect 501 of the software to be tested 50 according to the image file 211. Moreover, the screenshot unit 21 can have another floating tool column 271, and the tester can use the floating tool column 271 to mark the screen 502 of the defect 501 of the software to be tested 50 to generate a picture with the symbol 212. File 211, wherein the symbol 212 can be a pattern, a symbol, a text, or the like.

As shown in FIG. 3F-1, FIG. 3F-2 and FIG. 1 above, the video unit 22 of the test module 20 can be used by the tester to record the occurrence of the defect 501 of the software 50 to be tested in FIG. 3E. The screen 502 of the process is used to generate the video file 221 of the defect information 24, and the test module 20 transmits the video file 221 to the planning management module 10 in the manner of the accessory 242, for the planning management personnel to The video file 221 corrects the defect 501 of the software to be tested 50.

In addition, when the video unit 22 of the test module 20 records the screen 502 of the software to be tested 50, the recording unit 23 of the test module 20 can be used by the tester to simultaneously record the software 50 to be tested in FIG. 3E. Describe the sound of the defect 501, and combine the description sound into the video file 221 to generate the video file 222, and then transmit the video file 222 to the planning management module 10 by the test module 20 in the manner of the accessory 242. And the planning management personnel corrects the defect 501 of the software to be tested 50 according to the video file 222.

For example, in the 3F-1 diagram, the tester can select the option 22a "full screen" in the recording unit 22 to record the entire screen 502 of the software to be tested 50, and select option 23a "to start recording simultaneously. Start The recording unit 23 synchronously records the explanatory sound of the defect 501 of the software to be tested 50, thereby generating the video file 222. Alternatively, in the 3F-2 figure, the tester can select the option 22b "specified range" in the recording unit 22 to record a part of the screen 502 of the software to be tested 50, and select option 23a "Start recording simultaneously". The recording unit 23 is activated to synchronously record the explanatory sound of the defect 501 of the software to be tested 50, thereby generating the video file 222. However, in other embodiments, the present invention can also separately activate the video recording unit 22 to record the video file 221, and separately activate the recording unit 23 to perform recording to generate a recording file.

As shown in FIG. 3G-1, FIG. 3G-2 and FIG. 1 above, after the picture file 211, the video file 221 or the video file 222 is completed, the test module 20 generates a defect related to the software 50 to be tested. a form of information 24 for the tester to input the content 241 of the defect information 24 of the software to be tested 50 into the form of the defect information 24, and the defect of the 3G-1 map (or the 3G-2 map) The content 241 and the attachment 242 of the information 24 are transmitted to the defect information 24 of the planning management module 10 of the above FIG. 2E. For example, the defect information 24 of the 3G-1 map (or the 3G-2 map) includes an Assigned To, a Defect Type, a Severity, a Priority, and a Description. Or attachments and other fields, and the fields correspond to the fields of the developer, problem classification, severity level, priority level, description or attachment 242 of the above FIG. 2E, respectively.

As shown in FIG. 3H and FIG. 1 above, the tester can select the attachment 242 such as the picture file 211, the video file 221 or the video file 222 from the storage module 60 (such as a computer disk) of the electronic device, and then View this attachment 242 The attachment information 243, such as an attachment name, a size, a modified time, etc., is transmitted to the planning management module 10 through the test module 20 for the The planning manager corrects the defect 501 of the software to be tested 50 according to the attachment 242.

In addition, as shown in the above FIG. 3E and FIG. 3H, the tester can select the test result 28 of the software to be tested 50 from the floating tool row 27, such as No Run, Passed, and Failed. (Failed), Not Completed, or blocked.

In addition, in the above-mentioned first figure, the software testing system 1 includes a transceiver module 40, and the transceiver module 40 can transmit the defect information 24 of the software 50 to be tested to the email 401 directly or through the integration platform 30. In the e-mail box of the predetermined (such as the planning manager), the planning manager can correct the defect 501 of the software to be tested 50 according to the defect information 24 in the email 401. The email 401 may include the content 241 and the attachment 242 of the defect information 24 of the software to be tested 50, and the attachment 242 may be the image file 211, the video file 221, the video file 222, or the text file of the defect information 24.

It can be seen from the above that the software test system of the present invention can plan the test cases and test sets of the software to be tested through the planning management module, and integrate the screenshot, video and recording unit through the test module to retrieve the defect information of the software to be tested. And further correcting the defect of the software to be tested according to the defect information. Thereby, the invention can improve the management performance, test efficiency and quality of the software to be tested.

At the same time, on the planning management surface, the planning management module can be used by the planning management personnel to plan the testing requirements, test cases, and test defects of the software to be tested. With the test set, the tester can quickly understand the test workload, execution progress and effectiveness to facilitate the deployment of test resources and meet the requirements of the test plan.

Moreover, on the software test surface, the test module can provide an integrated tool for reducing test operations (All in One), so that the tester can get rid of the test techniques such as screenshots, videos, recordings, and file records. And the trouble of repeated switching between the screens and the multiple test tools of the prior art are replaced by a set of test modules of the present invention.

In addition, in the communication aspect of the test execution, the planning management module can serve as a communication platform between the planning management personnel and the testing personnel, and the testing personnel transmits the defect information of the software to be tested through the testing module. The planning management personnel can immediately obtain the defect information (such as image file, video file, video file or text file) of the software to be tested through the planning management module, the integration platform or the email, which is beneficial to quickly correct the software to be tested. defect.

The above-described embodiments are merely illustrative of the principles, features, and effects of the present invention, and are not intended to limit the scope of the present invention. Any person skilled in the art can practice the above without departing from the spirit and scope of the present invention. The examples are modified and altered. Any equivalent changes and modifications made by the disclosure of the present invention should be covered by the scope of the invention. Therefore, the scope of protection of the present invention should be as set forth in the scope of the patent application.

1‧‧‧Software Test System

10‧‧‧ Planning Management Module

11‧‧‧Test requirements

12‧‧‧ test cases

13‧‧‧Test defects

14‧‧‧Test set

15‧‧‧Download unit

16‧‧‧Importing unit

17‧‧‧Exporting unit

18‧‧‧Report generating unit

181‧‧‧ test report

182‧‧‧Test Dashboard

20‧‧‧Test module

21‧‧‧Screen unit

211‧‧‧ picture file

212‧‧‧ mark

22‧‧‧Video unit

221‧‧‧ video files

222‧‧‧ audio and video files

23‧‧‧Recording unit

24‧‧‧Defect information

241‧‧‧Content

242‧‧‧Annex

25‧‧‧Test Set List

26‧‧‧Defect list

30‧‧‧ Integration platform

301‧‧‧Database

40‧‧‧ transceiver module

401‧‧‧Email

50‧‧‧Software to be tested

501‧‧‧ Defects

Claims (10)

A software testing system for testing a software to be tested, the system comprising: a planning management module, which is a test case and a test set for the software to be tested; and a test module from the planning management module Obtaining the test case and the test set to test the defect of the software to be tested according to the test case and the test set, wherein the test module integrates a screenshot unit, a video unit and a recording unit to the software to be tested The defect is subjected to screenshot, video recording or recording to generate defect information, and the defect of the software to be tested is corrected according to the defect information. The software testing system of claim 1, wherein the planning management module further plans a test requirement and a test defect of the software to be tested, so as to transmit the test defect form to the test module, The test module loads the content and the attachment of the defect information into the table of the test defect. The software testing system as described in claim 1 further includes an integration platform that connects the planning management module and the testing module to integrate or exchange the planning management module and the testing module through the integration platform. Information. The software testing system of claim 3, wherein the planning management module has a downloading unit, through the downloading unit, the testing requirements and test items of the software to be tested in the integrated platform. A sample form of at least one of the case, the test defect, and the test set is downloaded to the plan management module. The software testing system of claim 3, wherein the planning management module has an importing unit or a sending unit, and the planning management module is related to the software to be tested through the importing unit. The information of at least one of the test requirements, the test cases, the test defects and the test set is imported into the integrated platform, or the test requirements, test cases, test defects and the test defects of the test software in the integrated platform are Information of at least one of the test sets is exported to the planning management module. The software test system of claim 1, wherein the test module further has a test set list to provide test information, test history, test steps or step execution status of the test software through the test set list. . The software testing system of claim 1, wherein the testing module further has a defect list to provide defect information or defect status statistics of the software to be tested through the defect list. The software testing system of claim 1, wherein the screenshot unit of the test module captures a picture about the defect of the software to be tested, and marks the screen to generate a picture of the defect information. And the test module transmits the image file to the planning management module, and corrects the defect of the software to be tested according to the image file. The software testing system of claim 1, wherein the video unit of the test module records a defect related to the software to be tested. The screen of the occurrence process is used to generate a video file of the defect information, and the test module transmits the video file to the planning management module, and the defect of the software to be tested is corrected according to the video file. The software testing system of claim 9, wherein when the video unit of the test module records the screen of the software to be tested, the recording unit of the test module simultaneously records the defect of the software to be tested. Describe a sound, and combine the description sound into the video file to generate a video file of the defect information, and then the test module transmits the video file to the planning management module, and correct the to-be-test according to the audio file Defects in software.