CN113495548A - Test scheduling system and method - Google Patents
Test scheduling system and method Download PDFInfo
- Publication number
- CN113495548A CN113495548A CN202010254998.3A CN202010254998A CN113495548A CN 113495548 A CN113495548 A CN 113495548A CN 202010254998 A CN202010254998 A CN 202010254998A CN 113495548 A CN113495548 A CN 113495548A
- Authority
- CN
- China
- Prior art keywords
- test
- task
- management platform
- platform
- execution
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 631
- 238000000034 method Methods 0.000 title claims abstract description 16
- 230000010354 integration Effects 0.000 claims abstract description 41
- 238000004891 communication Methods 0.000 claims abstract description 8
- 238000011161 development Methods 0.000 claims description 8
- 230000002085 persistent effect Effects 0.000 claims description 7
- 238000011990 functional testing Methods 0.000 claims description 6
- 238000012790 confirmation Methods 0.000 claims 1
- 238000007726 management method Methods 0.000 description 58
- 238000012163 sequencing technique Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 239000012141 concentrate Substances 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 230000033764 rhythmic process Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a test task scheduling system and a method, wherein the test task scheduling system comprises: the system comprises a continuous integration test platform constructed based on Jenkins, a test demand management platform constructed based on Redmine and a model and code management platform constructed based on SVN, wherein the test demand management platform is used for configuring the authority of a test control end and a test execution end which are in communication connection with the test demand management platform; the model and code management platform is used for providing a software model or code to be tested; the continuous integration test platform is used for acquiring the test tasks and the test priorities of the test execution ends from the test requirement management platform and generating an automatic test task scheduling table; and calling a software model or code to be tested from the model and code management platform, and starting a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table. The invention reduces the influence caused by manual intervention and greatly improves the testing efficiency.
Description
Technical Field
The invention belongs to the technical field of automobile function testing, and particularly relates to a testing and scheduling system and method.
Background
In the functional test of the vehicle control unit, commonly used test methods include an MIL (Model In Loop), an SIL (Software In Loop), and an HIL (Hardware In Loop). Traditional test flow is after receiving the functional requirement, the demand engineer carries out the demand and decomposes, software engineer carries out the software modeling, integrated engineer carries out the software integration, mark the engineer and mark, test engineer tests and feedback test result, often a test engineer will be responsible for the test of a plurality of functions of a plurality of projects in this in-process, how to rationally and effectively arrange the work of test team member according to the progress and the priority of a plurality of projects, optimize work flow, promote work efficiency, become a big popular research topic.
In the traditional MIL/SIL test task scheduling, a test supervisor generally makes a decision in a conference mode according to indexes such as test resources, workload of testers, test tasks and the like. However, once any link has a problem (the concurrent development of multiple projects is likely to occur), the scheduling of the test tasks is disordered if the whole test chain is not connected, so that the efficiency of the whole test team is reduced, and limited test resources are wasted.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a test scheduling system and method for effectively improving test efficiency.
In order to solve the above technical problem, the present invention provides a test task scheduling system, including: a continuous integration test platform constructed based on Jenkins, a test requirement management platform constructed based on Redmine, and a model and code management platform constructed based on SVN,
the test requirement management platform is used for configuring the authority of a test control end and a test execution end which are in communication connection with the test requirement management platform, so that the test control end distributes test tasks to the test execution ends according to the total test requirement and sets the test priority of the test tasks;
the model and code management platform is used for providing a software model or code to be tested;
the continuous integration test platform is used for acquiring the test tasks and the test priorities of the test execution ends from the test requirement management platform and generating an automatic test task scheduling table; and calling a software model or code to be tested from the model and code management platform, and starting a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table.
The test requirement management platform is further configured to establish a test task allocation template of the test control end and a test task execution template of the test execution end, respectively, where the test task allocation template includes key fields: project, development stage, task to be tested, tester, priority; the test task execution template comprises the following key fields: the SVN version number, the test engineering path, the test state, the test result, the father task number, the test mode and the automatic test starting time period of the software to be tested.
The test requirement management platform is further configured to set an authority of a test sub-control end, which is in communication connection with the test requirement management platform and is located at an intermediate level between the test control end and the test execution end, and establish a test task sub-distribution template, where the test task sub-distribution template includes key fields: project test state, function priority to be tested, scheduled test completion time and parent task number.
The continuous integration test platform obtains the test tasks and the test priorities of the test execution ends by reading the test task allocation template, the test task sub-allocation template and the test task execution template, and generates an automatic test task scheduling table according to the test tasks and the test priorities, wherein in the automatic test task scheduling table, the test priorities comprise project priorities and function priorities which are respectively represented by numerical values, and the numerical ranges of the project priorities and the function priorities are both 0-100.
When the continuous integrated test platform tests according to the automatic test task scheduling table, the continuous integrated test platform is carried out in a plurality of projects according to the project priority values from small to large, and the continuous integrated test platform is carried out in the same project according to the function priority values from small to large.
The continuous integration test platform is provided with an administrator account, and the account numbers of the test control end, the test sub-control end and the test execution end are arranged in the administrator account through Jenkins plug-ins.
The continuous integration test platform is specifically used for calling a test case developed by a test execution end through a test engineering path in the test task execution template when an automatic test starting time period is reached, and starting a model in-loop test tool or a software in-loop test tool to test.
After a certain test task is completed, the continuous integration test platform sets the test state in the test task execution template to be completed on the test requirement management platform, and starts the next test task on the automatic test task scheduling table until all test tasks are completed or the automatic test time period is exceeded.
The continuous integration test platform is also provided with a receiving address of a test result receiving end, and the receiving address is used for sending the test result to the test result receiving end after the test is finished.
The continuous integrated test platform is also used for freezing the test priority of the test task beyond the automatic test time period and putting the test priority into the next automatic test task scheduling table for sequencing.
The test execution end confirms the test result according to the test task in the finished state, sets the test state in the test task execution template to be closed on the test requirement management platform after the test is finished, and releases the corresponding function priority at the same time; and if all the functional tests of a certain project are completed, setting the test states in all the test task execution templates of the project to be closed, and simultaneously releasing the corresponding project priority.
The invention also provides a test task scheduling method, which is implemented by a continuous integration test platform constructed based on Jenkins, a test demand management platform constructed based on Redmine and a model and code management platform constructed based on SVN, and comprises the following steps:
the continuous integration test platform acquires the test tasks and the test priorities of the test execution ends from the test requirement management platform and generates an automatic test task scheduling table; the test requirement management platform is provided with a test control end and a test execution end which are in communication connection with the test requirement management platform, and the test control end distributes test tasks to the test execution ends according to the total test requirement and sets the test priorities of the test tasks;
and the continuous integration test platform calls a to-be-tested software model or code from the model and code management platform, and starts a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table.
The test task scheduling method further comprises the following steps:
the test requirement management platform respectively establishes a test task allocation template of a test control end and a test task execution template of a test execution end, wherein the test task allocation template comprises key fields as follows: project, development stage, task to be tested, tester, priority; the test task execution template comprises the following key fields: the SVN version number, the test engineering path, the test state, the test result, the father task number, the test mode and the automatic test starting time period of the software to be tested.
When the automatic test starting time period is reached, the continuous integration test platform calls a test case developed by a test execution end through a test engineering path in the test task execution template, and starts a model in-loop test tool or a software in-loop test tool to test.
After a certain test task is completed, the continuous integration test platform sets the test state in the test task execution template to be completed on the test requirement management platform, and starts the next test task on the automatic test task scheduling table until all test tasks are completed or the automatic test time period is exceeded.
And the continuous integration test platform sends the test result to a test result receiving end after the test is finished.
And the continuous integrated test platform freezes the test priority of the test task exceeding the automatic test time period and puts the test priority into a next automatic test task scheduling table for sequencing.
The test execution end confirms the test result according to the test task in the finished state, sets the test state in the test task execution template to be closed on the test requirement management platform after the test is finished, and releases the corresponding function priority at the same time; and if all the functional tests of a certain project are completed, setting the test states in all the test task execution templates of the project to be closed, and simultaneously releasing the corresponding project priority.
The embodiment of the invention has the following beneficial effects: after the test tasks are determined, the test supervisor and the test manager can completely know the test rhythm only by performing task allocation according to the priority, a test engineer can control the test process more freely according to the test tasks and only needs to concentrate on test preparation work such as development of test cases and the like and test result analysis, the test tasks are automatically executed according to the priority sequence, the test planning problem does not need to be considered, the influence caused by manual intervention is reduced, and the test efficiency is greatly improved; when an emergency task occurs, high-priority scheduling can ensure that the existing test task is not influenced or is influenced a little;
the invention can construct an MIL/SIL test task scheduling system by setting different role authorities of a test demand management platform based on a small amount of script calling, so that test work can be reasonably distributed and scheduled in week units, and multi-task sequential execution can be carried out in idle time by using a continuous integrated test platform.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a test task scheduling system according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments refers to the accompanying drawings, which are included to illustrate specific embodiments in which the invention may be practiced.
Jenkins is an open source software project, is a continuous integration tool developed based on Java, is used for monitoring continuous and repeated work, and aims to provide an open and easy-to-use software platform to enable continuous integration of software to be possible; redmine is web-based Project management software developed by Ruby, is a set of cross-platform Project management system developed by an ROR framework, organizes members, tasks (problems), documents, discussions and various forms of resources together in the form of 'Project', participates in updating the contents of tasks, documents and the like to promote the progress of projects, and simultaneously, the system automatically reports the progress of projects to the members by utilizing a time clue and various dynamic report forms; the SVN is an open source code version control system, realizes shared resources by adopting efficient management of a branch management system, and finally realizes centralized management. In the embodiment of the invention, according to the characteristics of Jenkins, Redmine and SVN that sources are open and free, Jenkins and plug-ins of various tools can construct an MIL/SIL test task scheduling system by setting different role authorities of Redmine based on a small amount of script calling forms, so that test work can be reasonably distributed and scheduled.
Referring to fig. 1, a test task scheduling system according to an embodiment of the present invention includes: a continuous integration test platform constructed based on Jenkins, a test requirement management platform constructed based on Redmine, and a model and code management platform constructed based on SVN,
the test requirement management platform is used for configuring the authority of a test control end and a test execution end which are in communication connection with the test requirement management platform, so that the test control end distributes test tasks to the test execution ends according to the total test requirement and sets the test priority of the test tasks;
the model and code management platform is used for providing a software model or code to be tested;
the continuous integration test platform is used for acquiring the test tasks and the test priorities of the test execution ends from the test requirement management platform and generating an automatic test task scheduling table; and calling a software model or code to be tested from the model and code management platform, and starting a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table.
Specifically, the test requirement management platform is further configured to respectively establish a test task allocation template of the test control end and a test task execution template of the test execution end, where the test task allocation template includes key fields: project, development stage, task to be tested, tester, priority (0-100, the larger the numerical value, the lower the priority, 0 is special for emergency task, the test execution end can not change after confirming the test task before the test is not completed); the test task execution template comprises the following key fields: the SVN version number of the software to be tested, the test engineering path, the test state (to be confirmed/in progress/completed/closed), the test result (passed/failed), the father task number, the test mode (manual/automatic), and the automatic test starting time period. It can be understood that the test control end is used by a test supervisor, and the test execution end is used by a test engineer.
If the number of test items is large, the authority and the template of the test sub-control end of the middle level can be set, the test sub-control end is specially responsible for the follow-up of the test task of a single item, the test control end only needs to define the priority of each current item, the test sub-control end defines the priority of each function to be tested aiming at the condition of the single item, and the test task sub-distribution template of the test sub-control end under the condition comprises key fields as follows: project testing state (not started/in progress/completed), priority of function to be tested (0-100, the higher the value is, the lower the priority is, 0 is special for emergency task, the test execution end can not change after confirming the test task before the test is not completed), planned testing completion time, and father task number. The test control end defines the priority of each project, assigns the test task to each test sub-control end, and has the Redmine number of N0. And testing requirements of a new project of the test child control end, defining the priority of each function, setting Redmine number to be N1 and setting a parent task number to be N0, and assigning the test tasks to each test execution end. After receiving the test task, the test execution end creates a function test requirement in Redmine, the Redmine is numbered N2, the father task is numbered N1, after the MIL/SIL test engineering debugging is completed, the test state is set to be in progress, at the moment, the priority sequence in the father task can not be changed until the test execution end confirms that the test is completed, and the test state is set to be completed. It is understood that the test sub-control end is provided for the test manager (or other persons who perform the same authority and function as the test manager in this embodiment, which is not limited by this embodiment) to use.
The continuous integration test platform obtains the test tasks and the test priorities of the test execution ends by reading the test task allocation template and the test task execution template (when the test sub-control ends exist, the test task sub-allocation template is also read), and an automatic test task scheduling table is generated according to the test tasks and the test priorities. In the automatic test task schedule, the test priority includes an item priority and a function priority, which are respectively expressed by numerical values, for example, (3.2) represents a test task with an item priority of 3 and a function priority of 2. It will be appreciated that the higher the value, the lower the priority, the smaller the item priority value in the plurality of items, and the smaller the functional priority value in the same item. For example, if the test priority of a test task is (2.2), it will be executed before the test task with the test priority of (3.2) (since its project priority 2 is less than 3); likewise, if the test priority of a test task is (2.1), it will be executed before the test task with the test priority of (2.2) (since its functional priority 1 is less than 2). As mentioned above, the priority value 0 is only limited to emergency handling, and other priorities can be skipped, but the test controller or the test sub-controller needs to be assigned on the test requirement management platform and assigned to a certain test executor.
The continuous integration test platform is provided with an administrator account, and account numbers (capable of accessing the test requirement management platform, the model and the code management platform) of the test control end, the test sub-control end and the test execution end are arranged in the administrator account through a Jenkins plug-in-plug v0.2, so that the administrator account can be operated to call open interfaces of the test requirement management platform, the model and the code management platform to know whether the test requirement management platform, the model and the code management platform change or not, and the significance of the method is that whether the test requirement of the test requirement management platform changes or not and whether a to-be-tested software model or a to-be-tested code of the model and the code management platform changes or not can be confirmed. For example, the test requirements management platform generates a new test task assignment template or test task execution template, or the test status in the template is updated (e.g., from "not started" to "in progress").
The continuous integrated test platform is also provided with a receiving address of a test result receiving end, which is usually a mail address, so that the test result can be sent to the test result receiving end after the test is finished. Generally, the test result receiving end is at least any one of a test control end, a test sub-control end, and a test execution end of the test, and its receiving address is set in an administrator account with its account number. However, the embodiment of the present invention is not limited to this, and a new receiving address of the receiving end of the test result may be set as needed.
The continuous integration test platform can call the test case developed by the test execution end when the test is performed on the ring test tool or the software in the ring test tool through the preset script starting model by the test engineering path in the test task execution template. And when the automatic test starting time period is reached, the continuous integrated test platform preferentially executes the automatic test tasks with small values in the automatic test task scheduling table. And after the test is finished, obtaining a test result, sending the test result to a set test result receiving end (by mail), finally closing the test, setting the test state in the test task execution template to be finished on a test requirement management platform, and starting the next test task on the task scheduling table until all test tasks are finished or the automatic test time period is exceeded. And for the test tasks exceeding the automatic test time period, the test priorities of the test tasks are frozen by the continuous integrated test platform and are placed into a next automatic test task scheduling table for sequencing. It should be noted that, if the automatic test task schedule is in units of days, the automatic test task schedule of the next time is the automatic test task schedule of the next day.
The test execution end (operated by a test engineer) confirms the test result according to the test task in the finished state, sets the test state in the test task execution template to be closed on the test requirement management platform after the test is finished, and releases the corresponding function priority at the same time; and if all the functional tests of a certain project are completed, setting the test state in the test task execution template of the project to be closed, and simultaneously releasing the corresponding project priority.
When the test task scheduling system of this embodiment is constructed, a continuous integration test platform constructed based on Jenkins, a test demand management platform constructed based on Redmine, and a model and code management platform constructed based on SVN may be installed in a server, and the three platforms are configured, so that the three platforms can be accessed in the form of a web page and the like in a local area network.
In order to enhance the applicability, in this embodiment, a new or ongoing test task may be turned off or terminated by the test execution end, and the test task that has been turned off may be turned on again by the test execution end for testing.
Corresponding to the first embodiment of the present invention, the second embodiment of the present invention further provides a test task scheduling method, which is implemented by a persistent integration test platform constructed based on Jenkins, a test requirement management platform constructed based on Redmine, and a model and code management platform constructed based on SVN, and the test task scheduling method includes the following steps:
the continuous integration test platform acquires the test tasks and the test priorities of the test execution ends from the test requirement management platform and generates an automatic test task scheduling table; the test requirement management platform is provided with a test control end and a test execution end which are in communication connection with the test requirement management platform, and the test control end distributes test tasks to the test execution ends according to the total test requirement and sets the test priorities of the test tasks;
and the continuous integration test platform calls a to-be-tested software model or code from the model and code management platform, and starts a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table.
The test task scheduling method further comprises the following steps:
the test requirement management platform respectively establishes a test task allocation template of a test control end and a test task execution template of a test execution end, wherein the test task allocation template comprises key fields as follows: project, development stage, task to be tested, tester, priority; the test task execution template comprises the following key fields: the SVN version number, the test engineering path, the test state, the test result, the father task number, the test mode and the automatic test starting time period of the software to be tested.
When the automatic test starting time period is reached, the continuous integration test platform calls a test case developed by a test execution end through a test engineering path in the test task execution template, and starts a model in-loop test tool or a software in-loop test tool to test.
After a certain test task is completed, the continuous integration test platform sets the test state in the test task execution template to be completed on the test requirement management platform, and starts the next test task on the automatic test task scheduling table until all test tasks are completed or the automatic test time period is exceeded.
And the continuous integration test platform sends the test result to a test result receiving end after the test is finished.
And the continuous integrated test platform freezes the test priority of the test task exceeding the automatic test time period and puts the test priority into a next automatic test task scheduling table for sequencing.
The test execution end confirms the test result according to the test task in the finished state, sets the test state in the test task execution template to be closed on the test requirement management platform after the test is finished, and releases the corresponding function priority at the same time; and if all the functional tests of a certain project are completed, setting the test states in all the test task execution templates of the project to be closed, and simultaneously releasing the corresponding project priority.
For the detailed working principle and process of the present embodiment, please refer to the description of the first embodiment of the present invention, which is not repeated herein.
As can be seen from the above description, the implementation of the embodiment of the present invention has the following beneficial effects:
after the test tasks are determined, the test supervisor and the test manager can completely know the test rhythm only by performing task allocation according to the priority, a test engineer can control the test process more freely according to the test tasks and only needs to concentrate on test preparation work such as development of test cases and the like and test result analysis, the test tasks are automatically executed according to the priority sequence, the test planning problem does not need to be considered, the influence caused by manual intervention is reduced, and the test efficiency is greatly improved; when an emergency task occurs, high-priority scheduling can ensure that the existing test task is not influenced or is influenced a little;
the invention can construct an MIL/SIL test task scheduling system by setting different role authorities of a test demand management platform based on a small amount of script calling, so that test work can be reasonably distributed and scheduled in week units, and multi-task sequential execution can be carried out in idle time by using a continuous integrated test platform.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.
Claims (12)
1. A test task scheduling system, comprising: a continuous integration test platform constructed based on Jenkins, a test requirement management platform constructed based on Redmine, and a model and code management platform constructed based on SVN,
the test requirement management platform is used for configuring the authority of a test control end and a test execution end which are in communication connection with the test requirement management platform, so that the test control end distributes test tasks to the test execution ends according to the total test requirement and sets the test priority of the test tasks;
the model and code management platform is used for providing a software model or code to be tested;
the continuous integration test platform is used for acquiring the test tasks and the test priorities of the test execution ends from the test requirement management platform and generating an automatic test task scheduling table; and calling a software model or code to be tested from the model and code management platform, and starting a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table.
2. The system according to claim 1, wherein the test requirement management platform is further configured to establish a test task allocation template of the test control end and a test task execution template of the test execution end, respectively, where the test task allocation template includes key fields: project, development stage, task to be tested, tester, priority; the test task execution template comprises the following key fields: the SVN version number, the test engineering path, the test state, the test result, the father task number, the test mode and the automatic test starting time period of the software to be tested.
3. The system according to claim 2, wherein the test requirement management platform is further configured to set an authority of a test sub-control end communicatively connected to the test requirement management platform and located at an intermediate level between the test control end and the test execution end, and establish a test task sub-allocation template, where the test task sub-allocation template includes key fields: project test state, function priority to be tested, scheduled test completion time and parent task number.
4. The system according to claim 3, wherein the persistent integration test platform obtains the test tasks and the test priorities thereof at each test execution end by reading the test task allocation template, the test task sub-allocation template, and the test task execution template, and generates an automatic test task schedule according to the test tasks and the test priorities, wherein in the automatic test task schedule, the test priorities include a project priority and a function priority, which are respectively represented by numerical values, and the numerical values of the project priority and the function priority are both 0 to 100.
5. The system according to claim 4, wherein the testing task scheduling system is configured to perform the testing according to the automatic testing task scheduling table by the continuous integration testing platform according to the item priority values from small to large in a plurality of items and according to the function priority values from small to large in the same item.
6. The system for dispatching test tasks according to claim 3, wherein the persistent integration test platform has an administrator account, and the account numbers of the test control end, the test sub-control end and the test execution end are set in the administrator account through Jenkins plug-ins.
7. The system according to claim 2, wherein the persistent integration test platform is specifically configured to, when the automatic test start time period is reached, invoke a test case developed by the test execution end through a test engineering path in the test task execution template, and start a model-in-loop test tool or a software-in-loop test tool to perform a test.
8. The system according to claim 7, wherein after a certain test task is completed, the persistent integration test platform sets the test status in the test task execution template to be completed on the test requirement management platform, and starts the next test task on the automatic test task schedule until all test tasks are completed or an automatic test time period is exceeded.
9. The system for dispatching test tasks according to claim 8, wherein the persistent integration test platform is further configured with a receiving address of a test result receiving end for sending the test result to the test result receiving end after the test is completed.
10. The test task scheduling system of claim 8, wherein the persistent integrated test platform is further configured to freeze test priorities of test tasks that exceed an automatic test time period and place them into a next automatic test task schedule for ordering.
11. The system according to claim 8, wherein the test execution end performs test result confirmation according to the test task in the completed state, and sets the test state in the test task execution template to be closed on the test requirement management platform after completion, and simultaneously releases the corresponding function priority; and if all the functional tests of a certain project are completed, setting the test states in all the test task execution templates of the project to be closed, and simultaneously releasing the corresponding project priority.
12. A test task scheduling method is characterized by being implemented through a continuous integration test platform constructed based on Jenkins, a test demand management platform constructed based on Redmine and a model and code management platform constructed based on SVN, and comprises the following steps:
the continuous integration test platform acquires the test tasks and the test priorities of the test execution ends from the test requirement management platform and generates an automatic test task scheduling table; the test requirement management platform is provided with a test control end and a test execution end which are in communication connection with the test requirement management platform, and the test control end distributes test tasks to the test execution ends according to the total test requirement and sets the test priorities of the test tasks;
and the continuous integration test platform calls a to-be-tested software model or code from the model and code management platform, and starts a model-in-loop test tool or a software-in-loop test tool to test through a preset script according to the automatic test task scheduling table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010254998.3A CN113495548A (en) | 2020-04-02 | 2020-04-02 | Test scheduling system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010254998.3A CN113495548A (en) | 2020-04-02 | 2020-04-02 | Test scheduling system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113495548A true CN113495548A (en) | 2021-10-12 |
Family
ID=77993889
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010254998.3A Pending CN113495548A (en) | 2020-04-02 | 2020-04-02 | Test scheduling system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113495548A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101246439A (en) * | 2008-03-18 | 2008-08-20 | 中兴通讯股份有限公司 | Automatized test method and system based on task scheduling |
| CN105786696A (en) * | 2014-12-26 | 2016-07-20 | 阿里巴巴集团控股有限公司 | Test method and device |
| CN106407100A (en) * | 2015-07-29 | 2017-02-15 | 中兴通讯股份有限公司 | Method and apparatus for realizing continuous integration testing |
| CN108536571A (en) * | 2018-04-13 | 2018-09-14 | 平安普惠企业管理有限公司 | Performance test methods, device, equipment and computer readable storage medium |
| CN108664386A (en) * | 2017-03-30 | 2018-10-16 | 北京神州泰岳软件股份有限公司 | A kind of automated testing method and platform |
| CN109062786A (en) * | 2018-07-16 | 2018-12-21 | 北京百度网讯科技有限公司 | Operation method, device and the terminal of test case |
| CN110245088A (en) * | 2019-06-21 | 2019-09-17 | 四川长虹电器股份有限公司 | A kind of defect automated verification system and verification method based on Jenkins |
| US10515005B1 (en) * | 2018-12-20 | 2019-12-24 | Atlassian Pty Ltd | Systems and methods for testing source code |
-
2020
- 2020-04-02 CN CN202010254998.3A patent/CN113495548A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101246439A (en) * | 2008-03-18 | 2008-08-20 | 中兴通讯股份有限公司 | Automatized test method and system based on task scheduling |
| CN105786696A (en) * | 2014-12-26 | 2016-07-20 | 阿里巴巴集团控股有限公司 | Test method and device |
| CN106407100A (en) * | 2015-07-29 | 2017-02-15 | 中兴通讯股份有限公司 | Method and apparatus for realizing continuous integration testing |
| CN108664386A (en) * | 2017-03-30 | 2018-10-16 | 北京神州泰岳软件股份有限公司 | A kind of automated testing method and platform |
| CN108536571A (en) * | 2018-04-13 | 2018-09-14 | 平安普惠企业管理有限公司 | Performance test methods, device, equipment and computer readable storage medium |
| CN109062786A (en) * | 2018-07-16 | 2018-12-21 | 北京百度网讯科技有限公司 | Operation method, device and the terminal of test case |
| US10515005B1 (en) * | 2018-12-20 | 2019-12-24 | Atlassian Pty Ltd | Systems and methods for testing source code |
| CN110245088A (en) * | 2019-06-21 | 2019-09-17 | 四川长虹电器股份有限公司 | A kind of defect automated verification system and verification method based on Jenkins |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105183644B (en) | A kind of multitask integrated automation test system and method | |
| CN109472442B (en) | Automatic processing system and method for work order | |
| Hou et al. | Allocation of periodic task modules with precedence and deadline constraints in distributed real-time systems | |
| CN110928774A (en) | Automatic test system based on node formula | |
| US8301935B2 (en) | Distributed batch runner | |
| CN106774240B (en) | service-oriented industrial production control and monitoring method and system | |
| Mönch et al. | A simulation framework for the performance assessment of shop-floor control systems | |
| CN107463362A (en) | The method and system of lasting deployment based on multiple Jenkins | |
| CN105260248B (en) | A kind of task scheduling system and dispatching method being dynamically adapted | |
| CN111240935B (en) | Automatic intelligent operation and maintenance system and operation and maintenance method | |
| CN110414908A (en) | Project examination method, air control approval system and medium based on air control approval system | |
| Maimon | Real-time operational control of flexible manufacturing systems | |
| CN113641483A (en) | Robot process automation system based on artificial intelligence | |
| CN111290934A (en) | Jenkins-based vehicle-mounted network product cloud testing method and system | |
| CN113495548A (en) | Test scheduling system and method | |
| Ham et al. | IP-based real-time dispatching for two-machine batching problem with time window constraints | |
| US20100235839A1 (en) | Apparatus and method for automation of a business process | |
| CN115185825A (en) | Interface test scheduling method and device | |
| CN109634749B (en) | Distributed unified scheduling method and device | |
| CN114428621A (en) | Operation automation deployment method | |
| Rongfa | Adaptive software test management system based on software agents | |
| CN109388415A (en) | Application automation updating device, system and method | |
| Kaltwasser et al. | Hierarchical control of flexible manufacturing systems | |
| Zhang et al. | Dynamic reconfiguration of holonic lower level control | |
| CN115022314B (en) | Enterprise-level RPA cloud management platform |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20211228 Address after: 511434 No. 36, Longying Road, Shilou Town, Panyu District, Guangzhou City, Guangdong Province Applicant after: GAC AION New Energy Vehicle Co.,Ltd. Address before: 23rd floor, Chengyue building, No. 448-458, Dongfeng Middle Road, Yuexiu District, Guangzhou City, Guangdong Province 510030 Applicant before: GUANGZHOU AUTOMOBILE GROUP Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211012 |
|
| RJ01 | Rejection of invention patent application after publication |