CN100422954C - Software system multi-user characteristic testing method and system - Google Patents
Software system multi-user characteristic testing method and system Download PDFInfo
- Publication number
- CN100422954C CN100422954C CNB2006100581950A CN200610058195A CN100422954C CN 100422954 C CN100422954 C CN 100422954C CN B2006100581950 A CNB2006100581950 A CN B2006100581950A CN 200610058195 A CN200610058195 A CN 200610058195A CN 100422954 C CN100422954 C CN 100422954C
- Authority
- CN
- China
- Prior art keywords
- test
- message
- parameter
- testing
- virtual
- 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
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention publicizes a testing methods of multi-user software system, including: separates information flow and information parameter values, puts each example of the operation of test flow into of Virtual Test unit; identifies news parameters of different users in the Test Case news, and generates the parameters table containing parameter information values; Virtual test modules obtain the corresponding parameter values from the table with the users, test cases, the source parameters; Virtual test unit operating the script procedures described to implement the testing process of users. Accordingly, the test system of the multi-user of this software system includes: virtual test module, control module and test monitoring unit. This invention can simulate flexibly the news flow with a between users and software system measured, reduce the workload and work intensity in the software development and testing system implementation / assessment phase.
Description
Technical field
The present invention relates to moving communicating field system testing technology, particularly a kind of method of testing and system of built-in system software subsystem multi-user characteristic.
Background technology
The commitment of process of embedded system exploitation, the technician adopts systematic approach will treat that development system is decomposed into software subsystem and hardware subsystem, the systemic-function characteristic is divided into relevant hardware functional characteristic and software function feature.Follow-up development activities is divided into the hardware and software subsystem and implements respectively, and final stage is integrated into the hardware and software subsystem a complete embedded system again.
Software system test is one of important link in the embedded device development process.In the checking development requirement of the function of software systems and expection whether consistent then be an important content of software system test.The checking system under test (SUT) is the important content of functional verification test design to a plurality of users' management characteristic.
Existing software test procedure is continued to use following step usually and is carried out Test Design, enforcement, realizes the checking to multi-user's characteristic of software systems:
(1) with sole user be test side, adopt ripe method for test examples design, the test case that expection covers index is satisfied in design.Method for designing comprises:
(1.1) elementary path method: test case deviser estimates based on the logic complexity of the understanding of software design details being derived certain function/process, and use this to estimate the baseset that defines execution route as guide, the test case that derives from this baseset guarantees each the bar perform statement the program is carried out once at least again;
(1.2) reciprocity interval division method: test case deviser is divided into some intervals with the input and output of tested software, makes that tested software all is of equal value to any value between a given zone.The data that form between the test section comprise the parameter of function/process, the global variable of software-accessible, system resource (these variablees or resource can be the data that exist with time form, or the input and output sequence that exists with stastus format) etc.Test case deviser designs a test case in a typical value of selection in each interval for it;
(1.3) boundary value analysis method: test case deviser adopts the analytical approach of (1.2), and the wrong border that most possibly appears between the interval of supposition.Test case deviser designs specific test case to two boundary values arrangements of boundary value again.
(2) after the method sign test case of describing according to (1), the test script that becomes test macro to carry out test case conversion based on test configurations and testing tool;
(3) to different users, repeating step (1)-(2);
(4) during test run, be executable unit with the unique user, the test script that generates of operating procedure (2)-(3) successively.
If said method tissue, operation test case are transformed the test script unit one to one, the work of the then development﹠ testing of test script execution, assessment will expend considerable human resources.
Summary of the invention
Therefore, the object of the present invention is to provide a kind of method of testing and system of software system multi-user characteristic, realize test by receive, send message parameter at when operation configuration virtual test cell (Virtual Tester), with the development﹠ testing that solves script in the prior art workload and working strength problem of higher in execution/evaluation stage to system under test (SUT) multi-user characteristic.
For achieving the above object, the method for testing of software system multi-user characteristic provided by the invention comprises: testing process and message parameter are separated, the shell script of described testing process is imported each virtual test cell; Determine the described message parameter value of the test case of different user, and generate the parameter list that comprises described message parameter value; Virtual test cell moves described shell script, and from described parameter list acquisition and user, test case, message parameter value that message parameter is corresponding, to carry out described testing process.
The parameter when test run being set and the quantity of virtual test cell according to test request, adjust described virtual test cell behavior by revising virtual test cell message parameter value, message parameter value of using in the described test case and test case Id, message Id, parameter I d, virtual test cell Id deposits jointly.
Described shell script comprises that the test script to expression interacting message order and message details compiles the test suite of generation separately.
Described virtual test cell calls api function or database reads function dynamic message parameter value that obtains from parameter list.
Described api function or database read function with test case Id, message Id, and parameter I d, run mode virtual test cell Id is as parameter.
It is corresponding one by one that the Id that test case of described test case Id unique identification, value are used during with Test Design person's advance planning test case keeps.
Described message Id is message of unique identification in the test case scope, and planned and define, quote in test script design and message parameter edit phase in the test case design phase by the Test Design personnel.
Described virtual test cell Id is obtained from test environment by virtual test cell when test run, is used to identify virtual test cell.
Correspondingly, the test macro of software system multi-user characteristic provided by the invention comprises:
Virtual test cell is used to simulate the various user types of tested software system;
Control module is used to control the execution and the termination of virtual test cell;
Testing monitoring unit is used to monitor the test process of a plurality of control modules and virtual test cell;
Described control module separates testing process and message parameter, and the shell script of described testing process is imported each virtual test cell; Described testing monitoring unit is determined the value of message parameter of the test case of different user, and generates the parameter list that comprises described message parameter; Described virtual test cell moves described shell script, and from parameter list acquisition and user, test case, message parameter value that message parameter is corresponding, to carry out described testing process.
Compared with prior art, the present invention has the following advantages:
The method of testing of software system multi-user characteristic of the present invention and system the time dynamically arrange parameter value based on a spot of message definition and operation and realize test to system under test (SUT) multi-user characteristic; The testing process that to represent the interacting message order of different user during test implementation is separately organized with the message parameter of expression message content, storage; Expression interacting message order compiles, is connected the executable test suite of generation separately with the test script of message details; The virtual test cell that is formed by the test procedure evolution calls the parameter value that API obtains specific user, message, parameter in the process of carrying out the test script program, thereby can simulate the message flow (for example input/output relation) between this user and the tested software system neatly.When utilizing a plurality of virtual test cells to simulate a plurality of users' message flow, a plurality of users' test procedure can carry out simultaneously, greatly reduces workload and the working strength of development﹠ testing execution/evaluation stage of script.
Description of drawings
Fig. 1 is the process flow diagram of software system multi-user characteristic testing method of the present invention;
Fig. 2 is a software system multi-user characteristic testing system block diagram of the present invention;
Fig. 3 is the process flow diagram that specifies software system multi-user characteristic testing method of the present invention;
Fig. 4 is the block scheme of the embodiment of software system multi-user characteristic testing of the present invention system.
Embodiment
The software subsystem test activity generally includes several stages such as test-schedule, test case design, test case exploitation, test run, outcome evaluation.Test case is high more to the software feature level of coverage, and system's latent defect possibility of finding in the test run is just high more, and the defective of hiding through test back system is just few more.Method of testing of the present invention is separated the message interaction process that test case relates to system with message parameter, in the Test Design stage message flow that test case comprises is carried out separate analysis, design and develop and message content virtual test instrument (Virtual Tester) message transmission/reception flow process independently, difference with flow process is distinguished test script, different testing process shapes should different virtual test instrument behaviors, definition and construction separately.The virtual test cell here can be defined as the set of the series of task that the test procedure script finished when carrying out.
Fig. 1 is the process flow diagram of software system multi-user characteristic testing method of the present invention.As shown in Figure 1, the method for testing of software system multi-user characteristic of the present invention is separated message flow and message parameter value, and the running example of testing process is imported each virtual test cell (S101); Determine the message parameter of different user in the test case message, and generate the parameter list (S102) that comprises the message parameter value; Virtual test cell is acquisition and user, test case, message parameter corresponding parameters value (S103) from parameter list; Virtual test cell moves described shell script and carries out user test flow process (S104).Method of testing of the present invention is carried out separate analysis in the Test Design stage to the message flow that test case comprises, design and develop and message content virtual test instrument message transmission/reception flow process independently, difference with flow process is distinguished test script, the virtual test instrument behavior that different testing processs is corresponding different.To represent during test that the testing process of interacting message order and the message parameter of expression message content separate.The virtual test instrument obtains the message parameter value from parameter list or database when operation, the interacting message when being moved by message flow between example and the system under test (SUT) realizes that message sends, reception/detecting operation.
Fig. 3 is the process flow diagram that specifies software system multi-user characteristic testing method of the present invention.As shown in Figure 3, before the test execution, the tester participates in the virtual test instrument number of test when requiring test run is set according to the multi-user, revise the behavior of single virtual tester by the parameter list in edit-modify parameter value table or the database according to elementary path method, reciprocity interval division method and boundary value analysis method principle.For test case 1, the message parameter that relates in virtual test instrument 0 or 1 the behavior definition all adopts formalization parameter (variable) expression, for example message 1 and message 2, parameter 0,1,2 and 3.The parameter value that uses in the test case is independent of test script to be deposited separately, and parameter value adopts the storage of two-dimensional matrix frame mode.The test script that to represent interacting message order and message details (partial parameters is that formalization parameter, actual value as ready row order section are determined) compiles, is connected the executable test case of generation separately.Virtual test instrument Id is obtained from test environment by the virtual test instrument when test run, and obtains test case Id, message Id and parameter I d from the test script specified message.Test case Id is used for test case of unique identification, and it is corresponding one by one that the Id that value is used during with Test Design person's advance planning test case keeps; Message Id is used for message of unique identification in the test case scope, is planned and defines, quotes in test script design and message parameter edit phase in the test case design phase by the Test Design personnel.The message parameter value that the virtual test instrument uses in test case and test case Id, message Id, parameter I d, virtual test instrument Id etc. leave in the outside data file or database simultaneously.The parameter acquiring api function or the database that can call when planning the operation of one group of test script simultaneously in the Test Design stage read function, and the virtual test instrument calls these api functions or database in the operation phase and reads function and dynamically obtain message parameter.By the message parameter value in call parameters table or the database, the user subject that virtual test instrument simulation is corresponding with the message parameter value sends message to system under test (SUT), and from system under test (SUT) reception message, and multi-user's characteristic of system under test (SUT) is detected.
Fig. 2 is a software system multi-user characteristic testing system block diagram of the present invention.As shown in Figure 2, the test macro of software system multi-user characteristic of the present invention comprises the virtual test cell of the various user types that are used to simulate the tested software system; Be used to control the control module of the execution and the termination of virtual test cell; Be used to monitor the testing monitoring unit of the test process of a plurality of control modules and virtual test cell.Control module separates testing process and message flow, and the shell script of testing process is imported each virtual test cell; Testing monitoring unit is determined the message parameter of message flow in the different user test case, and generates the parameter list that comprises message parameter; Virtual test cell obtains from parameter list and user message flow process corresponding parameters value; And move described shell script and carry out the user test flow process.System under test (SUT) is connected based on communication service with the virtual test instrument of simulation softward external environment condition; Collaborative activities between a plurality of control modules and the virtual test cell is managed by monitoring unit.State/the daily record of record was uploaded to monitoring unit when control module moved virtual test cell, and other operating components move the back result treatment, and generating structure is good, the test report of standard.
Fig. 4 is the block scheme of the embodiment of software system multi-user characteristic testing of the present invention system.When multi-user's (mobile phone, mobile communication terminal) management characteristic test of carrying out RNC (radio network controller of 3G (Third Generation) Moblie network) wireless signaling processing unit, test environment comprises following ingredient: a plurality of VT examples (comprising UE_Simulator, CN_Simulator, NodeB_Simulator etc.) message transmission service of testing engine (Rational Test RealTime Supervisor+Rational Test RealTime Agent), artificial antenna Signaling Processing Unit environment and test data management service etc.As shown in Figure 4, in the process of the multi-user management characteristic test of RNC wireless signaling processing unit configuration, testing engineering is according to test script, test private communication service code, data access service code organization; Testing engineering is edited in RTRT (Rational Tester RealTime) testing tool environment, safeguards, is preserved; Plan the external environment condition parts of simulation RNC wireless signaling processing units such as CN_Sim (simulation CN), NodeB_Sim (simulation NodeB) and UE_Sim (analogue mobile phone) in the test script.Test script middle finger location survey routine number and message and parameter identification on probation; During the configuration testing method of operation, specify CN_Sim, NodeB_Sim and UE_Sim all to support a plurality of examples; The running environment of being made up of from RTRT_Supervisor, RTRT-Agent the virtual test instrument of simulation external environment condition parts during operation is obtained virtual test instrument instance number, number by obtaining parameter in the predetermined parameter list, finish the initialization of transmission/reception message in conjunction with the use-case in the test script, message, parameter; Virtual test instrument example carries out the mutual of message according to the logical and system under test (SUT) of test script.Typical multi-user test script is as follows:
INSTANCE?NB_Sim：
COMMENT?NB_Sim?wait?and?receive?RL?Reconfigure?Req?from?SUT
DEF_MESSAGE?svar_IubC_SAAL_N_DATA_REQ_STRUCT，EV＝{
& uiMsgId＝＞IUBC_SAAL_N_DATA_REQ
&}
WAITTIL(MATCHING(svar_IubC_SAAL_N_DATA_REQ_STRUCT，ccss)，TIME＞1000)
--for?Trch?id/*2005-11-1*/
@GetParamfrmTable(ATL_CCID，122_VoiceCallI，IubC_DATA，svar_trchid)；
COMMENT?NB_Sim?Send?RadioLinkReconfigurationReady?message?to?SUT
......
VAR?svar_DCH_Informat?ionResponse，INIT＝{
& next＝＞NIL，
& value＝＞{
& bit_mask＝＞0x80，
& dCH_ID＝＞svar_trchid[0]，/*2005-10-11modify*/
......
END?INSTANCE--NB_Sim
When writing test case, need represent that the initialization of variable is finished by the api function that calls the test data management services module and provide because of the parameter of virtual test instrument implementation variations with variable.
Getting parms is worth api function then with test case Id, message Id, and parameter I d, run mode virtual test instrument Id (being the UE_Simulator example number ATL_OCCID that testing engine provides) is as parameter.The test data management services module is with the queried access of the paired multi-user test parameter of the information translation of api function allocation table.Multi-user test, is finished when test script is write according to the test case unified planning simultaneously with parameter list.Typical multi-user test is as follows with the parameter list segment:
Example Id parameter value during use-case ID message id parameter I D VT operation
122k_Voice_Call RB_Setup DCH_ID[0] 0 20
122k_Voice_Call RB_Setup DCH_ID[1] 0 21
122k_Voice_Call RL_Setup Binding_Id 0 266
64K_Stream_Call RB_Setup DCH_ID[0] 1 16
64K_Stream_Call RB_Setup DCH_ID[1] 1 18
......
Before the test implementation, configuration Rational Test RealTime instrument is supported a plurality of virtual test instrument examples.When obtaining ATL_OCCID as operation, Rational Test RealTime Supervisor identifies during the initialization of test virtual test instrument.
Though described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, wish that appended claim comprises these distortion and variation and do not break away from spirit of the present invention.
Claims (9)
1. the method for testing of a software system multi-user characteristic is characterized in that, comprising:
A. testing process and message parameter are separated, the shell script of described testing process is imported each virtual test cell;
B. determine the value of described message parameter of the test case of different user, and generate the parameter list that comprises described message parameter value;
C. described virtual test cell moves described shell script, and from described parameter list acquisition and user, test case, message parameter value that message parameter is corresponding, to carry out described testing process.
2. method of testing as claimed in claim 1, it is characterized in that: the parameter when test run being set and the quantity of virtual test cell according to test request, adjust described virtual test cell behavior by revising virtual test cell message parameter value, message parameter value of using in the described test case and test case Id, message Id, parameter I d, virtual test cell Id deposits jointly.
3. method of testing as claimed in claim 1 is characterized in that: described shell script comprises that the test script to expression interacting message order and message details compiles the test suite of generation separately.
4. method of testing as claimed in claim 1 is characterized in that: described virtual test cell calls api function or database reads function dynamic message parameter value that obtains from parameter list.
5. method of testing as claimed in claim 4 is characterized in that: described api function or database read function with test case Id, message Id, and parameter I d, run mode virtual test cell Id is as parameter.
6. method of testing as claimed in claim 2 is characterized in that: the Id that test case of described test case Id unique identification, value are used during with Test Design person's advance planning test case keeps corresponding one by one.
7. method of testing as claimed in claim 2, it is characterized in that: described message Id is message of unique identification in the test case scope, and planned and define, quote in test script design and message parameter edit phase in the test case design phase by the Test Design personnel.
8. method of testing as claimed in claim 2 is characterized in that: described virtual test cell Id is obtained from test environment by virtual test cell when test run, is used to identify virtual test cell.
9. the test macro of a software system multi-user characteristic is characterized in that, comprising:
Virtual test cell is used to simulate the various user types of tested software system;
Control module is used to control the execution and the termination of virtual test cell;
Testing monitoring unit is used to monitor the test process of a plurality of control modules and virtual test cell;
Described control module separates testing process and message parameter, and the shell script of described testing process is imported each virtual test cell; Described testing monitoring unit is determined the value of described message parameter of the test case of different user, and generates the parameter list that comprises described message parameter; Described virtual test cell moves described shell script, and from described parameter list acquisition and user, test case, message parameter value that message parameter is corresponding, to carry out described testing process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100581950A CN100422954C (en) | 2006-03-10 | 2006-03-10 | Software system multi-user characteristic testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100581950A CN100422954C (en) | 2006-03-10 | 2006-03-10 | Software system multi-user characteristic testing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101034370A CN101034370A (en) | 2007-09-12 |
| CN100422954C true CN100422954C (en) | 2008-10-01 |
Family
ID=38730937
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100581950A Active CN100422954C (en) | 2006-03-10 | 2006-03-10 | Software system multi-user characteristic testing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100422954C (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567203A (en) * | 2011-12-28 | 2012-07-11 | 创新科软件技术（深圳）有限公司 | Method and system for testing performance of distributed file system (DFS) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102156673B (en) * | 2011-04-20 | 2013-09-18 | 北京航空航天大学 | Test case description oriented GUI (Graphical User Interface) automatic test system and test method thereof |
| CN102395150B (en) * | 2011-06-28 | 2017-08-25 | 中兴通讯股份有限公司 | Packet data service paging telephone traffic testing method and device |
| CN103152216B (en) * | 2011-12-07 | 2016-08-10 | 北京新媒传信科技有限公司 | The method of testing of system and device in a kind of the Internet |
| CN103530222B (en) * | 2012-07-04 | 2018-01-09 | 腾讯科技（深圳）有限公司 | Method for testing software and system based on emotion |
| CN103853655A (en) * | 2012-11-30 | 2014-06-11 | 英业达科技有限公司 | Testing system and testing method for generating virtual testing unit outside to-be-tested device |
| CN104008055B (en) * | 2014-05-30 | 2017-06-06 | 广州华多网络科技有限公司 | The method of software test, equipment and system |
| CN105071988A (en) * | 2015-07-28 | 2015-11-18 | 武汉虹信通信技术有限责任公司 | Multi-user test system and method |
| CN105260309A (en) * | 2015-10-21 | 2016-01-20 | 上海斐讯数据通信技术有限公司 | Automatic test platform unrelated to test tool |
| CN107092559A (en) * | 2017-04-18 | 2017-08-25 | 携程旅游信息技术（上海）有限公司 | Test platform middleware, test system and method based on Jmeter |
| DE102017218296A1 (en) * | 2017-10-12 | 2019-04-18 | Rohde & Schwarz Gmbh & Co. Kg | Multi-user test system and method for configuring a multi-user test system |
| CN109739621A (en) * | 2018-12-28 | 2019-05-10 | 南京天溯自动化控制系统有限公司 | A kind of full soft data equipment simulating method of PaaSization |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004002121A1 (en) * | 2002-06-21 | 2003-12-31 | Empirix Inc. | One script test script system and method for testing a contact center voice application |
| CN1503168A (en) * | 2002-11-22 | 2004-06-09 | 深圳市中兴通讯股份有限公司 | Automatic test method for system products |
| US6772083B2 (en) * | 2002-09-03 | 2004-08-03 | Sap Aktiengesellschaft | Computer program test configurations with data containers and test scripts |
| CN1741479A (en) * | 2004-08-29 | 2006-03-01 | 华为技术有限公司 | Information receiving and transmitting controller based on information test and method thereof |
-
2006
- 2006-03-10 CN CNB2006100581950A patent/CN100422954C/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004002121A1 (en) * | 2002-06-21 | 2003-12-31 | Empirix Inc. | One script test script system and method for testing a contact center voice application |
| US6772083B2 (en) * | 2002-09-03 | 2004-08-03 | Sap Aktiengesellschaft | Computer program test configurations with data containers and test scripts |
| CN1503168A (en) * | 2002-11-22 | 2004-06-09 | 深圳市中兴通讯股份有限公司 | Automatic test method for system products |
| CN1741479A (en) * | 2004-08-29 | 2006-03-01 | 华为技术有限公司 | Information receiving and transmitting controller based on information test and method thereof |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567203A (en) * | 2011-12-28 | 2012-07-11 | 创新科软件技术（深圳）有限公司 | Method and system for testing performance of distributed file system (DFS) |
| CN102567203B (en) * | 2011-12-28 | 2015-09-23 | 创新科软件技术（深圳）有限公司 | A kind of method and system of test distributed file system performance |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101034370A (en) | 2007-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100422954C (en) | Software system multi-user characteristic testing method and system | |
| CN102880546B (en) | Software integration testing method and system based on extensible markup language (XML) database | |
| CN106940428B (en) | Chip verification method, device and system | |
| CA2496738C (en) | Method and system for configuration control in telecommunications networks | |
| Rountev et al. | Coverage criteria for testing of object interactions in sequence diagrams | |
| CN106933745A (en) | WEB automatic interface testing methods and system | |
| CN106874187A (en) | code coverage collection method and device | |
| CN103605606B (en) | A kind of embedded software test use-case batch execution method that can automatically change | |
| CN105786695A (en) | Data test method and system | |
| CN112433944A (en) | Service testing method, device, computer equipment and storage medium | |
| CN108255707A (en) | Development roles creation method, device, equipment and the storage medium of test case | |
| CN102025555B (en) | Method and device for testing IP multimedia sub-system performance | |
| CN101765129A (en) | Network access test system and method for data value-added service | |
| Jacob et al. | Towards a methodology for experimental evaluation in low-power wireless networking | |
| US6351455B1 (en) | System test metacontroller | |
| CN112685291A (en) | System joint test method and related device | |
| CN111176995B (en) | Test method and test system based on big data test case | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN115833964A (en) | Performance test method and performance test system of dual-mode communication module | |
| CN109117139A (en) | A kind of software building method and device, server and readable storage medium storing program for executing | |
| Wang et al. | Correlating context-awareness and mutation analysis for pervasive computing systems | |
| Nicolaescu et al. | Behavior-based architecture reconstruction and conformance checking | |
| CN115982055B (en) | Test method special for java language development program | |
| Zhang | Research on software development and test environment automation based on android platform | |
| CN112445692B (en) | Case testing method and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |