CN115185811A - Automated assay collection management method and apparatus, computing device, and readable storage medium - Google Patents

Abstract

The invention discloses an automatic test receipt management method and device, a computing device and a readable storage medium. The automatic assay collection management method comprises the following steps: receiving a request of acceptance application, executing first approval, and notifying acceptance preparers to execute acceptance preparation work under the condition that a first approval result meets a condition; receiving an acceptance plan written by acceptance preparation personnel in the acceptance preparation work, and executing a second examination and approval; if the second approval result is yes, receiving an acceptance application, issuing use case compiling work contained in an acceptance plan, facilitating acceptance staff to execute use case compiling, receiving a use case compiling result, and executing a third approval; issuing an acceptance task under the condition that the third examination and approval is passed; and receiving acceptance conclusion information through the acceptance conclusion template. According to the technical scheme of the invention, the automatic management process capable of managing the starting, examining and approving, executing and result of the acceptance process and displaying the information is provided.

Description

Automated assay collection management method and apparatus, computing device, and readable storage medium

Technical Field

The invention relates to the field of automatic management of acceptance processes, in particular to an automatic acceptance management method and device, a computing device and a readable storage medium.

Background

In the software quality system, a tester can be effectively guided to carry out synchronous verification and quality confirmation in each development stage according to a software test model. At present, enterprises can effectively manage integrated tests and system test processes by using various types of test management systems, but the management of acceptance tests only has available standard management tools and templates. Since acceptance testing is primarily directed at evaluating product quality for a whole output (including programs and many product supporting documents), test management tools within the development system are not effectively supported (often tracked in terms of project or product dimensions).

The Zen channel is a domestic project management software integrating product management, project task management, use case management and Bug management, and covers the core process of research and development project management. The Zen channel separately uses products, projects and tests, has related functions of project planning, black box test management, document management, release management and the like, can be independently used, and has a form import and export function and an API (Application Programming Interface) Interface function.

The following two disadvantages are found in the actual use of the Zen channel management system by business:

the first disadvantage is that: the lack of the function of controlling the flow of the business can not make a series of flow rules according to each business, including a delivery flow, an approval flow and the like. Delivery objects generated after the internal iterative test is passed do not have a uniform template, and when a project is delivered to a client or a demonstration conference, a workflow is lacked for approval, because project delivery parts at the moment flow out of a project team, and an approver needs to approve the project delivery parts.

The second disadvantage is that: front-end pages such as case management, bug management, product management, project task management and the like are realized based on PHP language, deep secondary customization is required, the technical difficulty is high, and the front-end pages can be realized by related professionals; the rear end of the system uses the MySQL database, although the system can use an export tool to import and export, the system is not beneficial to a manager to add a working form required by design according to the actual business form and the production line; and the templates of checking and accepting equipment management, checking and accepting personnel management, checking and accepting daily newspaper management and the like are lacked, so that the unified management of the checking and accepting process is inconvenient.

Disclosure of Invention

To this end, the present invention provides an automated assay receipt management method and apparatus, a computing device and a readable storage medium in an effort to solve or at least mitigate at least one of the problems identified above.

According to one aspect of the present invention, there is provided an automated assay acceptance management method, executed in a computing device, comprising the steps of: receiving a request for accepting an application, executing a first approval, and notifying acceptance preparers to execute acceptance preparation work under the condition that a first approval result meets a condition, wherein the first approval is used for auditing whether a file provided by the request for accepting the application meets the requirement; receiving an acceptance plan written by acceptance preparation personnel in the acceptance preparation work, and executing a second examination and approval, wherein the second examination and approval is used for examining whether the acceptance plan meets the condition; receiving an acceptance application under the condition that the second approval result is yes, issuing use case compiling work contained in an acceptance plan, facilitating an acceptance staff to execute use case compiling, receiving a use case compiling result, and executing a third approval, wherein the third approval is used for verifying whether the use case compiling meets the condition; issuing an acceptance task under the condition that the third examination and approval is passed; and receiving acceptance conclusion information through an acceptance conclusion template, wherein the acceptance conclusion information comprises a final test conclusion.

According to another aspect of the present invention, there is provided an automated acceptance management system, located in a computing device, comprising: the first approval module is used for receiving the request of the acceptance application, executing first approval and notifying acceptance preparers to execute acceptance preparation work under the condition that a first approval result meets the condition, wherein the first approval is used for auditing whether the file provided by the request of the acceptance application meets the requirement; the second approval module is used for receiving an acceptance plan written by acceptance preparation personnel in the acceptance preparation work and executing second approval, wherein the second approval is used for auditing whether the acceptance plan meets the condition; the third examination and approval module is used for receiving the acceptance application, issuing case compiling work contained in the acceptance plan, facilitating the acceptance staff to execute case compiling, receiving case compiling results and executing third examination and approval under the condition that the second examination and approval result is positive, wherein the third examination and approval is used for examining whether the case compiling meets the condition or not; the task issuing module is used for issuing an acceptance task under the condition that the third examination and approval is passed; and the acceptance conclusion generating module is used for receiving the acceptance conclusion information through the acceptance conclusion template.

According to another aspect of the present invention, there is provided a computing device comprising: at least one processor and a memory storing program instructions; the program instructions, when read and executed by the processor, cause the computing device to perform the automated assay management method described above.

According to another aspect of the present invention, there is provided a readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the above-described automated assay receipt management method.

According to the technical scheme of the invention, the automatic management process capable of managing the starting, examining and approving, executing and result of the acceptance process and displaying the information is provided, and the project acceptance team and related personnel can be effectively helped to know the progress and conclusion of the acceptance.

Further, a demand management system and an after-sales feedback system of an enterprise can be docked, so that use evaluation and feedback of external personnel on the product can be continuously tracked, and use scenes can be continuously collected to perfect acceptance test cases of the product.

Drawings

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings, which are indicative of various ways in which the principles disclosed herein may be practiced, and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description read in conjunction with the accompanying drawings. Throughout this disclosure, like reference numerals generally refer to like parts or elements.

FIG. 1 shows a schematic diagram of a computing device 100 according to an embodiment of the invention;

fig. 2 shows a flow diagram of an automated assay acceptance management method 200 according to an embodiment of the invention.

FIG. 3 illustrates an approval list created according to an embodiment of the present invention.

FIG. 4 illustrates a user scenario requirements analysis page created in accordance with an embodiment of the present invention.

FIG. 5 illustrates a template system diagram that may be constructed in accordance with a method 200 of an embodiment of the present invention.

Fig. 6 shows a business workflow for building an acceptance pipeline through the Apaas platform.

Fig. 7 shows a schematic block diagram of an automated acceptance management system according to an embodiment of the invention.

Fig. 8 shows an overall architecture diagram of a solution according to an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Aiming at the problem that the acceptance test lacks a unified standard flow, the invention provides an automatic test acceptance management method and device, a computing device and a readable storage medium, and provides an automatic management method capable of managing the starting, examining and approving, executing and result of the acceptance test and displaying information.

The automated acceptance management method of the present invention is executed in a computing device. The computing device may be any device with storage and computing capabilities, and may be implemented as, for example, a server, a workstation, or the like, or may be implemented as a personal computer such as a desktop computer or a notebook computer, or may be implemented as a terminal device such as a mobile phone, a tablet computer, a smart wearable device, or an internet of things device, but is not limited thereto.

FIG. 1 shows a schematic diagram of a computing device 100, according to one embodiment of the invention. It should be noted that the computing device 100 shown in fig. 1 is only an example, and in practice, the computing device for implementing the automatic assay collection management method of the present invention may be any type of device, and the hardware configuration thereof may be the same as the computing device 100 shown in fig. 1 or different from the computing device 100 shown in fig. 1. In practice, the computing device for implementing the automatic assay collection management method of the present invention may add or delete the hardware components of the computing device 100 shown in fig. 1, and the present invention does not limit the specific hardware configuration of the computing device.

As shown in FIG. 1, in a basic configuration 102, a computing device 100 typically includes a system memory 106 and one or more processors 104. A memory bus 108 may be used for communication between the processor 104 and the system memory 106.

Depending on the desired configuration, the processor 104 may be any type of processing, including but not limited to: a microprocessor (μ P), a microcontroller (μ C), a Digital Signal Processor (DSP), or any combination thereof. The processor 104 may include one or more levels of cache, such as a level one cache 110 and a level two cache 112, a processor core 114, and registers 116. The example processor core 114 may include an Arithmetic Logic Unit (ALU), a Floating Point Unit (FPU), a digital signal processing core (DSP core), or any combination thereof. The example memory controller 118 may be used with the processor 104, or in some implementations the memory controller 118 may be an internal part of the processor 104.

Depending on the desired configuration, system memory 106 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The physical memory in the computing device is usually referred to as volatile memory RAM, and data in the disk needs to be loaded into the physical memory to be read by the processor 104. System memory 106 may include an operating system 120, one or more applications 122, and program data 124. In some implementations, the application 122 can be arranged to execute instructions on an operating system with program data 124 by one or more processors 104. Operating system 120 may be, for example, linux, windows, etc., which includes program instructions for handling basic system services and performing hardware dependent tasks. The application 122 includes program instructions for implementing various user-desired functions, and the application 122 may be, for example, but not limited to, a browser, instant messenger, a software development tool (e.g., an integrated development environment IDE, a compiler, etc.), and the like. When the application 122 is installed into the computing device 100, a driver module may be added to the operating system 120.

When the computing device 100 is started, the processor 104 reads program instructions of the operating system 120 from the memory 106 and executes them. Applications 122 run on top of operating system 120, utilizing interfaces provided by operating system 120 and the underlying hardware to implement various user-desired functions. When the user starts the application 122, the application 122 is loaded into the memory 106, and the processor 104 reads the program instructions of the application 122 from the memory 106 and executes the program instructions.

The computing device 100 also includes a storage device 132, the storage device 132 including removable storage 136 and non-removable storage 138, the removable storage 136 and the non-removable storage 138 each connected to the storage interface bus 134.

Computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (e.g., output devices 142, peripheral interfaces 144, and communication devices 146) to the basic configuration 102 via the bus/interface controller 130. The example output device 142 includes a graphics processing unit 148 and an audio processing unit 150. They may be configured to facilitate communication with various external devices, such as a display or speakers, via one or more a/V ports 152. Example peripheral interfaces 144 may include a serial interface controller 154 and a parallel interface controller 156, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 158. An example communication device 146 may include a network controller 160, which may be arranged to facilitate communications with one or more other computing devices 162 over a network communication link via one or more communication ports 164.

A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media, such as carrier waves or other transport mechanisms, in a modulated data signal. A "modulated data signal" may be a signal that has one or more of its data set or its changes made in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or private-wired network, and various wireless media such as acoustic, radio Frequency (RF), microwave, infrared (IR), or other wireless media. The term computer readable media as used herein may include both storage media and communication media.

In computing device 100 according to the present invention, application 122 includes instructions for performing automated assay acceptance management method 200 of the present invention, which may instruct processor 104 to perform automated assay acceptance management method 200 of the present invention to manage the initiation, approval, execution, result presentation, and the like of the overall acceptance through an automated acceptance management process.

Fig. 2 shows a flow diagram of an automated acceptance management method 200 according to one embodiment of the invention. Method 200 is performed in a computing device, such as computing device 100 described above, for implementing automated process management of acceptance. Method 200 is described with respect to bank acceptance as an example, however, it should be understood that method 200 is not limited to application in the particular context of bank acceptance. In this particular example, the bank commissions a software development company to develop certain software. After the software development company completes the development work, the bank is requested to perform an acceptance work to check the completion of the work. The acceptance method may be stored in the application 122 in a program written by a programmer (in java, C language, etc.), or may be constructed by a zero-code application building platform, such as an Apaas application building platform.

Apaas (application Platform as a Service) can provide an environment for rapid development, and a user can complete development, test and deployment of applications within several hours and can adjust or update at any time. For convenience of describing the present invention, the platform will be taken as an example for illustration, however, it should be understood that the present invention is not limited thereto, and as described above, the operation of each step can be implemented by those skilled in the art by using any suitable language programming, and each workflow module required by the acceptance method can be deployed by using other platforms.

The method 200 is described below with reference to fig. 2. As shown in fig. 2, method 200 includes:

step S210, receiving a request for acceptance application, executing a first approval, and notifying acceptance preparers to execute acceptance preparation work when a first approval result satisfies a condition.

In the above example, the party initiating the acceptance request is the interface person of the software development company, for example, a project manager or a person with operation authority may click on the "reserved acceptance" button, and an information confirmation box may pop up on the platform. The interface person may enter the corresponding product name and current acceptance stage therein and begin to walk through the acceptance appointment workflow upon confirmation.

After receiving the reservation request of the acceptance application through the method, the bank side can execute the first approval. The first approval is used for checking whether the file provided by the initiator meets the condition. If the content provided meets the requirements, the subsequent work is started. This first approval may be performed automatically by the platform Apaas executing the method 200 or manually. In the case of an automatic execution of the method, it is necessary to set in advance the approval criteria, such as: whether the required completion degree reaches 100%, whether a test report is contained, and whether a complete matching document is submitted.

In the event that the first approval meets the condition, the platform may automatically notify acceptance preparers, such as the bank's interface person. The acceptance preparer performs acceptance preparation work such as: writing an acceptance plan, communicating acceptance standards, preparing test cases, calling human resources, preparing peripheral equipment of the machine and the like. The written acceptance plan may include activities such as breaking down by time: for example, a plan is written for the first week, a concrete case is written for the second week, a test is executed for the third week, and a report is written for the fourth week. Each process needs to define roles (who is the executing agent), what conditions need to be met (approval conditions) to execute the next flow (flow). In the case of using the workflow and worksheet functions of the Apaas application platform to build an acceptance test management system, the states of the peripherals and the like may be registered in the platform with reference to the device template of the platform, or may be directly filled in the computing system. In addition to peripherals, human situations (junior high level) and input/write of use cases can be managed in the platform in a unified manner.

S220, receiving an acceptance plan written by acceptance preparation personnel in the acceptance preparation work, and executing a second examination and approval, wherein the second examination and approval is used for examining whether the acceptance plan meets the conditions.

In practice, after the acceptance preparer is ready to accept the plan, the "submit" may be clicked on, and a notification confirming the approval may then be sent to the approver, with the approver clicking "pass" or "fail" to determine whether the audit is passed.

This step is performed because after the acceptance preparer is ready to accept the work (e.g., it takes a week to write the plan), it is necessary to approve whether the preparation work satisfies the condition. The approval process may be automatically executed by the platform to determine whether the acceptance preparation process meets the predetermined conditions, which may be set in advance, such as whether each planned step is complete, whether the execution subject is correct, whether the corresponding approval conditions are set, and the like. In addition, the approval can be performed by another party (e.g., a leader, a person in charge of the direct user of the product, etc.), and the approval can be performed by referring to the experience of the person.

And S230, receiving an acceptance application and issuing use case compiling work contained in an acceptance plan under the condition that the second approval result is yes, so that the acceptance personnel can conveniently execute use case compiling.

In practice, after the internal project research and development test is finished, the checking and accepting applicant can click a 'formal checking and accepting application' button arranged on the platform, the platform can pop up an information confirmation interface, the applicant can fill in corresponding information and application files according to the prompt information, and the submitting button can be clicked after the completion of the filling. The background workflow may send the electronic flow carrying the application information to the acceptance worksheet system. In subsequent steps, the acceptance work order system may create the various work orders (templates) mentioned later, facilitating the worker or platform to automatically populate the templates with relevant information, such as equipment, personnel, daily reports, acceptance conclusions, etc.

Through this step, the plan decomposition is issued to the employee. The employee execution plan includes writing a use case, preparing an environment, etc. as per the plan mentioned in the detailed description of step S210.

And S240, receiving the case writing result and executing a third examination and approval. Similarly, the third approval operation may be automatically executed by the platform to determine whether the case writing meets the predetermined condition, and the condition may be set in advance, for example, whether the number of test cases meets the condition, whether there is a format error, and the like. In addition, the approval can be performed by another party (e.g., a leader, a person in charge of the direct user of the product, etc.), and the approval can be performed by referring to the experience of the person.

According to the method, an approval workflow is established according to the approval level in an enterprise, the platform performs approval according to the approval conditions set in advance, or an auditor performs approval on form problems and obvious substantial problems in an application file, approval opinions are filled in an approval page, and an approval pass or reject button is clicked. After the examination and acceptance information is passed, a work order tracking the examination and acceptance information is automatically created in the examination and acceptance work order system, and the examination and approval opinions are automatically recorded in an examination and approval list according to the workflow. The approval work of each link can be automatically recorded in an approval list, as shown in fig. 3, the approval list can contain approval opinions, approvers, approval links and links. The link represents which operation node is located, and the examination and approval link represents which job related personnel execute the examination and approval task. Wherein the approval link and the approver can be combined into one piece of information. In addition, an automatic number can be automatically generated for each approval opinion according to the workflow.

And S250, issuing an acceptance task to an acceptance staff under the condition that the third examination is passed.

The acceptance personnel can then perform an acceptance test. Acceptance testing is performed in a test environment, which proceeds as follows: firstly, executing 1) smoking test, wherein the smoking test refers to obtaining a delivery piece submitted for acceptance check from the version management system, and executing a small amount of test to judge whether the starting condition of the acceptance check is met. The purpose of the smoke test is to perform a small number of tests to check whether the basic conditions of the test are met, which may be defined in advance, and may include, for example, that the system can be started normally, that pages can be displayed normally, that modules can respond normally, and the like. If the smoke test fails, the subsequent high-volume tests do not need to be carried out, and the possible problems of the system need to be solved firstly. And after the smoking test is passed, executing 2) formal test, namely executing a formal full-amount acceptance test case according to an acceptance test plan.

In an example of bank verification, tests may be performed according to software requirements specifications, and acceptance tests may include functional tests, performance tests, reliability tests, compatibility tests, and the like. During or after the test, relevant information such as equipment, personnel, use cases, defects (bugs), daily reports and the like can be recorded. The recording process of such information may be: the platform is used to design equipment templates, personnel templates, use case templates, defect (Bug) templates, daily templates, etc. by itself to fill in relevant information. Each template can be designed by self, and the content can be defined by self. The platform can be in butt joint with a related system, and related data is obtained through a workflow and automatically filled and written into the corresponding template. The equipment template can record relevant information of equipment for acceptance testing, the personnel template records relevant information of acceptance personnel, the case template records acceptance testing cases, the defect template can comprise an online defect template and an acceptance defect template, the online defect template is used for recording relevant information of defects fed back by a demand management system and the like, the acceptance defect template is used for recording relevant information of the defects found in the acceptance process, and the daily report template is used for recording the condition of executing the testing every day and can comprise testing completion degree, next-step work plan and the like.

During execution, a check-out procedure information page may be generated, which may contain the project name to be filled in, the check-out group length, the check-out conclusion, the check-out start/end time, etc. Some of which, such as the name of the item, may directly call the name in the item management system.

And S260, receiving acceptance conclusion information of an acceptance person executing an acceptance task through the acceptance conclusion template.

The content of the acceptance conclusion template may be customized, such as may include: start time, end time, acceptance conclusion, acceptance personnel, problems discovered, etc. The acceptance conclusion information can be automatically received according to the feedback of the test system. The relevant content may also be filled in on the template by acceptance testers. In practice, the "complete test" button may be clicked after the acceptance is over, and the acceptance conclusion template is filled in by the tester.

The acceptance conclusion information is a general conclusion, and a final product quality conclusion is given. More detailed acceptance test reports may also be given for each test. The platform provides the acceptance test report template, and after the test is finished, the test time, the test content and the test conclusion of each test are filled.

Enterprises generally use an item management system and a demand management system to perform functions of demand management, task management, use case management and defect management, wherein the demand management system and the after-sales management system are IT management systems of companies, are provided with secondary development interfaces, and can acquire quality feedback data for product delivery pieces by reading and using information of internal databases. Feedback information of online defects (online bugs) of a product may be obtained from a product demand management system and an after-market feedback system. The demand management system and the after-sales feedback system record the demands or problems reflected by the users, and can import the defects possibly confirmed in the demand management system into the acceptance management system by filtering the defects.

Specifically, after the product is released, according to the feedback of the enterprise technology support system and the demand management system, when the feedback information is confirmed to be the defect of the product, the defect information can be supplemented into the acceptance case template. The acceptance case template is a case template for guiding a tester to carry out functional tests according to the steps.

Before the user scene requirement analysis page is added into the acceptance case template, a user scene requirement analysis page as shown in fig. 4 can be automatically created, and corresponding feedback information is automatically input into the page. The acceptance personnel can supplement the acceptance scene according to the information. The user scene demand analysis page refers to a page for analyzing and accepting online defects by a tester, scene analysis is performed through the page (whether the involved bugs meet the current use scene, whether missed scenes exist or not and the like are judged by the tester), which cases need to be supplemented are judged, and then whether an acceptance case template is input or not is determined.

Therefore, the method 200 may further include the steps of: receiving feedback information from a product demand management system; confirming whether the feedback information represents a product defect or not, and if so, creating a user scene demand analysis page to execute scene analysis on the feedback information by an acceptance staff; and receiving a positive analysis result of the acceptance personnel, and supplementing the feedback information into the acceptance case template.

One of the problems in the prior art that project management systems perform acceptance testing is: the acceptance test is mainly aimed at the specific use scene of a client, the use feedback or on-line defect (Bug) feedback of the client to a product is often transmitted to an internal demand management system or an after-sales management system, different management modes exist between data of the two systems, and effective information which is beneficial to the acceptance test needs to be extracted according to a uniform template aiming at the information of the two systems, so that an acceptance team can supplement and perfect an acceptance case set in time.

According to the technical scheme, the technical problem is solved, the feedback information from the demand management system or the after-sales management system can be supplemented into the acceptance case template, and selective supplementation can be performed based on analysis of a tester.

The following benefits may be obtained using a platform such as Apaas: in a first aspect, a diversified data management table template can be zero-code built through a visualized data control. By easily constructing a worksheet template required by the acceptance link, business object data can be collected, stored and managed, for example, corresponding test process data can be automatically acquired according to cases, defect related fields and acceptance equipment management fields in an enterprise project management platform, and the test data can be displayed on a detailed page of a worksheet. Meanwhile, the table based on the template supports the functions of import and export, and a user can edit an imported/exported file by using an Excel tool to obtain what you see is what you get. The template system constructed is shown in fig. 5.

In the second aspect, by utilizing the basic public capability of the Apaas platform, the business workflow of the project development result acceptance pipeline can be constructed. The building process is shown in fig. 6, wherein the activities in the process are analyzed and disassembled according to the business process (610), and these activities are the activities stated in the above steps and/or required to be approved, such as writing a plan in the first week, writing a concrete case in the second week, executing a test in the third week, and writing a report in the fourth week. Generally speaking, these activities have a linked logical order or causal relationship between them. Tasks, approval roles, and flow rules in the workflow are then defined (620). In the case that the process is expected to be automatically executed, it may be defined that the approval roles are all machines or platforms, and the circulation rule is a condition that each approval passes. The workflow execution process is then executed and monitored 630, and the acceptance output information is finally presented 640. By building the whole workflow in this way, the method 200 can be automatically completed by the platform, and the process of acceptance management automation is realized. The process may eventually yield some information to the internal or external user.

The project management system in the prior art mainly has the following problems in the aspects of acceptance test management: project delivery is lack of standardized flow and check list from successful development to overall acceptance, and delivery management, acceptance process management and product quality report management are managed by manual form making, task board making and mail attachment. The consignment passes from the completion of project development to the complete acceptance, the related links and information are more, and the excessive dependence on manual management can directly influence the acceptance efficiency and the customer satisfaction degree of the consignment. There is a need for an automated templated management tool for project acceptance testing that can interface with a project management system. When the project research and development is finished and the project acceptance process is entered, the tool can display and control related project process input, can synchronously display acceptance process output information after the acceptance link is finished, and dynamically display information such as test progress, product quality and the like of product acceptance in real time in the acceptance process.

According to the technical scheme of the invention, the method for managing the user acceptance test can uniformly and effectively manage various information in the acceptance test, can be embedded into an automatic research and development test system of an enterprise at a lower cost, can greatly reduce the repeated labor of the acceptance test work by using a work template and a workflow which are customized in advance, enables acceptance personnel to focus on quality detection and valuable business scene construction, can manually export data statistics in the test process, can manually formulate a multi-dimensional statistical report according to the exported data, and is convenient for subsequent quality analysis.

According to the embodiment of the invention, the automatic acceptance management system is also provided. Fig. 7 shows a schematic block diagram of the automated acceptance management system. As shown in fig. 7, the system includes:

the first approval module 710 is configured to receive a request for acceptance application, execute the first approval, and notify acceptance preparers to execute acceptance preparation work when a result of the first approval satisfies a condition.

And a second approval module 720, configured to receive an acceptance plan written by the acceptance preparation staff in the acceptance preparation work, and execute a second approval, where the second approval is used to check whether the acceptance plan meets the condition.

And the use case compiling module 730 is used for receiving the acceptance application and issuing the use case compiling work contained in the acceptance plan under the condition that the second approval result is yes, so that the acceptance personnel can conveniently execute the use case compiling.

And a third approval module 740 configured to receive the use case writing result and execute a third approval.

And the task issuing module 750 is configured to issue an acceptance task to the acceptance staff when the third approval is passed.

And the acceptance conclusion generating module 760 is used for receiving acceptance conclusion information of the acceptance personnel executing the acceptance task through the acceptance conclusion template.

The acceptance conclusion information is a general conclusion, and gives a final product quality conclusion. More detailed acceptance test reports may also be given for each test. The platform provides the acceptance test report, and after the test is finished, the test time, the test content and the test conclusion of each test are filled. Accordingly, the system may further include a test report generation module to receive test report information through the test report template, the test report information including a test conclusion for each test.

The system also comprises a use case supplement module used for receiving feedback information from the product demand management system; confirming whether the feedback information represents a product defect or not, and if so, creating a user scene demand analysis page to execute scene analysis on the feedback information by an acceptance staff; and receiving a positive analysis result of the acceptance personnel, and supplementing the feedback information into the acceptance case template.

FIG. 8 shows the overall design of the system of the present invention, with the solid portion being the content within the system and the dashed portion being the existing management system of the enterprise. After the applicant initiates the acceptance application through the project management system, the system can know that an acceptance task exists, so that a project acceptance work order (a work order for initiating the acceptance application) can be created. The test management system is used for managing test cases. If some use cases are different from those stored in the system, the data can be exported in the form of an interface. The work order in the acceptance process is the template of the equipment, personnel, daily report, acceptance conclusion and the like.

According to the technical scheme of the invention, the system for managing the user acceptance test can uniformly and effectively manage various information in the acceptance test, can be embedded into an automatic research and development test system of an enterprise at a lower cost, can greatly reduce the repeated labor of the acceptance test work by using a work template and a workflow which are customized in advance, enables acceptance personnel to focus on quality detection and valuable business scene construction, can manually export data statistics in the test process, can manually formulate a multi-dimensional statistical report according to the exported data, and is convenient for subsequent quality analysis.

The various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present invention, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U.S. disks, floppy disks, CD-ROMs, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.

In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Wherein the memory is configured to store program code; the processor is configured to execute the automated assay collection management method of the present invention according to instructions in the program code stored in the memory.

By way of example, and not limitation, readable media may comprise readable storage media and communication media. Readable storage media store information such as computer readable instructions, data structures, program modules or other data. 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. Combinations of any of the above are also included within the scope of readable media.

In the description provided herein, algorithms and displays are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with examples of this invention. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. It will be appreciated by a person skilled in the art that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment, or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into multiple sub-modules.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. Additionally, some of the embodiments are described herein as a method or combination of method elements that can be implemented by a processor of a computer system or by other means of performing the described functions. A processor having the necessary instructions for carrying out the method or method elements thus forms a means for carrying out the method or method elements. Further, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is used to implement the functions performed by the elements for the purpose of carrying out the invention.

As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this description, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter.

Claims (10)

1. An automated assay collection management method comprising the steps of:

receiving a request for accepting an application, executing a first approval, and notifying acceptance preparers to execute acceptance preparation work under the condition that a first approval result meets a condition, wherein the first approval is used for auditing whether a file provided by the request for accepting the application meets the requirement;

receiving an acceptance plan written by acceptance preparation personnel in the acceptance preparation work, and executing a second examination and approval, wherein the second examination and approval is used for examining whether the acceptance plan meets the condition;

under the condition that the second approval result is yes, receiving an acceptance application, and issuing use case compiling work contained in an acceptance plan so as to facilitate the acceptance staff to execute use case compiling;

receiving a case writing result, and executing a third examination and approval, wherein the third examination and approval is used for examining and verifying whether the case writing meets the condition;

under the condition that the third examination and approval is passed, issuing an acceptance task to an acceptance staff;

and receiving acceptance conclusion information of an acceptance person executing an acceptance task through an acceptance conclusion template, wherein the acceptance conclusion information comprises a final test conclusion.

2. The automated assay acceptance management method of claim 1, wherein at least one of the first approval, the second approval, and the third approval is performed by an approval person.

3. The automated assay acceptance management method according to claim 1 or 2, further comprising:

receiving feedback information from a product demand management system;

confirming whether the feedback information represents a product defect or not, and if so, creating a user scene demand analysis page to execute scene analysis on the feedback information by an acceptance staff;

and receiving a positive analysis result of the acceptance personnel, and supplementing the feedback information into an acceptance case template.

4. The automated assay acceptance management method of any one of claims 1-3, further comprising:

and generating an approval list, wherein the approval list comprises approval opinions, approvers and links, and the links are used for identifying which of the first approval, the second approval and the third approval is currently located.

5. The automated assay acceptance management method of any one of claims 1-4, further comprising:

respectively receiving the following related information through an equipment template, a personnel template, an acceptance defect template, an acceptance case template, a daily report template and an acceptance process template: and inspecting and accepting the test equipment, personnel, defects generated in the inspection and acceptance process, test cases, test progress and the inspection and acceptance process.

6. The automated assay collection management method of claim 5, further comprising:

and responding to an external indication, and exporting at least one of the acceptance conclusion template, the equipment template, the personnel template, the acceptance defect template, the acceptance case template, the daily report template and the acceptance process template.

7. An automated assay collection management system comprising:

the first approval module is used for receiving the request of the acceptance application, executing first approval and notifying acceptance preparers to execute acceptance preparation work under the condition that a first approval result meets the condition, wherein the first approval is used for auditing whether the file provided by the request of the acceptance application meets the requirement;

the second approval module is used for receiving an acceptance plan written by acceptance preparation personnel in the acceptance preparation work and executing second approval, wherein the second approval is used for auditing whether the acceptance plan meets the condition;

the case compiling module is used for receiving the acceptance application and issuing case compiling work contained in the acceptance plan under the condition that the second approval result is yes, so that the acceptance personnel can conveniently execute case compiling,

the third examination and approval module receives the case writing result and executes third examination and approval, wherein the third examination and approval is used for examining whether the case writing meets the condition;

the task issuing module is used for issuing an acceptance task to the acceptance staff under the condition that the third examination and approval is passed;

and the acceptance conclusion generating module is used for receiving acceptance conclusion information of the acceptance personnel executing the acceptance tasks through the acceptance conclusion template.

8. The automated assay collection management system of claim 7, further comprising:

the use case supplementing module is used for receiving feedback information from the product demand management system; confirming whether the feedback information represents a product defect or not, and if so, creating a user scene demand analysis page to execute scene analysis on the feedback information by an acceptance staff; and receiving a positive analysis result of the acceptance personnel, and supplementing the feedback information into the acceptance case template.

9. A computing device, comprising:

at least one processor and a memory storing program instructions;

the program instructions, when read and executed by the processor, cause the computing device to perform the automated assay acceptance management method of any one of claims 1-6.

10. A readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the automated assay receipt management method of any one of claims 1-6.

Images