CN111352839A - Problem troubleshooting method and device for software system - Google Patents

Problem troubleshooting method and device for software system Download PDF

Info

Publication number
CN111352839A
CN111352839A CN202010127831.0A CN202010127831A CN111352839A CN 111352839 A CN111352839 A CN 111352839A CN 202010127831 A CN202010127831 A CN 202010127831A CN 111352839 A CN111352839 A CN 111352839A
Authority
CN
China
Prior art keywords
test case
smoking
category attribute
smoking test
software system
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.)
Granted
Application number
CN202010127831.0A
Other languages
Chinese (zh)
Other versions
CN111352839B (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

Images

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 invention provides a problem troubleshooting method and a problem troubleshooting device for a software system, wherein the method comprises the following steps: testing a smoking test case for a software system to obtain a test result of the smoking test case; if the test result is judged to be test failure, acquiring the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset; according to the category attribute of the smoking test case, acquiring processing role information corresponding to the category attribute; wherein the category attribute corresponds to the processing role information; and prompting that the smoking test case fails to test according to the processing role information. The device is used for executing the method. The problem troubleshooting method and device of the software system provided by the embodiment of the invention improve the accuracy of information prompt.

Description

Problem troubleshooting method and device for software system
Technical Field
The invention relates to the technical field of software testing, in particular to a problem troubleshooting 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 increases in geometric progression along with the development of the width and depth of the software system. Before a software system is on line, strict tests are required to be passed, effective development of the tests depends on efficient availability of a research and development test environment, however, in a complex system scene, the availability of the environment depends on factors such as application version quality, correctness of application configuration, completeness of application parameter data, stability of infrastructure and the like, and cooperation of multiple departments, multiple groups and multiple roles and even multiple regional organizations is required to be worked in a software organization. In the process of testing a software system, a corresponding manual or automatic detection mechanism can be established for software environment problems, but when problems occur, the responsibility is unclear, so that the problems are circulated and attenuated in a plurality of roles, the problems cannot be effectively and timely solved, and the delivery of software products is influenced.
Disclosure of Invention
In view of the problems in the prior art, embodiments of the present invention provide a problem troubleshooting method for a software system, which can at least partially solve the problems in the prior art.
On one hand, the invention provides a problem troubleshooting method of a software system, which comprises the following steps:
testing a smoking test case for a software system to obtain a test result of the smoking test case;
if the test result is judged to be test failure, acquiring the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset;
according to the category attribute of the smoking test case, acquiring processing role information corresponding to the category attribute; wherein the category attribute corresponds to the processing role information;
and prompting that the smoking test case fails to test according to the processing role information.
In another aspect, the present invention provides a problem troubleshooting apparatus for a software system, including:
the testing unit is used for testing the smoking testing case of the software system to obtain the testing result of the smoking testing case;
the judging unit is used for acquiring the 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 is used for 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 the first prompting unit is used for prompting the test failure of the smoking test case according to the processing role information.
In another aspect, the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the steps of the problem troubleshooting method of the software system described in any of the above embodiments are implemented.
In yet another aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the problem troubleshooting method of the software system according to any one of the above embodiments.
The problem troubleshooting method and device for the software system, provided by the embodiment of the invention, can be used for testing the smoking test case for the software system, obtaining the test result of the smoking test case, obtaining the class attribute of the smoking test case after judging that the test result is the test failure, obtaining the processing role information corresponding to the class attribute according to the class attribute of the smoking test case, prompting the test failure of the smoking test case according to the processing role information, and prompting the test failure of the smoking test case through the class attribute and the processing role information of the smoking test case, so that the accuracy of information prompting is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
fig. 1 is a flowchart illustrating a problem troubleshooting method of a software system according to an embodiment of the present invention.
Fig. 2 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to an embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to another embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to still another embodiment of the present invention.
Fig. 5 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to yet another embodiment of the present invention.
Fig. 6 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
In order to facilitate understanding of the technical solutions provided in the present application, the following briefly describes related contents of the technical solutions in the present application. In order to test a software system, a smoking test case needs to be designed, and when the smoking test case is designed, a problem that normal testing of an application version and an environment of the software system is affected needs to be designed, so that the environmental problem of the software system is found and solved. In the embodiment of the invention, in order to accurately position the problem of test failure of the smoking test cases, each smoking test case corresponds to the problem of test failure, namely, each smoking test case is designed aiming at one possible environmental problem of a software system. For each smoking test case, a category attribute is defined, which is defined based on the problem that the smoking test case failed the test. According to the problem troubleshooting method of the software system, after the smoking test case fails to be tested, corresponding personnel can be prompted to process according to the category attribute of the smoking test case and the preset mechanism, the software system is supervised and urged to troubleshoot and solve problems, and therefore the method is orderly and efficient, the efficiency of troubleshooting and solving the problems is improved, and the delivery efficiency of the software system is improved.
Fig. 1 is a schematic flow chart of a problem troubleshooting method of a software system according to an embodiment of the present invention, and as shown in fig. 1, the problem troubleshooting method of the software system according to the embodiment of the present invention includes:
s101, testing a smoking test case of a software system to obtain a test result of the smoking test case;
specifically, when a software system needs to be tested, a server tests a smoking test case for the software system, so that a test result of the smoking test case can be obtained, if no problem occurs in the smoking case testing process, the smoking test case passes the test, and if a problem occurs in the smoking case testing process, the smoking test case fails the test. The smoking test cases are preset, and each smoking test case corresponds to a reason for test failure. The execution subject of the problem troubleshooting method of the software system provided by the embodiment of the invention comprises but is not limited to a server.
S102, if the test result is judged to be test failure, obtaining the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset;
specifically, after obtaining the test result of the smoking test case, if the server determines that the test result is 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, and the category attribute is set according to actual needs.
For example, the category attribute may be set according to a test failure reason of the smoking test case. The category attribute may be a base resource category, a base service category, an application category, or a traffic category.
S103, acquiring 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;
specifically, after obtaining the category attribute of the smoking test case, the server may query, according to the category attribute, processing role information corresponding to the category attribute, where the processing role information is a contact manner of processing role personnel, and the processing role information includes, but is not limited to, a mailbox, a mobile phone number, a micro signal, and the like. The category attribute corresponds to the processing role information, the corresponding relation between the category attribute and the processing role information is preset, and the category attribute of the smoking test case corresponds to the processing role information of one processing role person.
For example, the category attribute includes a basic resource class, a basic service class, an application class, or a business class, and the processing role personnel includes system maintainers, application maintainers, developers, and testers. The category attribute of the smoking test case A is a basic resource category, and the corresponding processing role information is the processing role information of a system maintainer. The category attribute of the smoking test case B is a basic service category, and the corresponding role processing information is the processing role information of an application maintenance worker. The category attribute of the smoking test case C is an application category, and the corresponding role processing information is the processing role information of a developer. The category attribute of the smoking test case D is a service category, and the corresponding role processing information is the processing role information of a tester.
And S104, prompting that the smoking test case fails to test according to the processing role information.
Specifically, after obtaining the processing role information, the server sends a problem troubleshooting prompt to a processing role worker corresponding to the processing role information according to the processing role information, so as to prompt that the smoking test case fails to be tested. After the processing role personnel know that the smoking test case fails to test, the processing role personnel can check the problem of the testing failure of the smoking test case so as to solve the problem of the testing failure of the smoking test case as soon as possible.
The problem troubleshooting method of the software system provided by the embodiment of the invention can test the smoking test case of the software system, obtain the test result of the smoking test case, obtain the class attribute of the smoking test case after judging that the test result is the test failure, obtain the processing role information corresponding to the class attribute according to the class attribute of the smoking test case, prompt the test failure of the smoking test case according to the processing role information, and prompt the test failure of the smoking test case through the class attribute and the processing role information of the smoking test case, thereby improving the accuracy of information prompt. In addition, the testing and problem troubleshooting 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, further, the problem troubleshooting method for the software system provided by the embodiment of the present invention further includes:
and after the environment is changed, the software system is subjected to the smoking test case again.
Specifically, after the software system passes the test and is put into use, if the server judges that the environment changes, the server reruns the smoking test case to detect whether the software system runs with a problem after the environment changes, and if the software system runs with a problem, 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 the software system or a configuration information change of the software system, and is set according to actual needs, which is not limited in the embodiments of the present invention.
On the basis of the above embodiments, further, the problem troubleshooting method for the software system provided by the embodiment of the present invention further includes:
and prompting that the problem of the smoking test case is overtime according to the information of the responsible person corresponding to the processing role information if the smoking test case is judged and known not to succeed in testing within the preset time after the first test failure.
Specifically, after the server prompts that the smoking test case fails to test, the processing role personnel corresponding to the processing role information should investigate and solve the problem that the smoking test case fails to test as soon as possible, and then the software system is tested again on the server to obtain the test result of the smoking test case, wherein the test result is test failure or test passing. When the test result is that the test is passed, the problem investigation of the smoking test case which fails to be tested is completed, and the server can be understood to test the smoking test case at least twice on the software system before the problem investigation is completed. The server records the testing time of the first test of the smoking test case, if the testing result of the first test is a testing failure, the testing result of the last test of the smoking test case is inquired in a preset time, and if the testing result of the last test is a testing failure or the testing result of the second test of the smoking test case is not inquired, the server judges that the smoking test case has not been tested within the preset time after the first test failure, and the problem of the testing failure of the smoking test case is not solved. And the server sends a problem troubleshooting overtime prompt to a person in charge corresponding to the information of the person in charge according to the information of the person in charge corresponding to the processing role information so as to prompt the problem troubleshooting overtime of the smoking test case. After the responsible person knows that the problem of the smoking test case is cleared over time, the responsible person can be supervised to prompt the role handling personnel to speed up the problem clearing, or the responsible person is added to carry out the problem clearing under the condition that the problem handling is difficult. The information of the responsible person corresponding to the processing role information is preset, the information of the responsible person 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 information of the responsible person corresponds to one responsible person and can be a direct leader of the processing role personnel or a project responsible person. The preset time is set according to actual needs, and the embodiment of the invention is not limited.
On the basis of the above embodiments, further, the problem troubleshooting method for the software system provided by the embodiment of the present invention further includes:
and prompting that the smoking test case fails to test according to the attention role information corresponding to the category attribute.
Specifically, after the smoking test case fails to be tested, the server may query, according to the category attribute, to obtain the attention role information corresponding to the category attribute, and then prompt the smoking test case to fail to be tested according to the attention role information corresponding to the category attribute. The concerned role information is the contact information of the concerned role personnel, and the concerned role 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 role-concerned person may be a person who is in a project group with the role-processing person or jointly develops a software system, and the setting is performed according to actual needs, and the embodiment of the present invention is not limited.
Fig. 2 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to an embodiment of the present invention, as shown in fig. 2, on the basis of the foregoing embodiments, further, the problem troubleshooting apparatus of the software system according to the embodiment of the present invention includes a testing unit 201, a determining unit 202, an obtaining unit 203, and a first prompting unit 204, where:
the testing unit 201 is configured to test a smoking test case for a software system, and obtain a test result of the smoking test case; the judging unit 202 is configured to obtain the 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 the 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 that the smoking test case fails to be tested according to the processing role information.
Specifically, when a software system needs to be tested, the testing unit 201 performs a test on a smoking test case for the software system, so as to obtain a test result of the smoking test case, where if no problem occurs in the process of testing the smoking test case, the smoking test case passes the test, and if a problem occurs in the process of testing the smoking test case, the smoking test case fails the test. The smoking test cases are preset, and each smoking test case corresponds to a reason for test failure.
After obtaining the test result of the smoking test case, if the determining unit 202 determines 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, and the category attribute is set according to actual needs.
After the category attribute of the smoking test case is obtained, the obtaining unit 203 may obtain processing role information corresponding to the category attribute according to the category attribute, where the processing role information is a contact manner 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 category attribute corresponds to the processing role information, the corresponding relation between the category attribute and the processing role information is preset, and the category attribute of the smoking test case corresponds to the processing role information of one processing role person.
After the processing role information is obtained, the first prompting unit 204 sends a problem troubleshooting prompt to a processing role worker corresponding to the processing role information according to the processing role information to prompt that the smoking test case fails in testing. After the processing role personnel know that the smoking test case fails to test, the processing role personnel can check the problem of the testing failure of the smoking test case so as to solve the problem of the testing failure of the smoking test case as soon as possible.
The problem troubleshooting device of the software system provided by the embodiment of the invention can test the smoking test case of the software system, obtain the test result of the smoking test case, obtain the class attribute of the smoking test case after judging that the test result is the test failure, obtain the processing role information corresponding to the class attribute according to the class attribute of the smoking test case, prompt the test failure of the smoking test case according to the processing role information, and prompt the test failure of the smoking test case through the class attribute and the processing role information of the smoking test case, thereby improving the accuracy of information prompt.
Fig. 3 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to another embodiment of the present invention, as shown in fig. 3, on the basis of the foregoing embodiments, further, the problem troubleshooting apparatus of the software system according to the embodiment of the present invention further includes a retest unit 205, where:
the retesting unit 205 is configured to retest the software system for the smoking test case after the environment is changed.
Specifically, after the software system passes the test and is put into use, if the retesting unit 205 determines that the environment changes, the smoking test case is rerun to detect whether there is a problem in the running of the software system after the environment changes, and if there is a problem, the retesting unit 205 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 the software system or a configuration information change of the software system, and is set according to actual needs, which is not limited in the embodiments of the present invention.
Fig. 4 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to still another embodiment of the present invention, as shown in fig. 4, on the basis of the foregoing embodiments, further, the problem troubleshooting apparatus of the software system according to the embodiment of the present invention further includes a second prompting unit 206, where:
the second prompting unit 206 is configured to prompt that the problem troubleshooting of the smoking test case is overtime according to the information of the responsible person corresponding to the processing role information after judging that the smoking test case has not been tested successfully within a preset time after the first test fails.
Specifically, after the smoking test case is prompted to fail in testing, the processing role personnel corresponding to the processing role information should investigate and solve the problem of the smoking test case that fails in testing, and then perform testing on the smoking test case again to obtain the test result of the smoking test case, where the test result is testing failure or testing passing. When the test result is that the test is passed, the problem investigation of the smoking test case which fails in the test is completed, and it can be understood that the software system needs to be tested at least twice before the problem investigation is completed. The second prompting unit 206 records a test time for performing a first test on the smoking test case, and if the test result of the first test is a test failure, the test result of a last test on 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 a second test on the smoking test case is not queried, the second prompting unit 206 determines that the smoking test case has not been tested 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 troubleshooting timeout prompt to the responsible person corresponding to the information of the responsible person according to the information of the responsible person corresponding to the information of the processing role, so as to prompt that the problem troubleshooting of the smoking test case is timeout. After the responsible person knows that the problem of the smoking test case is cleared over time, the responsible person can be supervised to prompt the role handling personnel to speed up the problem clearing, or the responsible person is added to carry out the problem clearing under the condition that the problem handling is difficult. The information of the responsible person corresponding to the processing role information is preset, the information of the responsible person 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 information of the responsible person corresponds to one responsible person and can be a direct leader of the processing role personnel or a project responsible person. The preset time is set according to actual needs, and the embodiment of the invention is not limited.
Fig. 5 is a schematic structural diagram of a problem troubleshooting apparatus of a software system according to another embodiment of the present invention, as shown in fig. 5, on the basis of the foregoing embodiments, further, the problem troubleshooting apparatus of the software system according to the embodiment of the present invention further includes a third prompting unit 207, where:
the third prompting unit 207 is configured to prompt that the smoking test case fails to be tested according to the attention role information corresponding to the category attribute.
Specifically, after the smoking test case fails to be tested, the third prompting unit 207 may query, according to the category attribute, to obtain the attention role information corresponding to the category attribute, and prompt the smoking test case to fail to be tested. The concerned role information is the contact information of the concerned role personnel, and the concerned role 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 role-concerned person may be a person who is in a project group with the role-processing person or jointly develops a software system, and the setting is performed according to actual needs, and the embodiment of the present invention is not limited.
The embodiment of the problem troubleshooting apparatus of the software system provided in the embodiment of the present invention may be specifically configured to execute the processing flows of the above method embodiments, and the functions of the apparatus are not described herein again, and refer to the detailed description of the above method embodiments.
Fig. 6 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 6, the electronic device may include: a processor (processor)601, a communication Interface (Communications Interface)602, a memory (memory)603 and a communication bus 604, wherein the processor 601, the communication Interface 602 and the memory 603 complete communication with each other through the communication bus 604. The processor 601 may call logic instructions in the memory 603 to perform the following method: testing a smoking test case for a software system to obtain a test result of the smoking test case; if the test result is judged to be test failure, acquiring the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset; according to the category attribute of the smoking test case, acquiring processing role information corresponding to the category attribute; wherein the category attribute corresponds to the processing role information; and prompting that the smoking test case fails to test according to the processing role information.
In addition, the logic instructions in the memory 603 may be implemented in the form of software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and 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, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, comprising: testing a smoking test case for a software system to obtain a test result of the smoking test case; if the test result is judged to be test failure, acquiring the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset; according to the category attribute of the smoking test case, acquiring processing role information corresponding to the category attribute; wherein the category attribute corresponds to the processing role information; and prompting that the smoking test case fails to test according to the processing role information.
The present embodiment provides a computer-readable storage medium, which stores a computer program, where the computer program causes the computer to execute the method provided by the above method embodiments, for example, the method includes: testing a smoking test case for a software system to obtain a test result of the smoking test case; if the test result is judged to be test failure, acquiring the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset; according to the category attribute of the smoking test case, acquiring processing role information corresponding to the category attribute; wherein the category attribute corresponds to the processing role information; and prompting that the smoking test case fails to test according to the processing role information.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 herein, reference to the description of the terms "one embodiment," "a 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 invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. 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 above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (10)

1. A problem troubleshooting method for a software system, comprising:
testing a smoking test case for a software system to obtain a test result of the smoking test case;
if the test result is judged to be test failure, acquiring the category attribute of the smoking test case; wherein the category attribute of the smoking test case is preset;
according to the category attribute of the smoking test case, acquiring processing role information corresponding to the category attribute; wherein the category attribute corresponds to the processing role information;
and prompting that the smoking test case fails to test according to the processing role information.
2. The method of claim 1, further comprising:
and after the environment is changed, the software system is subjected to the smoking test case again.
3. The method of claim 1, further comprising:
and prompting that the problem of the smoking test case is overtime according to the information of the responsible person corresponding to the processing role information if the smoking test case is judged and known not to succeed in testing within the preset time after the first test failure.
4. The method of any of claims 1 to 3, further comprising:
and prompting that the smoking test case fails to test according to the attention role information corresponding to the category attribute.
5. A problem troubleshooting apparatus for a software system, comprising:
the testing unit is used for testing the smoking testing case of the software system to obtain the testing result of the smoking testing case;
the judging unit is used for acquiring the 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 is used for 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 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 of claim 5, further comprising:
and the retesting unit is used for retesting the smoking test case for the software system after the environment is changed.
7. The apparatus of claim 5, further comprising:
and the second prompting unit is used for prompting that the problem troubleshooting of the smoking test case is overtime according to the information of the responsible person corresponding to the processing role information after judging that the smoking test case does not succeed in testing within the preset time after the first test fails.
8. The apparatus of any one of claims 5 to 7, further comprising:
and the third prompting unit is used for prompting the test failure of the smoking test case according to the attention 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 steps of the method of any of claims 1 to 4 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of 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 true CN111352839A (en) 2020-06-30
CN111352839B 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 (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130151906A1 (en) * 2011-12-08 2013-06-13 International Business Machines Corporation Analysis of Tests of Software Programs Based on Classification of Failed Test Cases
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

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130151906A1 (en) * 2011-12-08 2013-06-13 International Business Machines Corporation Analysis of Tests of Software Programs Based on Classification of Failed Test Cases
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
CN111352839B (en) 2023-09-12

Similar Documents

Publication Publication Date Title
CN109947641B (en) Automatic testing method and device
CN105787364B (en) Automatic testing method, device and system for tasks
CN107766236B (en) Test task automatic management method, device, equipment and storage medium
CN110765018B (en) Automatic interface testing method and equipment
CN109710508A (en) Test method, test device, test equipment and computer readable storage medium
CN107025224B (en) Method and equipment for monitoring task operation
CN110990289B (en) Method and device for automatically submitting bug, electronic equipment and storage medium
CN112799953A (en) Interface testing method and device, computer equipment and storage medium
CN110275992B (en) Emergency processing method, device, server and computer readable storage medium
CN111367782B (en) Regression testing data automatic generation method and device
CN113971031A (en) Software package dependency relationship checking method and device
CN110727585B (en) Memory leak detection method, device, electronic equipment and readable storage medium
CN113050971A (en) Software version management system and method based on block chain
CN111352839A (en) Problem troubleshooting method and device for software system
CN116662197A (en) Automatic interface testing method, system, computer and readable storage medium
CN115525568A (en) Code coverage rate inspection method and device, computer equipment and storage medium
CN114141302A (en) Test method of solid state disk and electronic equipment
CN113157528A (en) Operation change monitoring method and device based on big data service cloud
CN114500249A (en) Root cause positioning method and device
CN110888809B (en) Risk prediction method and device for test task
CN112286792A (en) Interface testing method, device, equipment and storage medium
CN112596750A (en) Application testing method and device, electronic equipment and computer readable storage medium
CN113031995A (en) Rule updating method and device, storage medium and electronic equipment
CN110618943A (en) Security service test method and device, electronic equipment and readable storage medium
CN112214409B (en) Operation and maintenance method and device used in test environment

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