CN117910956A - Software quality control method, system, device and storage medium - Google Patents
Software quality control method, system, device and storage medium Download PDFInfo
- Publication number
- CN117910956A CN117910956A CN202311873539.3A CN202311873539A CN117910956A CN 117910956 A CN117910956 A CN 117910956A CN 202311873539 A CN202311873539 A CN 202311873539A CN 117910956 A CN117910956 A CN 117910956A
- Authority
- CN
- China
- Prior art keywords
- checking
- result
- project
- test
- stage
- 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 claims abstract description 170
- 238000001514 detection method Methods 0.000 claims abstract description 66
- 238000011161 development Methods 0.000 claims abstract description 30
- 238000000034 method Methods 0.000 claims description 56
- 230000006870 function Effects 0.000 claims description 9
- 238000012550 audit Methods 0.000 claims description 5
- 238000011056 performance test Methods 0.000 claims description 5
- 238000012552 review Methods 0.000 claims description 5
- 238000013461 design Methods 0.000 claims description 4
- 239000000779 smoke Substances 0.000 claims description 4
- 238000003908 quality control method Methods 0.000 abstract description 31
- 238000004891 communication Methods 0.000 abstract description 9
- 230000018109 developmental process Effects 0.000 description 27
- 238000007689 inspection Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 239000000047 product Substances 0.000 description 7
- 238000004590 computer program Methods 0.000 description 6
- 230000009286 beneficial effect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 239000013589 supplement Substances 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000010998 test method Methods 0.000 description 2
- 230000007723 transport mechanism Effects 0.000 description 2
- 230000007812 deficiency Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000002787 reinforcement Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06395—Quality analysis or management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Game Theory and Decision Science (AREA)
- Computer Hardware Design (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a software quality control method, a system, a device and a storage medium, comprising the following steps: newly creating a project task, and transferring the project flow to a development stage; acquiring a development product, and transferring the project flow to an internal test stage; acquiring an internal test result, and if the internal test result is qualified, transferring the project flow to an internal test result detection stage; acquiring a quasi self-checking index and a quasi self-checking result, and determining whether the quasi self-checking result is qualified or not according to the quasi self-checking index; if the quasi self-checking result is qualified, the project flow is transferred to a checking link of the checking result; and acquiring a detection result auditing standard, determining whether the quasi self-checking result is audited to pass or not according to the detection result auditing standard, and if the quasi self-checking result is audited to pass, transferring the project flow to an acceptance testing stage and a project item ending stage. The embodiment of the invention has more comprehensive quality control, improves the stability and the communication efficiency, and can be widely applied to the technical field of computers.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a software quality control method, system, device, and storage medium.
Background
For the mode of a software development team in cooperation with the first and second parties, the traditional software quality control (hereinafter referred to as "quality control") strategy is that the first and second party quality control teams perform functional test and performance test based on a software requirement specification, namely SIT (System Integration Testing, system integration test), after passing, the first party quality control team performs recheck verification on the test result of the first party quality control team, namely UAT (user ACCEPTANCE TEST ), and the whole test process is processed by full manpower. However, the requirement specification cannot be absolutely comprehensive, and the test result of the second quality control team is difficult to provide enough comprehensive and sufficient process evidence, so that the quality control mode may not be comprehensive enough and stable for covering the quality of each level of software, and the rechecking work of the first quality control team may also have the problems of communication inefficiency and understanding errors.
Disclosure of Invention
Accordingly, the present invention is directed to a software quality control method, system, device and storage medium, which has more comprehensive quality control and improved stability and communication efficiency.
In one aspect, an embodiment of the present invention provides a software quality control method, including:
newly creating a project task, and transferring the project flow to a development stage;
acquiring a development product, and transferring the project flow to an internal test stage;
acquiring an internal test result, and if the internal test result is qualified, transferring the project flow to an internal test result detection stage; the internal test result detection stage comprises a quasi self-detection link and a detection result auditing link;
Acquiring a quasi self-checking index and a quasi self-checking result, and determining whether the quasi self-checking result is qualified or not according to the quasi self-checking index; if the quasi self-checking result is qualified, the project flow is transferred to a checking link of the checking result; obtaining a detection result auditing standard, determining whether the quasi self-checking result is audited to pass or not according to the detection result auditing standard, and if the quasi self-checking result is audited to pass, transferring the project flow to an acceptance testing stage; the quasi self-checking result is determined according to a quasi self-checking method;
and acquiring a acceptance test result, and if the acceptance test result is qualified, turning the project flow to a project junction stage, acquiring a junction instruction and closing the project.
Optionally, the software quality control method further comprises:
And if the quasi self-checking result is not qualified, returning the project flow to the internal testing stage.
Optionally, the software quality control method further comprises:
And if the quasi self-checking result audit is not passed, returning the project flow to the internal testing stage.
Optionally, the software quality control method further comprises:
and if the acceptance test result is not qualified, returning the project flow to the development stage.
On the other hand, the embodiment of the invention provides a software quality control system, which comprises a project-stage flow rotor system, a quasi self-checking subsystem and a detection result auditing subsystem, wherein the project-stage flow rotor system is connected with the quasi self-checking subsystem and the detection result auditing subsystem;
The quasi-self-checking subsystem is used for providing quasi-self-checking indexes and quasi-self-checking methods for the project stage flow subsystem;
The detection result auditing subsystem is used for providing detection result auditing standards for the project stage flow subsystem;
the project phase stream rotor system is used for executing the method.
Optionally, the quasi self-checking subsystem includes any one or more project links of requirements, designs, interface tests, system smoke tests, system function tests, compatibility tests, performance tests, security tests, document tests, or review summaries.
Optionally, the interface test includes an interface test case, an interface test script, and an interface test report.
Optionally, the test result audit criteria includes any one or more dimensions of the quasi self-test result, the requirement specification, the test case, and the test report.
In another aspect, an embodiment of the present invention provides a software quality control apparatus, including:
At least one processor;
At least one memory for storing at least one program;
The at least one program, when executed by the at least one processor, causes the at least one processor to implement the method described above.
In another aspect, embodiments of the present invention provide a computer-readable storage medium in which a processor-executable program is stored, which when executed by a processor is configured to perform the above-described method.
The embodiment of the invention has the following beneficial effects: in the development process of the software, an internal test result detection stage is added, wherein the internal test result detection stage comprises a quasi self-checking link and a test result auditing link, when an internal test result is qualified, a project flow is transferred to the quasi self-checking link, whether the quasi self-checking result is qualified or not is determined according to quasi self-checking indexes, if the quasi self-checking result is qualified, the project flow is transferred to the test result auditing link, whether the quasi self-checking result is audited according to a test result auditing standard, if the quasi self-checking result is audited, the project flow is transferred to an acceptance test stage, the quasi self-checking result is determined by a second party, and the quasi self-checking result is audited by the first party and the second party in a common alignment mode in the software test process, so that the requirements of all layers of the two parties are covered, the quality control is more comprehensive.
Drawings
FIG. 1 is a schematic diagram of a software quality control system according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of steps of a software quality control method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a software quality control method according to an embodiment of the present invention;
FIG. 4 is a block diagram of another software quality control system provided by an embodiment of the present invention;
fig. 5 is a block diagram of a software quality control device according to an embodiment of the present invention.
Detailed Description
The invention will now be described in further detail with reference to the drawings and to specific examples. The step numbers in the following embodiments are set for convenience of illustration only, and the order between the steps is not limited in any way, and the execution order of the steps in the embodiments may be adaptively adjusted according to the understanding of those skilled in the art.
It should be noted that although functional block division is performed in a device diagram and a logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in the device, or in the flowchart. The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements 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 application described herein may be implemented, for example, 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 or inherent to such process, method, article, or apparatus.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.
In the software development engineering, the development is generally carried out locally, after the development is completed, whether own codes meet service requirements is judged locally through unit testing, and the stage is to self-detect whether writing is missed or not and make up for the self-consideration deficiency.
First stage (unit test stage): unit testing refers to checking and verifying the smallest testable unit in software. Unit testing is the lowest level of testing activity to be performed during the development of software, where individual units of software will be tested in isolation from other parts of the program.
Second stage (SIT test stage): the SIT test is in its simplest form to combine two units that have been tested into one component, testing the interface between them. System integration testing is the last step in the overall testing phase, where all development and testing collectively appear to produce a functional software system. That is to say, the codes of all developers are integrated, and the testers are tested in a test environment (generally, black-and-white box combined test) to further detect the logic of the codes and the operation result; typically, after this stage is entered, the code is not substantially altered. Only this phase passes and the third phase is reached.
Third stage (UAT test stage): user acceptance testing, i.e., user acceptance testing, is a stage of the system development lifecycle methodology when an associated user or independent tester tests and receives the system according to the test plan and results. It is determined by the system user whether to receive the system. It is a test that determines if a product can meet the contract or user-specified requirements. This stage is the last step of the production; testing is typically performed in a production environment; the user judges whether the system reaches the expected standard through exercise, and the program is required to reach the expected of the user at the stage, so that the system can be put into the market for use.
In the embodiment of the invention, as shown in fig. 1, after the project is started, the development stage is entered, and the development stage is performed by a development team. After the project development is completed, an internal test stage is entered, and the internal test stage is executed by a second party quality control team. After the internal test is finished, an internal test result inspection stage is entered, and in the internal test result inspection stage, two sub-stages are arranged, wherein the first sub-stage is a SIT quasi self-inspection link, and is matched with a SIT quasi self-inspection subsystem to force a second party quality control team to perform self-inspection according to self-inspection items set by the system; the second sub-stage is a SIT detection result auditing link, which is equipped with a SIT detection result auditing subsystem, in which the first quality control team confirms that the detection result of the second quality control team meets the admission requirement of UAT test. After the internal test result detection stage passes, entering an acceptance test stage, and further improving the UAT test case by a quality control team of the first party according to the SIT test result, thereby carrying out acceptance test on the product. And after the acceptance test is finished, project junction items are carried out.
As shown in fig. 2 and 3, an embodiment of the present invention provides a software quality control method, including the following steps:
s100, newly creating project tasks, and turning the project flow to a development stage.
And receiving an externally input new project task, entering a project starting stage, configuring a link to be detected and a detection index of the link for the project task according to the input project detail requirement, and then transferring the project flow to a development stage. The task of newly creating the project can be determined by a project manager, and the project detail requirement can be communicated with the A-party quality control group leader.
S200, acquiring development products, and transferring the project flow to an internal test stage.
After the development stage is completed, the developer forms a product, acquires the development product input by the development team, flows the project flow to the internal test stage, and performs SIT test by the second quality control team.
S300, acquiring an internal test result, and if the internal test result is qualified, transferring the project flow to an internal test result detection stage; the internal test result detection stage comprises a quasi self-detection link and a detection result auditing link.
Acquiring an internal test result (SIT test result) input by a second party quality control team, and if the internal test result is qualified, transferring the project flow to an internal test result detection stage; if the internal test result is unqualified, returning the project flow to the development stage, and re-developing by a development team.
S400, acquiring a quasi self-checking index and a quasi self-checking result, and determining whether the quasi self-checking result is qualified or not according to the quasi self-checking index; if the quasi self-checking result is qualified, the project flow is transferred to a checking link of the checking result; obtaining a detection result auditing standard, determining whether the quasi self-checking result is audited to pass or not according to the detection result auditing standard, and if the quasi self-checking result is audited to pass, transferring the project flow to an acceptance testing stage; the quasi-self-checking result is determined according to a quasi-self-checking method.
The internal test result detection stage comprises a SIT quasi self-detection link and a SIT detection result auditing link. And (3) if the internal test result is qualified, transferring the project flow to an SIT quasi self-checking link of the internal test result detection stage.
Optionally, the software quality control method further comprises:
And S410, if the quasi self-checking result is not qualified, returning the project flow to the internal testing stage.
Optionally, the software quality control method further comprises:
And S420, if the quasi self-checking result audit is not passed, returning the project flow to the internal test stage.
The method comprises the steps of obtaining a quasi self-checking index and a checking execution method from a quasi self-checking subsystem, carrying out self-checking by a second quality control team according to a checking execution prompt, uploading a checking result/accessory materials, automatically carrying out initial examination according to the quasi self-checking index, and judging whether the self-checking result meets the requirement. If the condition is not met, the project flow is returned to the internal test stage, so that the second party quality control team improves the test method and supplements/re-carries out SIT test; when the judging result meets the requirement, the project flow and the detecting result automatically flow to the next link: and checking SIT detection results.
The first party quality control team carries out auditing according to the detection execution prompt, the system automatically judges whether the auditing passes or not according to the content input by the first party quality control team and the detection result auditing standard acquired from the detection result auditing subsystem, if the auditing does not pass, the system returns the project flow to an internal testing stage so as to enable the second party quality control team to improve the testing method and supplement/re-carry out SIT test; if the auditing is passed, the project flow and the auditing result automatically flow to the next stage: and (3) checking and accepting test stage.
S500, acquiring a acceptance test result, if the acceptance test result is qualified, turning the project flow to a project junction stage, acquiring a junction instruction and closing the project.
Optionally, the software quality control method further comprises:
and S510, if the acceptance test result is not qualified, returning the project flow to the development stage.
Obtaining an acceptance test result (UAT test result) input by a quality control team of the first party, if the acceptance test result is qualified, and (3) turning the project flow to a project junction stage, checking the project by a project manager, and if the project passes, acquiring an externally input junction instruction and closing the project. If the acceptance test result is qualified, returning the project flow to the development stage, and re-modifying the product by a development team.
The embodiment of the invention has the following beneficial effects: in the development process of the software, an internal test result detection stage is added, wherein the internal test result detection stage comprises a quasi self-checking link and a test result auditing link, when an internal test result is qualified, a project flow is transferred to the quasi self-checking link, whether the quasi self-checking result is qualified or not is determined according to quasi self-checking indexes, if the quasi self-checking result is qualified, the project flow is transferred to the test result auditing link, whether the quasi self-checking result is audited according to a test result auditing standard, if the quasi self-checking result is audited, the project flow is transferred to an acceptance test stage, the quasi self-checking result is determined by a second party, and the quasi self-checking result is audited by the first party and the second party in a common alignment mode in the software test process, so that the requirements of all layers of the two parties are covered, the quality control is more comprehensive.
Referring to fig. 4, an embodiment of the present invention provides a software quality control system, which includes a project phase flow rotor system, a quasi self-checking subsystem and a detection result auditing subsystem, wherein the project phase flow rotor system is connected with the quasi self-checking subsystem and the detection result auditing subsystem;
The quasi-self-checking subsystem is used for providing quasi-self-checking indexes and quasi-self-checking methods for the project stage flow subsystem;
The detection result auditing subsystem is used for providing detection result auditing standards for the project stage flow subsystem;
the project phase flow rotor system is used for executing the software quality control method.
The project phase stream rotor system includes a processor and a memory, the processor for executing the software quality control method described above. The project stage flow rotor system is provided with six stages of project starting, development stage, internal test result inspection stage, acceptance test stage and project junction item, wherein the internal test result detection stage is further divided into two sub-links of SIT quasi self-inspection link and SIT detection result auditing link. Each stage is filled in/submitted with necessary content and accessories by the relevant staff for the staff in the next stage to perform the operation of the stage. If the detection result of a certain stage does not pass, the project flow can be returned to the designated stage for repair/reinforcement detection.
The quasi self-checking subsystem is operated by a second party quality control team, the quasi self-checking subsystem provides core detection indexes and detection execution methods for various output objects of various project links, the second party quality control team needs to fill in self-checking results of various self-checking items in the system, and then the system can automatically conduct initial review judgment on the filling results according to preset index values. When the judgment result is that the SIT fails, the system returns the project flow to the internal test stage so as to enable the second party quality control team to improve the test method and supplement/re-conduct SIT test; when the system judges that the result is passing, the project flow and the detection result automatically flow to the next link: and (3) a SIT detection result auditing link.
The detection result auditing subsystem is filled in by the quality control team of the first party, sets passing standards and corresponding auditing methods for a plurality of quality dimensions of the SIT detection result, and has the function of automatically judging whether the SIT detection result passes auditing according to the auditing result.
The first party quality control team firstly carries out all-dimensional examination on the self-checking results of SIT quasi self-checking links, the submitted documents of upstream stages such as requirement specifications, test cases, test reports and the like according to an examination method of system prompt, and then fills the examination results into the system according to the system requirements. The system automatically judges whether the auditing passes or not according to the filled content, if the auditing does not pass, the system returns the project flow to an internal testing stage so as to enable the quality control team of the second party to improve the testing method and supplement/re-conduct SIT test; if the auditing is passed, the project flow and the auditing result automatically flow to the next stage: an acceptance test phase.
Optionally, the quasi self-checking subsystem includes any one or more project links of requirements, designs, interface tests, system smoke tests, system function tests, compatibility tests, performance tests, security tests, document tests, or review summaries.
It should be noted that, the project links included in the quasi-self-checking subsystem are determined according to practical applications, and the embodiment is not limited specifically.
The quasi self-checking subsystem comprises any one or more of the project links including but not limited to requirements, designs, interface tests, system smoke tests, system function tests, compatibility tests, performance tests, security tests, document tests, review summaries and the like.
Optionally, the interface test includes an interface test case, an interface test script, and an interface test report.
In a specific embodiment, the core detection indexes and the detection execution methods proposed by the quasi self-checking subsystem for various output objects of the project link are shown in table one. The results, results effects and meaning descriptions, and normal iteration core indexes of each project stage are listed in Table one.
List one
Optionally, the test result auditing standard includes the quasi self-test result, a requirement instruction, a test case and a test
Any one or more dimensions in the report.
In a specific embodiment, the detection result auditing standard of the detection result auditing subsystem is specifically shown in table two. Table two lists the inspection methods corresponding to the plurality of quality dimensions.
Watch II
It can be seen that the content in the above method embodiment is applicable to the system embodiment, and the functions specifically implemented by the system embodiment are the same as those of the method embodiment, and the beneficial effects achieved by the method embodiment are the same as those achieved by the method embodiment.
Referring to fig. 5, an embodiment of the present invention provides a software quality control apparatus, including:
At least one processor;
At least one memory for storing at least one program;
The at least one program, when executed by the at least one processor, causes the at least one processor to implement the method described above.
Wherein the memory is operable as a non-transitory computer readable storage medium storing a non-transitory software program and a non-transitory computer executable program. The memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes remote memory provided remotely from the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
It can be seen that the content in the above method embodiment is applicable to the embodiment of the present device, and the functions specifically implemented by the embodiment of the present device are the same as those of the embodiment of the above method, and the beneficial effects achieved by the embodiment of the above method are the same as those achieved by the embodiment of the above method.
Furthermore, the embodiment of the application also discloses a computer program product or a computer program, and the computer program product or the computer program is stored in a computer readable storage medium. The computer program may be read from a computer readable storage medium by a processor of a computer device, the processor executing the computer program causing the computer device to perform the method as described above. Similarly, the content in the above method embodiment is applicable to the present storage medium embodiment, and the specific functions of the present storage medium embodiment are the same as those of the above method embodiment, and the achieved beneficial effects are the same as those of the above method embodiment.
The embodiment of the present invention also provides a computer-readable storage medium storing a program executable by a processor, which when executed by the processor is configured to implement the above-described method.
It is to be understood that all or some of the steps, systems, and methods disclosed above may be implemented in software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
It is to be understood that all or some of the steps, systems, and methods disclosed above may be implemented in software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
While the preferred embodiment of the present application has been described in detail, the application is not limited to the embodiment, and various equivalent modifications and substitutions can be made by those skilled in the art without departing from the spirit of the application, and these equivalent modifications and substitutions are intended to be included in the scope of the present application as defined in the appended claims.
Claims (10)
1. A method for software quality control, comprising:
newly creating a project task, and transferring the project flow to a development stage;
acquiring a development product, and transferring the project flow to an internal test stage;
acquiring an internal test result, and if the internal test result is qualified, transferring the project flow to an internal test result detection stage; the internal test result detection stage comprises a quasi self-detection link and a detection result auditing link;
Acquiring a quasi self-checking index and a quasi self-checking result, and determining whether the quasi self-checking result is qualified or not according to the quasi self-checking index; if the quasi self-checking result is qualified, the project flow is transferred to a checking link of the checking result; obtaining a detection result auditing standard, determining whether the quasi self-checking result is audited to pass or not according to the detection result auditing standard, and if the quasi self-checking result is audited to pass, transferring the project flow to an acceptance testing stage; the quasi self-checking result is determined according to a quasi self-checking method;
and acquiring a acceptance test result, and if the acceptance test result is qualified, turning the project flow to a project junction stage, acquiring a junction instruction and closing the project.
2. The method according to claim 1, wherein the method further comprises:
And if the quasi self-checking result is not qualified, returning the project flow to the internal testing stage.
3. The method according to claim 1, wherein the method further comprises:
And if the quasi self-checking result audit is not passed, returning the project flow to the internal testing stage.
4. The method according to claim 1, wherein the method further comprises:
and if the acceptance test result is not qualified, returning the project flow to the development stage.
5. The software quality control system is characterized by comprising a project stage flow rotor system, a quasi self-checking subsystem and a detection result auditing subsystem, wherein the project stage flow rotor system is connected with the quasi self-checking subsystem and the detection result auditing subsystem;
The quasi-self-checking subsystem is used for providing quasi-self-checking indexes and quasi-self-checking methods for the project stage flow subsystem;
The detection result auditing subsystem is used for providing detection result auditing standards for the project stage flow subsystem;
the project phase flow rotor system for performing the method of any one of claims 1-4.
6. The system of claim 5, wherein the quasi self-test subsystem includes any one or more project links of a demand, design, interface test, system smoke test, system function test, compatibility test, performance test, security test, document test, or review summary.
7. The system of claim 6, wherein the interface test comprises an interface test case, an interface test script, and an interface test report.
8. The system of claim 5, wherein the test result audit criteria includes any one or more dimensions of the quasi self-test result, a requirement specification, a test case, and a test report.
9. A software quality control apparatus, comprising:
At least one processor;
At least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method of any of claims 1-4.
10. A computer readable storage medium, in which a processor executable program is stored, characterized in that the processor executable program is for performing the method according to any of claims 1-4 when being executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311873539.3A CN117910956A (en) | 2023-12-29 | 2023-12-29 | Software quality control method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311873539.3A CN117910956A (en) | 2023-12-29 | 2023-12-29 | Software quality control method, system, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117910956A true CN117910956A (en) | 2024-04-19 |
Family
ID=90690318
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311873539.3A Pending CN117910956A (en) | 2023-12-29 | 2023-12-29 | Software quality control method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117910956A (en) |
-
2023
- 2023-12-29 CN CN202311873539.3A patent/CN117910956A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Tuteja et al. | A research study on importance of testing and quality assurance in software development life cycle (SDLC) models | |
| Hovorushchenko | Methodology of evaluating the sufficiency of information for software quality assessment according to ISO 25010 | |
| US7917895B2 (en) | Automated software testing and validation system | |
| US9710257B2 (en) | System and method to map defect reduction data to organizational maturity profiles for defect projection modeling | |
| US6601017B1 (en) | Process and system for quality assurance for software | |
| EP2778929B1 (en) | Test script generation system | |
| CN102236672B (en) | A kind of data lead-in method and device | |
| US20050204241A1 (en) | Method and device for analyzing software error | |
| CN103377120B (en) | A kind of applied program testing method and device | |
| CN107665171A (en) | Automatic regression test method and device | |
| CN102880543B (en) | For the test data supply chain manager of integration testing platform | |
| CN109977012A (en) | Joint debugging test method, device, equipment and the computer readable storage medium of system | |
| CN107451058A (en) | A kind of software development methodology and device | |
| CN103678116A (en) | Method and system for facilitating automated program testing | |
| US20190384664A1 (en) | Systems and methods for validation of test results in network testing | |
| Chopra | Software quality assurance: a self-teaching introduction | |
| CN111858377B (en) | Quality evaluation method and device for test script, electronic equipment and storage medium | |
| CN117910956A (en) | Software quality control method, system, device and storage medium | |
| CN110717305A (en) | Method, system, device and medium suitable for verifying and confirming FPGA | |
| CN115840560A (en) | Management system for software development process | |
| CN112419052B (en) | Transaction testing method, device, electronic equipment and readable storage medium | |
| CN113704123A (en) | Interface test method, device, equipment and storage medium | |
| CN115176233A (en) | Performing tests in deterministic order | |
| KR20200112477A (en) | Source code inspection system and method | |
| CN116010349B (en) | Metadata-based data checking method and device, electronic equipment and storage 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 |