CN111352839B - Problem investigation method and device for software system - Google Patents

Problem investigation method and device for software system Download PDF

Info

Publication number
CN111352839B
CN111352839B CN202010127831.0A CN202010127831A CN111352839B CN 111352839 B CN111352839 B CN 111352839B CN 202010127831 A CN202010127831 A CN 202010127831A CN 111352839 B CN111352839 B CN 111352839B
Authority
CN
China
Prior art keywords
test case
smoking
test
category attribute
smoking test
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010127831.0A
Other languages
Chinese (zh)
Other versions
CN111352839A (en
Inventor
吴利华
赵振标
曾旭峰
张成明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202010127831.0A priority Critical patent/CN111352839B/en
Publication of CN111352839A publication Critical patent/CN111352839A/en
Application granted granted Critical
Publication of CN111352839B publication Critical patent/CN111352839B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites

Abstract

The application provides a problem investigation method and device of a software system, wherein the method comprises the following steps: testing a smoking test case of a software system to obtain a test result of the smoking test case; if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset; obtaining processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information; and prompting the test failure of the smoking test case according to the processing role information. The device is used for executing the method. The problem investigation method and device for the software system provided by the embodiment of the application improve the accuracy of information prompt.

Description

Problem investigation method and device for software system
Technical Field
The application relates to the technical field of software testing, in particular to a problem investigation method and device for a software system.
Background
With the application of information technology in various industries, software systems are widely applied in the fields of finance, government affairs, communication, civil aviation and the like.
The software system is an organic combination of hundreds of application systems, and the complexity of the whole software system rises with the development of the breadth and the depth of the software system into geometric progression. Before a software system is on line, a strict test must be passed, the effective development of the test depends on the efficient availability of research and development test environments, however, in a complex system scene, the availability of the environment depends on factors such as application version quality, application configuration correctness, application parameter data completeness, infrastructure stability and the like, and the software system needs to work in a software organization to involve cooperation of multiple departments, multiple teams and multiple roles even multiple regional organizations. In the process of software system testing, a corresponding manual or automatic detection mechanism is established for the software environment problem, but when the problem occurs, the responsibility is not clear, so that the problem is circulated and withheld in a plurality of roles, the problem cannot be effectively and timely solved, and the delivery of the software product is affected.
Disclosure of Invention
Aiming at the problems in the prior art, the embodiment of the application provides a problem checking method of a software system, which can at least partially solve the problems in the prior art.
In one aspect, the present application provides a method for troubleshooting a software system, including:
testing a smoking test case of a software system to obtain a test result of the smoking test case;
if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset;
obtaining processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information;
and prompting the test failure of the smoking test case according to the processing role information.
In another aspect, the present application provides a problem-checking apparatus for a software system, including:
the test unit is used for testing the smoking test case of the software system and obtaining the test result of the smoking test case;
the judging unit is used for acquiring the category attribute of the smoking test case after judging that the test result is the test failure; wherein the category attribute of the smoking test case is preset;
the obtaining unit is used for obtaining the processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information;
and the first prompting unit is used for prompting the test failure of the smoking test case according to the processing role information.
In yet another aspect, the present application provides an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method for troubleshooting a software system according to any of the embodiments described above when the program is executed by the processor.
In yet another aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the problem-solving method of a software system according to any of the above embodiments.
The problem checking method and the device for the software system provided by the embodiment of the application can test the smoking test case of the software system, obtain the test result of the smoking test case, obtain the category attribute of the smoking test case after judging that the test result is test failure, obtain the processing role information corresponding to the category attribute according to the category attribute of the smoking test case, prompt the test failure of the smoking test case according to the processing role information, prompt the test failure of the smoking test case through the category attribute and the processing role information of the smoking test case, and improve the accuracy of information prompt.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
fig. 1 is a flowchart of a method for troubleshooting a software system according to an embodiment of the present application.
Fig. 2 is a schematic structural diagram of a device for troubleshooting a software system according to an embodiment of the present application.
Fig. 3 is a schematic structural diagram of a device for troubleshooting a software system according to another embodiment of the present application.
Fig. 4 is a schematic structural diagram of a device for troubleshooting a software system according to still another embodiment of the present application.
Fig. 5 is a schematic structural diagram of a problem-checking device of a software system according to another embodiment of the present application.
Fig. 6 is a schematic physical structure of an electronic device according to an embodiment of the application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present application and their descriptions herein are for the purpose of explaining the present application, but are not to be construed as limiting the application. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be arbitrarily combined with each other.
In order to facilitate understanding of the technical scheme provided by the application, the following description will briefly explain relevant content of the technical scheme of the application. In order to test a software system, a smoking test case needs to be designed, and when the smoking test case is designed, the design needs to be performed aiming at the problems affecting the application version and the environment normal test of the software system, so that the environment problem of the software system is found and solved. In the embodiment of the application, in order to accurately locate the problem of test failure of the smoking test cases, each smoking test case corresponds to one problem of test failure, namely, each smoking test case is designed aiming at one environmental problem possibly occurring in a software system. For each smoking test case, a category attribute is defined, which is defined based on the problem of test failure of the smoking test case. According to the problem investigation method for the software system, after the smoking test case fails to be tested, corresponding personnel can be prompted to process according to the preset mechanism according to the category attribute of the smoking test case, and the software system is supervised to be subjected to problem investigation and solution, so that the problem investigation and solution efficiency is improved, and the delivery efficiency of the software system is improved.
Fig. 1 is a flow chart of a method for troubleshooting a software system according to an embodiment of the present application, as shown in fig. 1, where the method for troubleshooting a problem of a software system according to an embodiment of the present application includes:
s101, testing a smoking test case of a software system to obtain a test result of the smoking test case;
specifically, when the software system needs to be tested, the server tests a smoking test case on the software system, so that a test result of the smoking test case can be obtained, if no problem occurs in the smoking test case, the smoking test case passes, and if the problem occurs in the smoking test case, the smoking test case fails. Wherein, the smoking test cases are preset, and each smoking test case corresponds to a reason of test failure. The execution main body of the problem investigation method of the software system provided by the embodiment of the application comprises, but is not limited to, a server.
S102, if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset;
specifically, after obtaining the test result of the smoking test case, if the test result is determined to be a test failure, the server obtains the category attribute of the smoking test case. The category attribute of the smoking test case is preset, the smoking test case corresponds to one category attribute, the category attribute is set according to actual needs, and the embodiment of the application is not limited.
For example, the category attribute may be set based on a test failure cause of the smoking test case. The category attribute may be a base resource class, a base service class, an application class, or a business class.
S103, according to the category attribute of the smoking test case, processing role information corresponding to the category attribute is obtained; wherein the category attribute corresponds to the processing role information;
specifically, after obtaining the category attribute of the smoking test case, the server may query and obtain processing role information corresponding to the category attribute according to the category attribute, where the processing role information is a contact way of a processing role person, and the processing role information includes, but is not limited to, a mailbox, a mobile phone number, a micro signal, and the like. The class attribute corresponds to the processing role information, the corresponding relation between the class attribute and the processing role information is preset, and the class attribute of the smoking test case corresponds to the processing role information of one processing role personnel.
For example, the category attributes include a basic resource class, a basic service class, an application class, or a business class, and the process role personnel include system maintenance personnel, application maintenance personnel, development personnel, and test personnel. The class attribute of the smoking test case A is a basic resource class, and the corresponding processing role information is the processing role information of a system maintainer. The class attribute of the smoking test case B is a basic service class, and the corresponding role processing information is the processing role information of an application maintainer. The class attribute of the smoking test case C is an application class, and the corresponding role processing information is the processing role information of a developer. The class attribute of the smoking test case D is a service class, and the corresponding role processing information is the processing role information of one tester.
S104, prompting the test failure of the smoking test case according to the processing role information.
Specifically, after obtaining the processing role information, the server sends a problem checking prompt to processing role personnel corresponding to the processing role information according to the processing role information so as to prompt that the smoking test case fails in test. After the processing role personnel know that the test of the smoking test case fails, the processing role personnel can check the problem of the test failure of the smoking test case so as to solve the problem of the test failure of the smoking test case as soon as possible.
The problem checking method of the software system provided by the embodiment of the application can test the smoking test case of the software system, obtain the test result of the smoking test case, obtain the category attribute of the smoking test case after judging that the test result is test failure, obtain the processing role information corresponding to the category attribute according to the category attribute of the smoking test case, prompt the smoking test case to test failure according to the processing role information, prompt the smoking test case to test failure through the category attribute and the processing role information of the smoking test case, and improve the accuracy of information prompt. In addition, the testing and problem-solving process of the smoking test case can be recorded, and effective data is provided for subsequent improvement and treatment.
On the basis of the above embodiments, the method for troubleshooting a software system according to the embodiment of the present application further includes:
after the environment changes, the software system is re-tested for the smoke test cases.
Specifically, after the software system passes the test and is put into use, if the server judges that the environment changes, the smoking test case is rerun to detect whether the operation of the software system has a problem after the environment changes, if so, the test fails, and the server prompts the smoking test case that the test fails according to the processing role information. The environment change is, for example, a version change of a software system or a configuration information change of the software system, and is set according to actual needs, which is not limited by the embodiment of the application.
On the basis of the above embodiments, the method for troubleshooting a software system according to the embodiment of the present application further includes:
if judging that the smoking test case is not tested to be successful within the preset time after the first test failure, prompting the smoking test case to be overtime in problem investigation according to the responsible person information corresponding to the processing role information.
Specifically, after prompting that the smoking test case fails, the server checks the problem that the smoking test case fails, and solves the problem as soon as possible, and then tests the smoking test case again on the server to obtain a test result of the smoking test case, wherein the test result is that the test fails or the test passes. When the test result is that the test passes, the problem investigation of the test failure of the smoking test case is described, and it is understood that the server performs the test of the smoking test case at least twice on the software system before the problem investigation is completed. The server records the test time of the first test of the smoking test case, if the test result of the first test is a test failure, the test result of the last test of the smoking test case is queried within a preset time, and if the test result of the last test is a test failure or the test result of the second test of the smoking test case is not queried, the server judges that the smoking test case does not have a test success within the preset time after the first test failure, and the problem of the test failure of the smoking test case is not solved. And the server sends a problem investigation overtime prompt to the responsible person corresponding to the responsible person information according to the responsible person information corresponding to the processing role information so as to prompt the problem investigation overtime of the smoking test case. After knowing that the problem investigation of the smoking test case is overtime, the responsible person can prompt the personnel of the processing role to accelerate the investigation of the problem, or send personnel to conduct the investigation of the problem under the condition that the problem is difficult to process. The responsible person information corresponding to the processing role information is preset, and is a contact way of the responsible person, including but not limited to a mailbox, a mobile phone number, a micro signal and the like, and the responsible person information corresponds to one responsible person and can be a direct leader of the processing role person or an item responsible person. The preset time is set according to actual needs, and the embodiment of the application is not limited.
On the basis of the above embodiments, the method for troubleshooting a software system according to the embodiment of the present application further includes:
and prompting the test failure of the smoking test case according to the concerned role information corresponding to the category attribute.
Specifically, after the test of the smoking test case fails, the server may query according to the category attribute to obtain the attention role information corresponding to the category attribute, and then prompt the test of the smoking test case fails according to the attention role information corresponding to the category attribute. The attention character information is the contact information of attention character personnel, and the attention character information comprises but is not limited to a mailbox, a mobile phone number, a micro signal and the like. The category attribute corresponds to the attention role information, the corresponding relation between the category attribute and the attention role information is preset, and the category attribute of the smoking test case corresponds to the attention role information of at least one attention role person. The concerned role personnel can be personnel in the same project group or commonly developed software system with the processing role personnel, and the setting is carried out according to actual needs, so that the embodiment of the application is not limited.
Fig. 2 is a schematic structural diagram of a problem-checking device of a software system according to an embodiment of the present application, as shown in fig. 2, further, based on the above embodiments, the problem-checking device of a software system according to an embodiment of the present application includes a testing unit 201, a judging unit 202, an obtaining unit 203, and a first prompting unit 204, where:
the test unit 201 is used for testing a smoking test case of the software system to obtain a test result of the smoking test case; the judging unit 202 is configured to obtain a category attribute of the smoking test case after judging that the test result is a test failure; wherein the category attribute of the smoking test case is preset; the obtaining unit 203 is configured to obtain processing role information corresponding to a category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information; the first prompting unit 204 is configured to prompt the failure of the test of the smoking test case according to the processing role information.
Specifically, when a software system needs to be tested, the test unit 201 tests a smoking test case on the software system, so that a test result of the smoking test case can be obtained, if no problem occurs in the process of the smoking test case, the smoking test case passes, and if the problem occurs in the process of the smoking test case, the smoking test case fails. Wherein, the smoking test cases are preset, and each smoking test case corresponds to a reason of test failure.
After obtaining the test result of the smoking test case, if the judging unit 202 judges that the test result is a test failure, the category attribute of the smoking test case is obtained. The category attribute of the smoking test case is preset, the smoking test case corresponds to one category attribute, the category attribute is set according to actual needs, and the embodiment of the application is not limited.
After obtaining the category attribute of the smoking test case, the obtaining unit 203 may obtain, according to the category attribute query, processing role information corresponding to the category attribute, where the processing role information is a contact way of a processing role person, and the processing role information includes, but is not limited to, a mailbox, a mobile phone number, a micro signal, and the like. The class attribute corresponds to the processing role information, the corresponding relation between the class attribute and the processing role information is preset, and the class attribute of the smoking test case corresponds to the processing role information of one processing role personnel.
After the processing role information is obtained, the first prompting unit 204 sends a problem checking prompt to the processing role personnel corresponding to the processing role information according to the processing role information so as to prompt that the smoking test case fails to test. After the processing role personnel know that the test of the smoking test case fails, the processing role personnel can check the problem of the test failure of the smoking test case so as to solve the problem of the test failure of the smoking test case as soon as possible.
The problem checking device of the software system provided by the embodiment of the application can test the smoking test case of the software system, obtain the test result of the smoking test case, obtain the category attribute of the smoking test case after judging that the test result is test failure, obtain the processing role information corresponding to the category attribute according to the category attribute of the smoking test case, prompt the smoking test case to test failure according to the processing role information, prompt the smoking test case to test failure through the category attribute and the processing role information of the smoking test case, and improve the accuracy of information prompt.
Fig. 3 is a schematic structural diagram of a problem-checking device of a software system according to another embodiment of the present application, as shown in fig. 3, further, based on the above embodiments, the problem-checking device of a software system according to an embodiment of the present application further includes a retest unit 205, where:
the retest unit 205 is configured to retest the smoking test cases on the software system after the change in environment.
Specifically, after the software system passes the test and is put into use, if the retest unit 205 determines that the environment changes, the smoke test case is rerun to detect whether there is a problem in the operation of the software system after the environment changes, if there is a problem, the test fails, and if the test fails, the retest unit 205 prompts the smoke test case that the test fails according to the processing role information. The environment change is, for example, a version change of a software system or a configuration information change of the software system, and is set according to actual needs, which is not limited by the embodiment of the application.
Fig. 4 is a schematic structural diagram of a problem-checking device of a software system according to another embodiment of the present application, as shown in fig. 4, further, based on the above embodiments, the problem-checking device of a software system according to an embodiment of the present application further includes a second prompting unit 206, where:
the second prompting unit 206 is configured to prompt, after judging that the smoking test case is known to have not been tested for a time period within a preset time period after the first test failure, that the problem investigation of the smoking test case is overtime according to the responsible person information corresponding to the processing role information.
Specifically, after prompting that the test of the smoking test case fails, the processing role personnel corresponding to the processing role information should check the problem of the test failure of the smoking test case and solve the problem as soon as possible, and then test the smoking test case again on the software system to obtain a test result of the smoking test case, wherein the test result is the test failure or the test passing. When the test result is that the test passes, the problem investigation of the test failure of the smoking test case is described, and it is understood that the software system is tested at least twice before the problem investigation is completed. The second prompting unit 206 records the test time of the first test of the smoking test case, if the test result of the first test is a test failure, the test result of the last test of the smoking test case is queried within a preset time, and if the test result of the last test is a test failure or the test result of the second test of the smoking test case is not queried, the second prompting unit 206 judges that the smoking test case does not have a test success within the preset time after the first test failure, which indicates that the problem of the test failure of the smoking test case is not solved. The second prompting unit 206 sends a problem investigation timeout prompt to the responsible party corresponding to the responsible party information according to the responsible party information corresponding to the processing role information, so as to prompt the problem investigation timeout of the smoking test case. After knowing that the problem investigation of the smoking test case is overtime, the responsible person can prompt the personnel of the processing role to accelerate the investigation of the problem, or send personnel to conduct the investigation of the problem under the condition that the problem is difficult to process. The responsible person information corresponding to the processing role information is preset, and is a contact way of the responsible person, including but not limited to a mailbox, a mobile phone number, a micro signal and the like, and the responsible person information corresponds to one responsible person and can be a direct leader of the processing role person or an item responsible person. The preset time is set according to actual needs, and the embodiment of the application is not limited.
Fig. 5 is a schematic structural diagram of a problem-checking device for a software system according to another embodiment of the present application, as shown in fig. 5, further, based on the above embodiments, the problem-checking device for a software system according to an embodiment of the present application further includes a third prompting unit 207, where:
the third prompting unit 207 is configured to prompt the failure of the test of the smoking test case according to the attention role information corresponding to the category attribute.
Specifically, after the smoking test case fails, the third prompting unit 207 may obtain, according to the category attribute query, the attention role information corresponding to the category attribute, and prompt that the smoking test case fails. The attention character information is the contact information of attention character personnel, and the attention character information comprises but is not limited to a mailbox, a mobile phone number, a micro signal and the like. The category attribute corresponds to the attention role information, the corresponding relation between the category attribute and the attention role information is preset, and the category attribute of the smoking test case corresponds to the attention role information of at least one attention role person. The concerned role personnel can be personnel in the same project group or commonly developed software system with the processing role personnel, and the setting is carried out according to actual needs, so that the embodiment of the application is not limited.
The embodiment of the problem-checking device for a software system provided in the embodiment of the present application may be specifically used to execute the processing flow of each method embodiment, and the functions thereof are not described herein in detail, and reference may be made to the detailed description of the method embodiments.
Fig. 6 is a schematic physical structure of an electronic device according to an embodiment of the present application, as shown in fig. 6, the electronic device may include: processor 601, communication interface (Communications Interface) 602, memory 603 and communication bus 604, wherein processor 601, communication interface 602, memory 603 complete the communication between each other through communication bus 604. The processor 601 may call logic instructions in the memory 603 to perform the following method: testing a smoking test case of a software system to obtain a test result of the smoking test case; if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset; obtaining processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information; and prompting the test failure of the smoking test case according to the processing role information.
Further, the logic instructions in the memory 603 described above may be implemented in the form of software functional units and may be stored in a computer readable storage medium when sold or used as a stand alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, are capable of performing the methods provided by the above-described method embodiments, for example comprising: testing a smoking test case of a software system to obtain a test result of the smoking test case; if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset; obtaining processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information; and prompting the test failure of the smoking test case according to the processing role information.
The present embodiment provides a computer-readable storage medium storing a computer program that causes the computer to execute the methods provided by the above-described method embodiments, for example, including: testing a smoking test case of a software system to obtain a test result of the smoking test case; if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset; obtaining processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information; and prompting the test failure of the smoking test case according to the processing role information.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In the description of the present specification, reference to the terms "one embodiment," "one particular embodiment," "some embodiments," "for example," "an example," "a particular example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the application, and is not meant to limit the scope of the application, but to limit the application to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the application are intended to be included within the scope of the application.

Claims (10)

1. A method for troubleshooting a software system, comprising:
testing a smoking test case of a software system to obtain a test result of the smoking test case;
if the test result is judged to be the test failure, the category attribute of the smoking test case is obtained; wherein the category attribute of the smoking test case is preset; the category attribute is defined based on a problem of test failure of the smoking test case;
obtaining processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information;
and prompting the test failure of the smoking test case according to the processing role information.
2. The method as recited in claim 1, further comprising:
after the environment changes, the software system is re-tested for the smoke test cases.
3. The method as recited in claim 1, further comprising:
if judging that the smoking test case is not tested to be successful within the preset time after the first test failure, prompting the smoking test case to be overtime in problem investigation according to the responsible person information corresponding to the processing role information.
4. A method according to any one of claims 1 to 3, further comprising:
and prompting the test failure of the smoking test case according to the concerned role information corresponding to the category attribute.
5. A problem-solving apparatus of a software system, comprising:
the test unit is used for testing the smoking test case of the software system and obtaining the test result of the smoking test case;
the judging unit is used for acquiring the category attribute of the smoking test case after judging that the test result is the test failure; wherein the category attribute of the smoking test case is preset; the category attribute is defined based on a problem of test failure of the smoking test case;
the obtaining unit is used for obtaining the processing role information corresponding to the category attribute according to the category attribute of the smoking test case; wherein the category attribute corresponds to the processing role information;
and the first prompting unit is used for prompting the test failure of the smoking test case according to the processing role information.
6. The apparatus as recited in claim 5, further comprising:
and the retest unit is used for retesting the smoking test case for the software system after the environment changes.
7. The apparatus as recited in claim 5, further comprising:
and the second prompting unit is used for prompting the problem investigation timeout of the smoking test case according to the responsible person information corresponding to the processing role information after judging that the smoking test case is not tested to be successful within the preset time after the first test failure.
8. The apparatus according to any one of claims 5 to 7, further comprising:
and the third prompting unit is used for prompting the failure of the test of the smoking test case according to the concerned role information corresponding to the category attribute.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of claims 1 to 4 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 4.
CN202010127831.0A 2020-02-28 2020-02-28 Problem investigation method and device for software system Active CN111352839B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010127831.0A CN111352839B (en) 2020-02-28 2020-02-28 Problem investigation method and device for software system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010127831.0A CN111352839B (en) 2020-02-28 2020-02-28 Problem investigation method and device for software system

Publications (2)

Publication Number Publication Date
CN111352839A CN111352839A (en) 2020-06-30
CN111352839B true CN111352839B (en) 2023-09-12

Family

ID=71195826

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010127831.0A Active CN111352839B (en) 2020-02-28 2020-02-28 Problem investigation method and device for software system

Country Status (1)

Country Link
CN (1) CN111352839B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105677567A (en) * 2016-01-10 2016-06-15 上海与德通讯技术有限公司 Automation testing method and system
CN107908550A (en) * 2017-10-27 2018-04-13 链家网(北京)科技有限公司 A kind of software defect statistical processing methods and device
CN108984418A (en) * 2018-08-22 2018-12-11 中国平安人寿保险股份有限公司 Software testing management method, device, electronic equipment and storage medium
CN110147312A (en) * 2019-04-09 2019-08-20 平安科技(深圳)有限公司 Software development test method, device, computer installation and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9037915B2 (en) * 2011-12-08 2015-05-19 International Business Machines Corporation Analysis of tests of software programs based on classification of failed test cases

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105677567A (en) * 2016-01-10 2016-06-15 上海与德通讯技术有限公司 Automation testing method and system
CN107908550A (en) * 2017-10-27 2018-04-13 链家网(北京)科技有限公司 A kind of software defect statistical processing methods and device
CN108984418A (en) * 2018-08-22 2018-12-11 中国平安人寿保险股份有限公司 Software testing management method, device, electronic equipment and storage medium
CN110147312A (en) * 2019-04-09 2019-08-20 平安科技(深圳)有限公司 Software development test method, device, computer installation and storage medium

Also Published As

Publication number Publication date
CN111352839A (en) 2020-06-30

Similar Documents

Publication Publication Date Title
CN106951364B (en) Test method and device
CN105787364B (en) Automatic testing method, device and system for tasks
CN110765018B (en) Automatic interface testing method and equipment
CN109165170B (en) Method and system for automatic request test
US10331439B2 (en) Source code transfer control method, computer program therefor, and recording medium therefor
CN105389256A (en) Unit testing method and system
US9734042B1 (en) System, method, and computer program for automated parameterized software testing
CN109522181B (en) Performance test method, device and equipment of distributed storage system
CN112799953A (en) Interface testing method and device, computer equipment and storage medium
CN113111000A (en) Continuous integration automation test system and method, electronic device and storage medium
CN110888804B (en) Interface test method and interface test platform
CN111221721B (en) Automatic recording and executing method and device for unit test cases
CN111352839B (en) Problem investigation method and device for software system
CN116662197A (en) Automatic interface testing method, system, computer and readable storage medium
CN111767218A (en) Automatic testing method, equipment and storage medium for continuous integration
CN103312554A (en) Testing method and system of multi-server interactive services
CN106940647B (en) Code management method and device
CN113031995B (en) Rule updating method and device, storage medium and electronic equipment
CN114141302A (en) Test method of solid state disk and electronic equipment
CN110941830B (en) Vulnerability data processing method and device
CN112596750A (en) Application testing method and device, electronic equipment and computer readable storage medium
CN113342600A (en) Method and device for monitoring program dependent plug-in
CN112286792A (en) Interface testing method, device, equipment and storage medium
CN113238901A (en) Multi-device automatic testing method and device, storage medium and computer device
CN113157555A (en) System, method and equipment for online pressure measurement data leakage library real-time detection

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant