CN102819488B - Test processes device and test processing method - Google Patents
Test processes device and test processing method Download PDFInfo
- Publication number
- CN102819488B CN102819488B CN201210226131.2A CN201210226131A CN102819488B CN 102819488 B CN102819488 B CN 102819488B CN 201210226131 A CN201210226131 A CN 201210226131A CN 102819488 B CN102819488 B CN 102819488B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- module
- case
- context
- 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.)
- Active
Links
Abstract
The invention provides a kind of test processes device, comprising: test case acquisition module, the test case in acquisition system; Context parameters arranges module, is set in the thread context of described test case by the context parameters needed for test target component; Test case execution module, performs described test case, to test described target member.Correspondingly, present invention also offers a kind of test processing method.By technical scheme of the present invention, for based on OSGi(Open? Service? Gateway? Initiative) software systems realized, the context consistent with true environment can be provided for the execution of tested use-case, avoid the difference of the test result caused due to the difference of execution environment, simultaneously, realize the loose coupling between test case and tested object, test case can be performed in a batch, and then improve the testing efficiency of software systems, promote the development quality of software systems.
Description
Technical field
The present invention relates to software test field, in particular to a kind of test processes device and a kind of test processing method.
Background technology
OSGi (OpenServiceGatewayInitiative) is the dynamic modeling system towards Java, the exploitation that it is modular applications defines an architecture, make application program can realize standard package that is definition refining, reusable and that can cooperate, and can neatly, dynamically assemble and be deployed in application system.Due to these characteristics, OSGi has obtained the widespread use of industry, becomes one of first-selected framework of Integrated Simulation and enterprise development.
But owing to adopting different Classloaders to carry out loading procedure code to realize loose couplings and the Dynamical Deployment of assembly under OSGi environment, this mechanism is completely different from traditional application program, and the method for testing used in traditional application development can not be transplanted in OSGi environment simply.This contradiction makes at present there are some FAQs in various degree based on the software system development of OSGi: a, cannot carry out automatic test and can only adopt the manual test of inefficiency, the regression test time and effort consuming carried out after software systems change, test coverage is low; B, test case code closely depend on the target member of test and cannot separately dispose; C, test case can only not rely on for some the component run with system context environment and test, and cause those components depending on business contexts environment to set up automatic test cases.
In sum, in OSGi environment, the difference problem that the subject matter faced is the context environmental of test case operation and the true environment of test target component is tested to software component.
For this, existing common way sets up independently test context for each test case to load and implementation of test cases, as shown in Figure 1A.The context environmental of implementation of test cases under this mode is defined by test frame itself, and be different from the true environment (as shown in Figure 1B) that tested component performs in software systems, and the context of each test case is isolation, this just requires that tested component can not depend on the execution environment of the software systems at its place.Therefore the scope of application of this method is more limited, the building blocks of function of usual software systems all needs the context environmental depending on system, so above-mentioned test frame cannot support the test to this class A of geometric unitA in function aspects such as affairs, safety, data access, daily records mostly.
Therefore need a kind of new technical scheme, the context consistent with true environment can be provided for the execution of tested use-case, avoid the difference of the test result caused due to the difference of execution environment, simultaneously, realize the loose coupling between test case and tested object, test case can be performed in a batch, and then improves the testing efficiency of software systems, promotes the development quality of software systems.
Summary of the invention
Technical matters to be solved by this invention is, a kind of new technical scheme is provided, the context consistent with true environment can be provided for the execution of tested use-case, avoid the difference of the test result caused due to the difference of execution environment, meanwhile, realize the loose coupling between test case and tested object, test case can be performed in a batch, and then improve the testing efficiency of software systems, promote the development quality of software systems.
In view of this, the invention provides a kind of test processes device, comprising: test case acquisition module, the test case in acquisition system; Context parameters arranges module, is set in the thread context of described test case by the context parameters needed for test target component; Test case execution module, performs described test case, to test described target member.
In this technical scheme, by described context parameters, module is set, context parameters needed for test target component is set in the thread context of described test case, thus provide the context consistent with true environment for tested use-case, and then the difference of the test result caused due to the difference of execution environment can be avoided, improve the quality of software test.
In technique scheme, preferably, also comprise: criterion settings module, the data structure of described test case, deployment way and/or load mode are set; Test case realizes module, described test case is realized in the system by described data structure, described deployment way and/or described load mode, described test case acquisition module is by described deployment way, described test case is obtained from described system, and/or described test case execution module is according to described data structure, create the programmatic object instances of described test case, to test described target member, and/or by described load mode, load described test case, to perform described test case to test described target member.
In the technical program, the data structure of test case, defines the information that should comprise when representing or indicate a test case, such as numbering, title, version, author etc.; The deployment of test case and load mode, define the existence form of test case, searches adopting corresponding mode accordingly and load test case.
In technique scheme, preferably, when described system is dynamic module system, described test case acquisition module obtains the module of all startups from the context of described system, and obtains the module comprising described test case from the module of described startup.
In this technical scheme, test case can be obtained according to concrete system environments, be particularly useful for OSGi(OpenServiceGatewayInitiative) software systems that realize, such as, under OSGi environment, the bundle comprising test case can be filtered out from the bundle started.
In technique scheme, preferably, also comprise: module realizes module, in the system, realize described test case and described target member with modular form.
In this technical scheme, need, in systems in which in environment, in advance target member and test case to be disposed in modular form, be conducive to reducing the coupling between target member and test case, such as, under OSGi environment, target member and test case can bundle form realize.
In technique scheme, preferably, described context parameters comprises login user, data source, session identification and/or Transaction Identifier.
In this technical scheme, it will be appreciated by those skilled in the art that foregoing is only the example of context parameters, be not limited, context parameters can comprise more eurypalynous content.
Present invention also offers a kind of test processing method, comprising: step 202, the test case in acquisition system; Step 204, is set in the thread context of described test case by the context parameters needed for test target component; Step 206, performs described test case, to test described target member.
In this technical scheme, context parameters needed for test target component is set in the thread context of described test case, thus provide the context consistent with true environment for tested use-case, and then the difference of the test result caused due to the difference of execution environment can be avoided, improve the quality of software test.
In technique scheme, preferably, before described step 202, also comprise: the data structure of described test case, deployment way and/or load mode are set, and realize described test case in the system by described data structure, described deployment way and/or described load mode; Described step 202 comprises: by described deployment way, from described system, obtain described test case; And/or described step 206 comprises: according to described data structure, create the programmatic object instances of described test case, to test described target member, and/or by described load mode, load described test case, to perform described test case to test described target member.
In the technical program, the data structure of test case, defines the information that should comprise when representing or indicate a test case, such as numbering, title, version, author etc.; The deployment of test case and load mode, define the existence form of test case, searches adopting corresponding mode accordingly and load test case.
In technique scheme, preferably, described step 202 comprises: when described system is dynamic module system, obtain the module of all startups from the context of described system, and obtain the module comprising described test case from the module of described startup.
In this technical scheme, test case can be obtained according to concrete system environments, be particularly useful for OSGi(OpenServiceGatewayInitiative) software systems that realize, such as, under OSGi environment, the bundle comprising test case can be filtered out from the bundle started.
In technique scheme, preferably, before described step 202, also comprise: in the system, realize described test case and described target member with modular form.
In this technical scheme, need, in systems in which in environment, in advance target member and test case to be disposed in modular form, be conducive to reducing the coupling between target member and test case, such as, under OSGi environment, target member and test case can bundle form realize.
In technique scheme, preferably, described context parameters comprises login user, data source, session identification and/or Transaction Identifier.
In this technical scheme, it will be appreciated by those skilled in the art that foregoing is only the example of context parameters, be not limited, context parameters can comprise more eurypalynous content.
By above technical scheme, the context consistent with true environment can be provided for the execution of tested use-case, avoid the difference of the test result caused due to the difference of execution environment, simultaneously, realize the loose coupling between test case and tested object, test case can be performed in a batch, and then improves the testing efficiency of software systems, promotes the development quality of software systems.
Accompanying drawing explanation
The running environment schematic diagram of the component testing method that Figure 1A is general under showing the OSGi environment in correlation technique;
Figure 1B shows the running environment schematic diagram of the software systems component reality in correlation technique;
Fig. 2 shows the process flow diagram of test processing method according to an embodiment of the invention;
Fig. 3 shows the block diagram of test processes device according to an embodiment of the invention;
Fig. 4 shows the structural representation of test processes device according to an embodiment of the invention;
Fig. 5 shows the module diagram of test processes device according to an embodiment of the invention;
Fig. 6 shows the workflow diagram of test processes device according to an embodiment of the invention.
Embodiment
In order to more clearly understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.
Set forth a lot of detail in the following description so that fully understand the present invention, but the present invention can also adopt other to be different from other modes described here and implement, and therefore, the present invention is not limited to the restriction of following public specific embodiment.
Fig. 2 shows the process flow diagram of test processing method according to an embodiment of the invention.
As shown in Figure 2, present invention also offers a kind of test processing method, comprising: step 202, the test case in acquisition system; Step 204, is set in the thread context of described test case by the context parameters needed for test target component; Step 206, performs described test case, to test described target member.
In this technical scheme, context parameters needed for test target component is set in the thread context of described test case, thus provide the context consistent with true environment for tested use-case, and then the difference of the test result caused due to the difference of execution environment can be avoided, improve the quality of software test.
In technique scheme, before described step 202, also comprise: the data structure of described test case, deployment way and/or load mode are set, and realize described test case in the system by described data structure, described deployment way and/or described load mode; Described step 202 comprises: by described deployment way, from described system, obtain described test case; And/or described step 206 comprises: according to described data structure, create the programmatic object instances of described test case, to test described target member, and/or by described load mode, load described test case, to perform described test case to test described target member.
In the technical program, the data structure of test case, defines the information that should comprise when representing or indicate a test case, such as numbering, title, version, author etc.; The deployment of test case and load mode, define the existence form of test case, searches adopting corresponding mode accordingly and load test case.
In technique scheme, described step 202 comprises: when described system is dynamic module system, obtain the module of all startups from the context of described system, and obtain the module comprising described test case from the module of described startup.
In this technical scheme, test case can be obtained according to concrete system environments, be particularly useful for OSGi(OpenServiceGatewayInitiative) software systems that realize, such as, under OSGi environment, the bundle comprising test case can be filtered out from the bundle started.
In technique scheme, before described step 202, also comprise: in the system, realize described test case and described target member with modular form.
In this technical scheme, need, in systems in which in environment, in advance target member and test case to be disposed in modular form, be conducive to reducing the coupling between target member and test case, such as, under OSGi environment, target member and test case can bundle form realize.
In technique scheme, described context parameters comprises login user, data source, session identification and/or Transaction Identifier.
In this technical scheme, it will be appreciated by those skilled in the art that foregoing is only the example of context parameters, be not limited, context parameters can comprise more eurypalynous content
Fig. 3 shows the block diagram of test processes device according to an embodiment of the invention.
As shown in Figure 3, the invention provides a kind of test processes device 300, comprising: test case acquisition module 302, the test case in acquisition system; Context parameters arranges module 304, is set in the thread context of described test case by the context parameters needed for test target component; Test case execution module 306, performs described test case, to test described target member.
In this technical scheme, by described context parameters, module 304 is set, context parameters needed for test target component is set in the thread context of described test case, thus provide the context consistent with true environment for tested use-case, and then the difference of the test result caused due to the difference of execution environment can be avoided, improve the quality of software test.
In technique scheme, also comprise: criterion settings module 308, the data structure of described test case, deployment way and/or load mode are set; Test case realizes module 310, described test case is realized in the system by described data structure, described deployment way and/or described load mode, described test case acquisition module 302 is by described deployment way, described test case is obtained from described system, and/or described test case execution module 306 is according to described data structure, create the programmatic object instances of described test case, to test described target member, and/or by described load mode, load described test case, to perform described test case to test described target member.
In the technical program, the data structure of test case, defines the information that should comprise when representing or indicate a test case, such as numbering, title, version, author etc.; The deployment of test case and load mode, define the existence form of test case, searches adopting corresponding mode accordingly and load test case.
In technique scheme, when described system is dynamic module system, described test case acquisition module 302 obtains the module of all startups from the context of described system, and obtains the module comprising described test case from the module of described startup.
In this technical scheme, test case can be obtained according to concrete system environments, be particularly useful for OSGi(OpenServiceGatewayInitiative) software systems that realize, such as, under OSGi environment, the bundle comprising test case can be filtered out from the bundle started.
In technique scheme, also comprise: module realizes module 312, in the system, realize described test case and described target member with modular form.
In this technical scheme, need, in systems in which in environment, in advance target member and test case to be disposed in modular form, be conducive to reducing the coupling between target member and test case, such as, under OSGi environment, target member and test case can bundle form realize.
In technique scheme, described context parameters comprises login user, data source, session identification and/or Transaction Identifier.
In this technical scheme, it will be appreciated by those skilled in the art that foregoing is only the example of context parameters, be not limited, context parameters can comprise more eurypalynous content.
Below in conjunction with embodiment, describe technical scheme of the present invention in detail.
The test processes apparatus design proposed in the present embodiment is be run in same environment with tested software systems, the context consistent with true environment can be provided like this for the execution of test case, solve the problem mentioned in background technology, relative to prior art, the schematic diagram of the test processes device of the technical scheme of the present embodiment can as shown in Figure 4, and test case can carry out the test of target member in conjunction with actual actual motion environment.
The test processes device that the present embodiment proposes can as shown in Figure 5, be made up of test and management module 502, test interface module 504, test case module 506 3 part:
1, test interface module 502(is equivalent to aforesaid criterion settings module): this part defines the interface specification that test case module 506 needs are followed.Test and management module 504 and test case module 506 all depend on this module.
2, test and management module 504(is equivalent to aforesaid context parameters and arranges module and test case acquisition module): this partial function is search from the OSGi environment run, loads and run the test case of having disposed, for test case arranges the thread context of code execution, and collect and output test result.
3, test case module 506(is equivalent to aforesaid module and realizes module): this part defines carries out the test case of testing for specific objective.This module relies on but independent of the module at tested target member place, is a unit that can independently dispose, can disposes as required.
Test and management module 504, test interface module 502, test case module 506 are all identical with the module at test target place in the form realized in physical aspect, all be implemented as the bundle of OSGi, be deployed in OSGi running environment with same form.
Directly not relying between test and management module 504, test interface module 502, test case module 506, is that the mode of the loose coupling provided according to OSGi running environment forms dependence between them.
The inventive system comprises 1 test and management module, 504,1 test interface module, 502 and 0 ~ N number of test case module 506.Test case module 506 can be disposed as required, and test and management module 504 collects all test cases of definition in test case module 506 in a dynamic way from OSGi context.
One, test interface module 502:
This module is the public module of test and management module 504 and test case module 506, and its core defines the interface specification that test case and test and management module 504 follow all jointly.Test case is followed this interface specification to realize, and test and management module 504 is also followed same interface specification to load and testing results use-case.
Test interface module 502 is existence abstract in logic, and the actual form of interface specification of its definition can show as interface on programming language or class, also can show as the XML document that portion needs jointly to observe, or the document of other form.Thus, physically, test interface module 502 can be one and contain one of the data file such as interface, class, XML document of the programming language forming interface specification independently OSGiBundle, also these data files can be realized in same OSGiBundle together with test and management module.
The key element of interface specification definition comprises:
(1) data structure of test case:
Define the information that should comprise when representing or indicate a test case, such as numbering, title, version, author etc.;
(2) deployment of test case and load mode:
Define the existence form of test case, test and management module 504 is searched adopting corresponding mode accordingly and loads test case.
Such as, be below one section of description about test case interface specification:
Test case requires all will comprise the contents such as title, version, author, description, needs to realize interface type com.my.test.ITestCase; Method of testing in test case, with small letter " test " beginning, does not have rreturn value and parameter; Test assertion judges whether by test by a series of static method assertEquals of type com.my.test.Test; Be configured with in test b undle the ClassName of all test cases defined in the Bundle at test case place with XML file testbundle.xml, testbundle.xml file is arranged in META-INF catalogue.
Similarly, in interface module, interface type com.my.test.ITestCase and Test is defined as follows:
Two, the realization of test and management module 504:
Test and management module 504 is nucleus modules of the present invention, and the key realizing this module is to implement these as OSGiBundle, is deployed in the OSGi environment of goal systems, performs with test target in identical context in the same manner as test target.Like this, before implementation of test cases, the context parameters of goal systems can be set in the thread context performing use-case, ensure that test case is correctly carried out the test call of test target component with this.
The execution of a test assignment is formed primarily of following several operation:
1, test case is collected:
The test case of searching and collecting deployment from current system environments is the prerequisite performing test assignment, and the interface specification that detailed process will follow test interface module definition realizes.
The first step, obtains the Bundle of all startups current OSGi environment from OSGiBundle context.The BundleContext object provided according to OSGi environment provides corresponding programmed method (such as: getBundles ()) and can obtain all Bundle.
Second step, is defined according to test interface specification the Bundle leaching and contain test case.Together with the definition Bundle of test case is deployed in the Bundle of test target component, therefore need the Bundle list filtering obtained from Bundle context to go out to comprise the Bundle of test case, the method for filtration follows the interface specification of test interface module definition.For before act interface specification example, correspondingly, this can according to the META-INF catalogue in Bundle in whether contain testbundle.xml configuration file and be configured with at least one test case in file as filtercondition, follow-up process is performed to qualified Bundle.
3rd step, searches the list obtaining test case from Bundle; This step needs the interface specification following test interface module definition to collect the information of test case.For before act interface specification example, correspondingly, the testbundle.xml configuration file of resolving in Bundle under META-INF catalogue obtains the type, title, parameter etc. of the test case configured wherein, and these information will be used for the programmatic object instances creating test case when implementation of test cases.
2, initialization use-case performs context:
This process is set in the thread context of test case by the context parameters required for test target component, makes the test call of test case to target member be able to effective operation.Contextual initialization mode is relevant to actual software systems, in general includes but not limited to current login user, current data source, session id, the system environments parameters such as affairs ID.
3, implementation of test cases outputs test result:
According to the test case information collected in operation before, load test case, the method for testing in implementation of test cases, record and export the execution result of these method of testings.Need to realize according to the interface specification of test interface module definition to the loading of test case and the execution of method of testing.For before act interface specification example, correspondingly, create the example that those achieve the type of com.my.test.ITestCase interface, perform wherein with the method for test beginning one by one, the test method testing result output of throw exception is not had to be by testing for complete, the output of throw exception is test crash, and output abnormality information.
Three, test case module 506:
Test case module 506 is for defining test case, its way of realization is OSGiBundle, depend on test interface module 502 and test target component, together dispose with the Bundle of test target component, it is introduced modes such as Service, PackageImport that the dependence of test target component is provided by OSGi, does not have invasive to test target component.
In test case module 506, test case is the codes implement class that have followed interface specification that test interface module 502 defines and realize carrying out for particular elements the checking of code execution result, and what what it was concrete realize depending on the function of the destination object of its test.
For the interface specification lifted in test interface module 502, a test case can be implemented as following form:
The realization example of the testbundle.xml accordingly in the META-INF catalogue of Bundle is as follows:
Be more than the example that test case realizes, this example is followed interface specification and is achieved interface ITestCase, defines two method of testing testDistributeOrders, testUploadOrders.
Fig. 6 illustrates the workflow of the test processes device of embodiments of the invention.
As shown in Figure 6, step 602, from all Bundle information of OSGi context collection;
Step 604, processes the Bundle collected one by one;
Step 606, judges whether this Bundle is Validity Test use-case module, entering step 608, when no, enter step 612 when being;
Step 608, loads the test case defined in test case module;
Step 610, adds execution queue by test case;
Step 612, has judged whether untreated Bundle, has had, returned step 604, then do not entered step 614;
Step 614, initialization test use-case performs context;
Step 616, implementation of test cases outputs test result.
By above technical scheme, a kind of test processes device and a kind of disposal route can be realized, improve the testing efficiency of software systems, improve the development quality of software systems.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (8)
1. a test processes device, is characterized in that, comprising:
Test case acquisition module, the test case in acquisition system;
Context parameters arranges module, is set in the thread context of described test case by the context parameters needed for test target component;
Test case execution module, performs described test case, to test described target member;
Criterion settings module, before the test case in described acquisition system, arranges the data structure of described test case, deployment way and/or load mode;
Test case realizes module, described test case is realized in the system by described data structure, described deployment way and/or described load mode, described test case acquisition module is by described deployment way, described test case is obtained from described system, and/or described test case execution module is according to described data structure, create the programmatic object instances of described test case, to test described target member, and/or by described load mode, load described test case, to perform described test case to test described target member.
2. test processes device according to claim 1, it is characterized in that, when described system is dynamic module system, described test case acquisition module obtains the module of all startups from the context of described system, and obtains the module comprising described test case from the module of described startup.
3. test processes device according to claim 2, is characterized in that, also comprise:
Module realizes module, before the test case in described acquisition system, in the system, realizes described test case and described target member with modular form.
4. test processes device according to any one of claim 1 to 3, is characterized in that, described context parameters comprises login user, data source, session identification and/or Transaction Identifier.
5. a test processing method, is characterized in that, comprising:
Step 202, the test case in acquisition system;
Step 204, is set in the thread context of described test case by the context parameters needed for test target component;
Step 206, performs described test case, to test described target member;
Before described step 202, also comprise: the data structure of described test case, deployment way and/or load mode are set, and realize described test case in the system by described data structure, described deployment way and/or described load mode;
Described step 202 comprises: by described deployment way, from described system, obtain described test case; And/or
Described step 206 comprises: according to described data structure, creates the programmatic object instances of described test case, to test described target member, and/or
By described load mode, load described test case, to perform described test case to test described target member.
6. test processing method according to claim 5, is characterized in that, described step 202 comprises:
When described system is dynamic module system, obtain the module of all startups from the context of described system, and obtain the module comprising described test case from the module of described startup.
7. test processing method according to claim 6, is characterized in that, before described step 202, also comprises:
In the system, described test case and described target member is realized with modular form.
8. the test processing method according to any one of claim 5 to 7, is characterized in that, described context parameters comprises login user, data source, session identification and/or Transaction Identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210226131.2A CN102819488B (en) | 2012-06-29 | 2012-06-29 | Test processes device and test processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210226131.2A CN102819488B (en) | 2012-06-29 | 2012-06-29 | Test processes device and test processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102819488A CN102819488A (en) | 2012-12-12 |
| CN102819488B true CN102819488B (en) | 2016-01-20 |
Family
ID=47303610
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210226131.2A Active CN102819488B (en) | 2012-06-29 | 2012-06-29 | Test processes device and test processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102819488B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103425585B (en) * | 2013-08-31 | 2017-02-08 | 华南理工大学 | OSGI (Open Service Gateway Initiative) integration testing method |
| CN104850489B (en) * | 2014-02-13 | 2017-11-28 | 富士通株式会社 | Mobile solution test system |
| CN105701005B (en) * | 2014-11-28 | 2018-09-18 | 阿里巴巴集团控股有限公司 | Application framework test method based on OSGI and system |
| CN107015814A (en) * | 2017-04-26 | 2017-08-04 | 国网冀北电力有限公司信息通信分公司 | Meet the browser operation design method of OS business transplanting |
| CN107908543A (en) * | 2017-07-26 | 2018-04-13 | 平安壹钱包电子商务有限公司 | Applied program testing method, device, computer equipment and storage medium |
| CN109992511B (en) * | 2019-03-25 | 2022-11-22 | 口碑(上海)信息技术有限公司 | Device and method for obtaining code test coverage rate |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1780236A (en) * | 2004-11-17 | 2006-05-31 | 中兴通讯股份有限公司 | Universal testing system and method for telecommunication intelligent service |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8423962B2 (en) * | 2009-10-08 | 2013-04-16 | International Business Machines Corporation | Automated test execution plan generation |
-
2012
- 2012-06-29 CN CN201210226131.2A patent/CN102819488B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1780236A (en) * | 2004-11-17 | 2006-05-31 | 中兴通讯股份有限公司 | Universal testing system and method for telecommunication intelligent service |
Non-Patent Citations (1)
| Title |
|---|
| 通用网管接口测试事务模型的构建方法及其实现;刘文勇;《中国优秀硕士学位论文全文数据库》;20111015;第20-21页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102819488A (en) | 2012-12-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102819488B (en) | Test processes device and test processing method | |
| CN108845940A (en) | A kind of enterprise information system automated function test method and system | |
| CN103995698A (en) | Application form agile development method and system oriented to business | |
| CN105760296A (en) | Automation testing control method, device and terminal | |
| CN107220297A (en) | The multi-source heterogeneous automated data acquiistion method and system of software-oriented project | |
| CN105069686A (en) | Case automatic detection method and system | |
| US20190087160A1 (en) | System and method for creating domain specific language | |
| CN106599167A (en) | System and method capable of supporting incremental upgrading of database | |
| CN103246605A (en) | Method and system for collocating remote controller key values based on xml (extensive markup language) | |
| CN101201788A (en) | System for locating detection item | |
| CN101662394B (en) | Automated testing system and automated testing method | |
| Gambi et al. | Poster: Improving cloud-based continuous integration environments | |
| CN103838890A (en) | Comparative method of layout and schematic uniformity of multi-power-domain system with black box IPs | |
| CN103176904B (en) | A kind of simulation test platform software architecture and the method for testing based on this framework | |
| JP2013077124A (en) | Software test case generation device | |
| CN112464237B (en) | Static code security diagnosis method and device | |
| Saadatmand | Towards automating integration testing of. NET applications using Roslyn | |
| CN106528179A (en) | Static recognition method for Java class dependence relations | |
| CN100511178C (en) | Method for locating detection item | |
| CN101201789A (en) | System for locating detection item | |
| CN106600149A (en) | Process analysis method and apparatus | |
| Bhullar et al. | Exploration of UML diagrams based code generation methods | |
| CN109828914A (en) | Whole process distributed system automated testing method and test macro | |
| CN101251824B (en) | Method for testing public objects request proxy structure and tools | |
| CN104182346A (en) | Detection framework applicable to open service gateway initiative (OSGI) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100094 Haidian District North Road, Beijing, No. 68 Applicant after: Yonyou Network Technology Co., Ltd. Address before: 100094 Beijing city Haidian District North Road No. 68, UFIDA Software Park Applicant before: UFIDA Software Co., Ltd. |
|
| COR | Change of bibliographic data | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |