CN116303019A - Test tracing method, device, equipment and medium - Google Patents
Test tracing method, device, equipment and medium Download PDFInfo
- Publication number
- CN116303019A CN116303019A CN202310264964.6A CN202310264964A CN116303019A CN 116303019 A CN116303019 A CN 116303019A CN 202310264964 A CN202310264964 A CN 202310264964A CN 116303019 A CN116303019 A CN 116303019A
- Authority
- CN
- China
- Prior art keywords
- test
- software product
- result
- target software
- information
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 443
- 238000000034 method Methods 0.000 title claims abstract description 72
- 230000008859 change Effects 0.000 claims abstract description 51
- 230000008569 process Effects 0.000 claims description 25
- 238000012545 processing Methods 0.000 claims description 22
- 230000007547 defect Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 16
- 238000011161 development Methods 0.000 claims description 15
- 238000003860 storage Methods 0.000 claims description 13
- 238000010998 test method Methods 0.000 claims description 10
- 239000000047 product Substances 0.000 description 32
- 238000004519 manufacturing process Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 239000012467 final product Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001737 promoting effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000010923 batch production Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013100 final test Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a test tracing method, a test tracing device, test tracing equipment and a test tracing medium. Wherein the method comprises the following steps: obtaining a test result of a target software product; if the test result is passed, a test report is generated according to the first test information; wherein the first test information comprises at least one of a test range, a test result, a product version and a code version; issuing the target software product based on the test report; generating a change list according to the first test information so as to trace back the test of a first type based on the change list; wherein the change order corresponds to a unique change order number. According to the technical scheme, the test report can be traced through the change list, and the test information of the product can be traced, so that the complexity of establishing association among tools is reduced.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a test tracing method, apparatus, device, and medium.
Background
In the current software testing process, development and testers are difficult to fully interact and cooperate, and when the testers execute testing, the incidence relation information of the testing results and the associated objects is distributed in management and complicated to find. The test result and the associated information of the associated object are stored in a plurality of systems, and the test result or the associated object must be queried and acquired in different systems when being queried, so that the operation is complicated.
Disclosure of Invention
The invention provides a test tracing method, a test tracing device, a test tracing equipment and a test tracing medium, which can trace test reports and test information of products through a change list, and reduce the complexity of establishing association among tools.
According to an aspect of the present invention, there is provided a tracing method for testing, including:
obtaining a test result of a target software product;
if the test result is passed, a test report is generated according to the first test information; wherein the first test information comprises at least one of a test batch, a test range, a test result, an article version and a code version;
issuing the target software product based on the test report;
generating a change list according to the first test information so as to trace back the test of a first type based on the change list; wherein the change order corresponds to a unique change order number.
Optionally, the method further comprises:
if the test result is not passed, obtaining second test information; wherein the second test information includes at least one of test case identification, test input data, a test procedure, and a test expected result;
and generating a defect record based on the second test information.
Optionally, the test results include automated test results and non-automated test results;
correspondingly, obtaining the test result of the target software product comprises the following steps:
if the test result is an automatic test result, automatically testing the target software product based on the constructed test flow to obtain an automatic test result;
and if the test result is a non-automatic test result, receiving the test result input by the tester to obtain the non-automatic test result.
Optionally, before obtaining the test result of the target software product, the method further includes:
acquiring service requirements corresponding to a target software product;
splitting the business requirement into a plurality of test ranges, and writing test cases and development codes based on the plurality of test ranges;
compiling the development code to generate a primary software product;
performing promotion processing on the primary software product to obtain a target software product; wherein the target software product is rated higher than the primary software product; the promotion process includes a test process.
Optionally, the method further comprises:
establishing association relations between service demands and test cases and codes respectively;
and performing the tracing of the second type of the test based on the association relation.
Optionally, obtaining the test result of the target software product includes:
and taking the result of the test processing in the promotion processing as the test result of the target software product.
According to another aspect of the present invention, there is provided a traceability device for testing, comprising:
the test result acquisition module is used for acquiring a test result of the target software product;
the test report generation module is used for generating a test report according to the first test information if the test result is passed; wherein the first test information comprises at least one of test batch, test scope, test result, product version and code version
The product release module is used for releasing the target software product based on the test report;
the test tracing module is used for generating a change list according to the first test information so as to trace the test of the first type based on the change list; wherein the change order corresponds to a unique change order number.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the trace back method of the test of any one of the embodiments of the present invention.
According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to execute a trace back method of a test according to any of the embodiments of the present invention.
According to the technical scheme, the test result of the target software product is obtained; if the test result is passed, a test report is generated according to the first test information; wherein the first test information includes at least one of a test scope, a test report, an artifact version, and a code version; issuing the target software product based on the test report; generating a change list according to the first test information so as to trace back the test of a first type based on the change list; wherein the change order corresponds to a unique change order number. According to the technical scheme, the test report can be traced through the change list, and the test information of the product can be traced, so that the complexity of establishing association among tools is reduced.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a test trace back method provided in accordance with a first embodiment of the present invention;
fig. 2 is a schematic structural diagram of a test trace back device according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of a test tracing method according to a first embodiment of the present invention, where the method may be applied to tracing a test procedure of a software product, and the method may be performed by a test tracing device, where the test tracing device may be implemented in hardware and/or software, and the test tracing device may be configured in an electronic device with data processing capability. As shown in fig. 1, the method includes:
this embodiment may be implemented by the Microsoft Visual Studio Team Foundation Server (TFS) microsoft tool, which may be deployed into a software development environment. Thus enabling the use of various services it provides. In the process of software development, the TFS-based tool can automatically analyze, store the test result into the device, automatically form a defect record and a structured test report, and record the association between the test result and the business requirement entry, the test case, the defect record, the code version, the product, the automated test report, the manual test report, and the like. Illustratively, in the process of DevOps development, a developer develops based on a certain requirement entry, and submitting code to a different code branch of Microsoft Visual Studio Team Foundation Server (TFS) tool triggers a corresponding DevOps pipeline.
S110, obtaining a test result of the target software product.
Among other things, a software product may be understood as a binary file generated by compiling and packaging source code, where different development languages correspond to binary files of different formats, and these binary files may typically run directly on a re-server. A target software product may be understood as a product object that has been subjected to various tests by an integrated build pipeline. The test results may be understood as the results of various automated or non-automated tests on the target software product based on the pipeline of the integrated build. Specifically, in this embodiment, the process of testing the target software product is an operation of testing the software product based on the test case by writing the test case based on the business requirement. In this embodiment, a test result of the target software product may be obtained.
And S120, if the test result is passed, generating a test report according to the first test information.
Wherein the first test information includes at least one of a test lot, a test range, a test result, an article version, and a code version. A test lot is understood to mean that the object of the product to be tested is tested in different lots. The test scope is understood to be the content that the test subject needs to test. The test coverage in this embodiment may be determined based on the business requirements of the article. Test results may be understood as the results of various tests performed on an integrated pipeline. The artifact version may be understood as version information of executable files tested by the target software artifact. The code version may also be referred to as a code baseline, and may be understood as code version information for code development based on business requirements. Test reports are generated from various test information of the target software product during the test. The first test information in this embodiment may be automatically recorded based on TFS. Further, the test report in this embodiment specifically needs to include which test information may be preset based on actual needs by a technician.
In this embodiment, if the test result obtained by testing the target software product is passing, a test report may be generated according to at least one of the test batch, the test range, the test result, the product version and the code version.
In this embodiment, after the target software product passes the test, the TFS may enter a test standard flow after the test passes, automatically form a final test report according to the information such as the test batch, the test range, the product version, the code version, the automated test report link, and the test conclusion, and record the association relationship between the test report and the automated test report. The test report is understood to be a high-level product which can be automatically generated after all the tests on the pipeline pass, and the specific content of the test report can be confirmed by a technician.
In this embodiment, optionally, the test results include an automated test result and a non-automated test result; correspondingly, obtaining the test result of the target software product comprises the following steps: if the test result is an automatic test result, automatically testing the target software product based on the constructed test flow to obtain an automatic test result; and if the test result is a non-automatic test result, receiving the test result input by the tester to obtain the non-automatic test result.
The automated test result is understood to be an automated test in a pre-established test flow. By way of example, the automated test may be an interface automated test, or the like. Non-automated testing may be understood as testing that requires manual confirmation by a technician. A test flow may be understood as a test flow based on tool integration of a pre-built test pipeline. The test flow may include a test flow of a test pipeline, a test flow of a pre-production pipeline, a test flow of a production pipeline, and the like.
In the embodiment, the automatic test can be performed on the target software product based on a pre-constructed test flow to obtain an automatic test result; the non-automatic test result can be obtained by receiving the test result input by the tester. With such an arrangement in this embodiment, the test results of the software product can be determined by different tests in order to determine a test report based on the test information.
In this embodiment, optionally, the method further includes: if the test result is not passed, obtaining second test information; wherein the second test information includes at least one of test case identification, test input data, a test procedure, and a test expected result; and generating a defect record based on the second test information.
The test results may include automated test results and non-automated test results, among others. Test cases can be understood as descriptions of test tasks performed on software products, and embody information such as test schemes, methods, techniques, strategies, and the like. Test case identification may be understood as identification information of the test case, and may be, for example, test case ID information. Each test case has its corresponding ID information. The test input data may be input data information of a current test. The test procedure may be descriptive information of the test procedure. The test expected result may be understood as a test result that the test is expected to achieve. Defect recording can be understood as an erroneous information in the test, a problem that arises. The defect records may be defect records from one to the next, and may correspond to test cases and technicians.
For example, in this embodiment, the TFS may analyze the test result, and if the automated test result is failed, obtain a screenshot in the test process from the automated test platform; the test case ID, test input data, test process description and expected result in the test case can be obtained from the test management platform, and a defect record is automatically created; for non-automatic test, a tester can select whether the test conclusion of the test case is passed or not, if the test result of the non-automatic test is not passed, the TFS automatically acquires the test case ID, the test input data, the test process description and the expected result in the test case from the test management platform to create a defect record, and then the tester perfects the test actual result screenshot in the defect record, thereby establishing the association relation between the test case and the defect record.
In this embodiment, if the test result of the target software product fails, information such as a test case identifier, test input data, a test process, a test expected result and the like in the second test information may be obtained, and a defect record may be automatically generated based on the obtained second test information. Through the arrangement, the defect record can be automatically generated for the test which does not pass the test result, so that technicians who determine corresponding problems can conveniently process the defects in time, and the problems in the test can be more conveniently processed.
In this embodiment, optionally, before obtaining the test result of the target software product, the method further includes: acquiring service requirements corresponding to a target software product; splitting the business requirement into a plurality of test ranges, and writing test cases and development codes based on the plurality of test ranges; compiling the development code to generate a primary software product; performing promotion processing on the primary software product to obtain a target software product; wherein the target software product is rated higher than the primary software product; the promotion process includes a test process.
Where business requirements may be understood as requirements of business functions of the target software product. Test scope is understood to be the scope of the content of a software product that needs to be tested. Test cases can be understood as descriptions of test tasks performed on software products, and embody information such as test schemes, methods, techniques, strategies, and the like. In this embodiment, the TFS may split the service requirement into multiple functional work items, that is, multiple test ranges, and write test cases and develop code based on the multiple test ranges. The primary software product may be understood as being compiled from developed code derived based on business requirements. The target software product is rated higher than the primary software product. Illustratively, promotional level names are typically in order of temporary, primary, intermediate, advanced, final, etc. The promotion process may include a testing process. The promotion processing of the product in the embodiment can be understood as that the product is promoted to the next state after reaching the corresponding standard through a series of quality access control detection, so that the single and credible source of the production deployment version is ensured.
Further, in this embodiment, the primary software product may be obtained by compiling the development code, or the primary product input product library may be generated by performing interface automation test and interface automation test through the integrated construction pipeline, the code is tag-typed, and the naming mode of the code may be the same as the naming mode of the primary product, so as to establish the association relationship between the code and the product; the TFS records the test lot, the product name, the code version, and the automated test report link to establish an association of the product with the automated test report.
In this embodiment, the service requirements corresponding to the target software product may be split into multiple test ranges, and test cases and development codes may be written based on the multiple test ranges; the target software product is obtained by compiling the development code to generate a primary software product and then promoting the primary software product. Through the arrangement, the target software product can be obtained, and the association relation between the requirements of the software product and the test cases and codes is established, so that the test can be traced conveniently.
In this embodiment, optionally, the method further includes: establishing association relations between service demands and test cases and codes respectively; and performing the tracing of the second type of the test based on the association relation.
The second type can be understood as a forward type. In this embodiment, the association relationship between the service requirement and the test case and the code can be established by writing the test case and developing the code based on the service requirement, so that the forward trace of the test is performed based on the association relationship.
In this embodiment, the association relationship between the TFS record service requirement and the test case and the code, and the association relationship between other information in the recording test process, for example, the TFS record test lot, the product version name, the code version and the automated test report link are respectively based on the TFS record service requirement, so as to establish the association relationship between the product and the automated test report. Through the arrangement, the association relation between the test result and the test information is recorded based on the TFS tool, so that the test is conveniently traced.
In this embodiment, optionally, obtaining a test result of the target software product includes: and taking the result of the test processing in the promotion processing as the test result of the target software product.
In this embodiment, the result of the test processing in the promotion processing may be used as the test result of the target software product.
Furthermore, in this embodiment, the primary products in the product library may be promoted to the advanced products step by step through the test flows of the test flow line, the pre-production flow line and the production deployment flow line, and in this process, the test batch and the automated test report link information in the test process are recorded in the TFS, so as to establish the association relationship between the automated test report and the products.
Through the arrangement, the test result of the target software product can be obtained, the test result and the associated object are automatically identified through the algorithm in the TFS, the test information is recorded, and the complexity of establishing the association between tools is reduced.
S130, publishing the target software product based on the test report.
Wherein, release can be understood as that the target software product can perform the operation of the production flow. The embodiment can generate a test report according to the test information after the test is passed, and then issue the target software based on the test report.
And S140, generating a change list according to the first test information so as to trace back the test of the first type based on the change list.
Wherein the change order corresponds to a unique change order number. The change order can be used for recording change information of batch production in production process, including but not limited to change range, production time, production, production baseline and test report, and the change order usually has a unique number as a unique identification. The first type may be understood as a reverse type. In this embodiment, a change order may be generated according to the first test information, so as to perform reverse tracing on the test based on the change order.
Specifically, in this embodiment, a production change may be initiated by a production change system, a technician manually selects a final product to be produced and deploys the final product to a production environment, and the TFS may fill information such as a test range, a test report, a product version, a code version and the like corresponding to the selected product into a change list according to product information, and after production is completed, the TFS automatically backfills change list number information of a requirement item. The embodiment can query information such as requirement items, test cases, defects, test batches, test reports, product versions, code versions and the like on the TFS according to the change order number.
According to the technical scheme, the test result of the target software product is obtained; if the test result is passed, a test report is generated according to the first test information; wherein the first test information includes at least one of a test scope, a test report, an article of manufacture, and a code version; issuing the target software product based on the test report; generating a change list according to the first test information so as to trace back the test of a first type based on the change list; wherein the change order corresponds to a unique change order number. According to the technical scheme, the test can be traced through the change list, the test information of the product can be traced, and the complexity of establishing association among tools is reduced.
Example two
Fig. 2 is a schematic structural diagram of a test trace back device according to a second embodiment of the present invention. As shown in fig. 2, the apparatus includes:
a test result obtaining module 210, configured to obtain a test result of the target software product;
the test report generating module 220 is configured to generate a test report according to the first test information if the test result is passed; wherein the first test information comprises at least one of test batch, test scope, test result, product version and code version
An article publishing module 230 for publishing the target software article based on the test report;
a first type tracing module 240, configured to generate a change order according to the first test information, so as to trace the test of the first type based on the change order; wherein the change order corresponds to a unique change order number.
Optionally, the method further comprises:
the second test information acquisition module is used for acquiring second test information if the test result is failed; wherein the second test information includes at least one of test case identification, test input data, a test procedure, and a test expected result;
and the defect record generating module is used for generating a defect record based on the second test information.
Optionally, the test results include automated test results and non-automated test results;
correspondingly, the test result acquisition module is specifically configured to:
if the test result is an automatic test result, automatically testing the target software product based on the constructed test flow to obtain an automatic test result;
and if the test result is a non-automatic test result, receiving the test result input by the tester to obtain the non-automatic test result.
Optionally, the method further comprises: the target software product acquisition module is used for acquiring the service requirements corresponding to the target software product before acquiring the test result of the target software product;
splitting the business requirement into a plurality of test ranges, and writing test cases and development codes based on the plurality of test ranges;
compiling the development code to generate a primary software product;
performing promotion processing on the primary software product to obtain a target software product; wherein the target software product is rated higher than the primary software product; the promotion process includes a test process.
Optionally, the method further comprises: a second type traceback module for:
establishing association relations between service demands and test cases and codes respectively;
and performing the tracing of the second type of the test based on the association relation.
Optionally, the test result obtaining module is configured to:
and taking the result of the test processing in the promotion processing as the test result of the target software product.
The test tracing device provided by the embodiment of the invention can execute the test tracing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example III
Fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 3, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the test trace back method.
In some embodiments, the traceability method of the test may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the trace back method of testing described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the traceback method of testing in any other suitable way (e.g. by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method of traceability of a test, comprising:
obtaining a test result of a target software product;
if the test result is passed, a test report is generated according to the first test information; wherein the first test information comprises at least one of a test batch, a test range, a test result, an article version and a code version;
issuing the target software product based on the test report;
generating a change list according to the first test information so as to trace back the test of a first type based on the change list; wherein the change order corresponds to a unique change order number.
2. The method as recited in claim 1, further comprising:
if the test result is not passed, obtaining second test information; wherein the second test information includes at least one of test case identification, test input data, a test procedure, and a test expected result;
and generating a defect record based on the second test information.
3. The method of claim 1, wherein the test results comprise automated test results and non-automated test results;
correspondingly, obtaining the test result of the target software product comprises the following steps:
if the test result is an automatic test result, automatically testing the target software product based on the constructed test flow to obtain an automatic test result;
and if the test result is a non-automatic test result, receiving the test result input by the tester to obtain the non-automatic test result.
4. The method of claim 1, further comprising, prior to obtaining the test results for the target software product:
acquiring service requirements corresponding to a target software product;
splitting the business requirement into a plurality of test ranges, and writing test cases and development codes based on the plurality of test ranges;
compiling the development code to generate a primary software product;
performing promotion processing on the primary software product to obtain a target software product; wherein the target software product is rated higher than the primary software product; the promotion process includes a test process.
5. The method as recited in claim 4, further comprising:
establishing association relations between service demands and test cases and codes respectively;
and performing the tracing of the second type of the test based on the association relation.
6. The method of claim 4, wherein obtaining test results for the target software product comprises:
and taking the result of the test processing in the promotion processing as the test result of the target software product.
7. A traceability device for testing, comprising:
the test result acquisition module is used for acquiring a test result of the target software product;
the test report generation module is used for generating a test report according to the first test information if the test result is passed; wherein the first test information comprises at least one of test batch, test scope, test result, product version and code version
The product release module is used for releasing the target software product based on the test report;
the first type tracing module is used for generating a change list according to the first test information so as to trace the test of the first type based on the change list; wherein the change order corresponds to a unique change order number.
8. The apparatus as recited in claim 7, further comprising:
the second test information acquisition module is used for acquiring second test information if the test result is failed; wherein the second test information includes at least one of test case identification, test input data, a test procedure, and a test expected result;
and the defect record generating module is used for generating a defect record based on the second test information.
9. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the traceback method of the test of any of claims 1 to 6.
10. A computer readable storage medium storing computer instructions for causing a processor to perform the traceback method of the test of any of claims 1-6 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310264964.6A CN116303019A (en) | 2023-03-13 | 2023-03-13 | Test tracing method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310264964.6A CN116303019A (en) | 2023-03-13 | 2023-03-13 | Test tracing method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116303019A true CN116303019A (en) | 2023-06-23 |
Family
ID=86793890
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310264964.6A Pending CN116303019A (en) | 2023-03-13 | 2023-03-13 | Test tracing method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116303019A (en) |
-
2023
- 2023-03-13 CN CN202310264964.6A patent/CN116303019A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115016321A (en) | Hardware-in-loop automatic testing method, device and system | |
| CN110865806B (en) | Code processing method, device, server and storage medium | |
| CN110795332A (en) | Automatic testing method and device | |
| CN115576828A (en) | Test case generation method, device, equipment and storage medium | |
| CN116089739A (en) | Message pushing method, device, electronic equipment and storage medium | |
| CN116303013A (en) | Source code analysis method, device, electronic equipment and storage medium | |
| CN116011955A (en) | Robot flow automation demand realization method, device, equipment and storage medium | |
| CN116303019A (en) | Test tracing method, device, equipment and medium | |
| CN115017047A (en) | Test method, system, equipment and medium based on B/S architecture | |
| CN114116288A (en) | Fault processing method, device and computer program product | |
| CN111638905A (en) | Version number generation method and device, electronic equipment and readable storage medium | |
| CN115374010A (en) | Function testing method, device, equipment and storage medium | |
| CN117492822B (en) | Change contrast method, device, electronic equipment and storage medium | |
| CN113297088B (en) | Test method, test device, electronic equipment and storage medium | |
| CN115567624A (en) | Message processing method and device, electronic equipment and medium | |
| CN117609087A (en) | Code processing method, device, equipment and medium | |
| CN109871310B (en) | Version quality testing method and device | |
| CN116755744A (en) | Patch package generation method and device, electronic equipment and storage medium | |
| CN116225390A (en) | Warehouse-in method, device, equipment and medium for software development files | |
| CN115794646A (en) | Software testing method and device, electronic equipment and storage medium | |
| CN115374012A (en) | Automatic regression testing method and device, electronic equipment and storage medium | |
| CN117648252A (en) | Function test method and device for software application, electronic equipment and storage medium | |
| CN116909925A (en) | Test flow management method and management system based on agile iteration | |
| CN116701081A (en) | Communication fault point determining method, device and medium | |
| CN117472751A (en) | Vehicle system function analysis method, device, equipment and medium |
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 |