CN1932776A - Automatic operating method for interface test in embedded operating system - Google Patents
Automatic operating method for interface test in embedded operating system Download PDFInfo
- Publication number
- CN1932776A CN1932776A CN 200610116867 CN200610116867A CN1932776A CN 1932776 A CN1932776 A CN 1932776A CN 200610116867 CN200610116867 CN 200610116867 CN 200610116867 A CN200610116867 A CN 200610116867A CN 1932776 A CN1932776 A CN 1932776A
- Authority
- CN
- China
- Prior art keywords
- test
- embedded
- target machine
- developing engine
- test case
- 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.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
An automatic course method uses for interface testing in insert-type operating system. Create testing object by exploitation machine after periodic time and tests executing script and information of test case. Transmit the test object to goal machine and start system to download testing executing script. Circularly download test case and run to produce testing export information. Send testing export information and testing end information to exploitation machine and it will send the testing course result after comparing the d criterion export information and testing export information. It effectively shortens regression and testing period and assures the fast balanced advance of the system with smooth capability and without manpower interposition to save resource. It is suit for testing the application interface to bring benefit with broader range of application to further development of inset-type system and its super software.
Description
Technical field
The present invention relates to field of computer, particularly computing machine embedded OS automatic test field specifically is meant the automatic operating method of interface testing in a kind of embedded OS.
Background technology
Along with being showing improvement or progress day by day of The present computer technology, people also become more and more easier for the various exploitations and the maintenance of computer system.Operating system interface is kept apart hardware details and programmer, provides one group can manage and method of operating hardware resource easily.The interface of embedded OS generally comprises aspects such as process, thread, memory management, file system, can also provide network interface and graphic interface etc. according to application need.Most interfaces of operating system have descended in the early stage just definition of system development, in the embedded OS performance history, move forward steadily in order to ensure exploitation, and we need carry out continuous regression test to system interface.Regression test occurs in after the software modification, can carry out once comprehensively regression test with interior code revision to one day usually, guarantees the correctness of this day exploitation, also is convenient in time locate and solve the bug that this day exploitation occurs, and guarantees that software development moves forward steadily.
At first the test of operating system interface is adopted usually the means development and testing use-case code of unit testing and integration testing, the test code that exploitation is finished is included regression test in then, such test case reaches thousands of usually, and the executable file size of all test codes reaches hundreds and thousands of million.Embedded OS is different with the general-purpose operating system, the exploitation of the operation code of embedded system, compiling and link are to finish on developing engine (computing machine of Windows operating system for example is housed), executable file need be uploaded to embedded device from developing engine, the process that so just has a file transfer, and the general storage space of the embedded device that it moves is all smaller, is difficult to carry up to a hundred million test procedure.Usually our the simplest method expected is, manually downloads a test procedure and moves to embedded device, checks the result then, deletes this test file, and then downloads another test procedure and continue operation.
This method of testing needs manual intervention, and manually move test case and will spend a large amount of time, the regression test cycle is long, caused the prolongation of construction cycle, and operating process is more uninteresting, and wanting to finish in the limited time regression test often needs to expend more man power and material.
Summary of the invention
The objective of the invention is to have overcome above-mentioned shortcoming of the prior art, a kind of operation that can finish all test case programs on the embedded device of limited storage resources automatically is provided, need not manual intervention, saves human resources, effectively shortens the regression test cycle, guarantees the propelling of embedded system development quick and stable, stable and reliable for performance, the scope of application automatic operating method of interface testing in the embedded OS comparatively widely.
In order to realize above-mentioned purpose, the automatic operating method of interface testing is as follows in the embedded OS of the present invention:
The automatic operating method of interface testing in this embedded OS, the host's test target machine system that comprises developing engine system and embedded OS, communicator in the described developing engine system is connected with communicator in the target machine system by data link, its principal feature is that described method may further comprise the steps:
(1) the developing engine system regularly generates embedded OS tested object, test execution script and test case information processing;
(2) the developing engine system is transferred to described embedded OS tested object in the target machine system by communicator;
(3) the target machine system starts embedded OS and from the processing of developing engine system downloads test execution script;
(4) the target machine system carries out the test execution script, from developing engine system downloads test case information;
(5) target machine system operation test case information and generation test output information;
(6) the target machine system transmits this test output information by communicator to the developing engine system;
(7) current test case information of target machine system-kill and test output information;
(8) the target machine system judges whether the test execution script is finished, if be not finished, then returns step (4) operation;
(9) if be finished, then the target machine system transmits end of test (EOT) information by communicator to the developing engine system;
(10) the developing engine system receives this end of test (EOT) information, and default standard output information and the test output information that receives are compared, and obtains the test run result.
Regular generation embedded OS tested object, test execution script and the test case information of the automatic operating method of interface testing may further comprise the steps in this embedded OS:
(1) system regularly downloads up-to-date code from the source code server;
(2) above-mentioned code compile is generated image file and all test case programs of embedded OS;
(3) system synthesizes the pairing execution script of each test case program and generation test execution script.
The automatic operating method of interface testing the embedded OS tested object is transferred in the target machine system may further comprise the steps in this embedded OS:
(1) the developing engine system sends notice reboot flag data to the target machine system by communicator, and notification target machine system restarts;
(2) the target machine system receives the notice reboot flag data that the developing engine system sends, restarting systems;
(3) after the developing engine system treats that the target machine system restarts, be transferred in the target machine system by the image file of communication device with embedded OS;
(4) the target machine system receives the image file that the developing engine system sends by communicator, and with its programming in the embedded device of target machine system.
The source code server of the automatic operating method of interface testing can be CVS source code management server, ClearCase source code management server or SourceSafe source code management server in this embedded OS.
The startup embedded OS of the automatic operating method of interface testing and may further comprise the steps in this embedded OS from the processing of developing engine system downloads test execution script:
(1) the target machine system judges that this startup belongs to any in following two kinds of situations: start first after the programming of new system is intact, new system restarts unusually because of taking place in the test run process;
(2) if the programming of new system starts after intact first, then the target machine system by communicator from developing engine system downloads test execution script;
(3) if new system restarts unusually because of generation in the test run process, then, only keep the order line content of not carrying out with the order line deletion of having carried out in the test execution script.
The target machine system of the automatic operating method of interface testing operation test case information may further comprise the steps in this embedded OS:
(1) to note the program command of current operation before start carrying out this test case information capable in system;
(2) process of the corresponding test case information of system creation and begin to carry out, and the appearance of the various abnormal conditions of monitoring in real time in the process of implementation of test cases process;
(3) if the operation of the test case process system that makes is absorbed in deadlock, then the process that does not also have operation to finish will be killed by system behind one section special time, if kill this process success, it is capable then to continue the operation Next Command; If kill this process failure, then carry out system and restart;
(4) if the operation of the test case process system that makes is absorbed in debugging mode, then this process will be killed by system, if kill this process success, it is capable then to continue the operation Next Command; If kill this process failure, then carry out system and restart;
(5) the Installed System Memory deficiency be lower than the systemic presupposition value if the operation of test case process makes, then carry out system and restart as if the discovery Installed System Memory.
In the automatic operating method of interface testing, carry out the real-time monitoring of abnormal conditions in this embedded OS by deadlock monitor code, debugging mode monitor code, the internal memory monitoring code that in the exploitation code of system, adds through conditional compilation control.
The end of test (EOT) information of the automatic operating method of interface testing is test run end mark file in this embedded OS.
The standard output information of the automatic operating method of interface testing is standard output file in this embedded OS, and described test output information is the test output file.
In this embedded OS the automatic operating method of interface testing default standard output information and the test output information that receives are compared into:
Use the file compare tool that default standard output file and the test output file that receives are compared.
Adopted the automatic operating method of interface testing in the embedded OS of this invention, owing in the developing engine system, realized automatic compiled code, and notification target machine system begins test, and upload operation system image file and test case program are downloaded the test output file automatically automatically; Simultaneously, in the target machine system, realized automatic download, operation and deletion test procedure, upload the test output file, automatically handle various system exceptions, and the test execution script can continue to move next test procedure after the assurance abnormality processing, notify developing engine to finish test at last, thereby realized on the embedded device of limited storage resources, carrying out the automatic operating of embedded OS interface testing, need not manual intervention, human resources have been saved, effectively shorten the regression tested cycle, guaranteed the propelling of embedded system development quick and stable, stable and reliable for performance.Moreover, the automatic operating method of interface testing is not limited to operating system interface in the embedded OS of the present invention, test for the application interface on the embedded OS is suitable for too, can bring benefit for application and development, the scope of application is comparatively extensive, for further developing of embedded system and upper layer software (applications) thereof established solid foundation.
Description of drawings
Fig. 1 is the integrated testability framework synoptic diagram of the automatic operating method of interface testing in the embedded OS of the present invention.
Fig. 2 is the test process synoptic diagram of target machine system of the automatic operating method of interface testing in the embedded OS of the present invention.
Fig. 3 is for carrying out the process synoptic diagram of file transfer between the developing engine system of the automatic operating method of interface testing in the embedded OS of the present invention and the target machine system.
Embodiment
In order more to be expressly understood technology contents of the present invention, describe in detail especially exemplified by following examples.
See also Fig. 1 to shown in Figure 3, the automatic operating method of interface testing in this embedded OS, the host's test target machine system that comprises developing engine system and embedded OS, communicator in the described developing engine system is connected with communicator in the target machine system by data link, wherein, may further comprise the steps:
(1) the developing engine system regularly generates embedded OS tested object, test execution script and test case information processing, may further comprise the steps:
(a) system regularly downloads up-to-date code from the source code server, and this source code server can be CVS source generation
Sign indicating number management server, ClearCase source code management server or SourceSafe source code management server;
(b) above-mentioned code compile is generated image file and all test case programs of embedded OS;
(c) system synthesizes the pairing execution script of each test case program and generation test execution script;
(2) the developing engine system is transferred to described embedded OS tested object in the target machine system by communicator, may further comprise the steps:
(a) the developing engine system sends notice reboot flag data to the target machine system by communicator, and notification target machine system restarts;
(b) the target machine system receives the notice reboot flag data that the developing engine system sends, restarting systems;
(c) after the developing engine system treats that the target machine system restarts, be transferred in the target machine system by the image file of communication device with embedded OS;
(d) the target machine system receives the image file that the developing engine system sends by communicator, and with its programming in the embedded device of target machine system;
(3) the target machine system starts embedded OS and from the processing of developing engine system downloads test execution script, may further comprise the steps:
(a) the target machine system judges that this startup belongs to any in following two kinds of situations: start first after the programming of new system is intact, new system restarts unusually because of taking place in the test run process;
(b) if the programming of new system starts after intact first, then the target machine system by communicator from developing engine system downloads test execution script;
(c) if new system restarts unusually because of generation in the test run process, then, only keep the order line content of not carrying out with the order line deletion of having carried out in the test execution script;
(4) the target machine system carries out the test execution script, from developing engine system downloads test case information;
(5) target machine system operation test case information and generation test output information may further comprise the steps:
(a) to note the program command of current operation before start carrying out this test case information capable in system;
(b) process of the corresponding test case information of system creation and begin to carry out, and the appearance of the various abnormal conditions of monitoring in real time in the process of implementation of test cases process;
(c) if the operation of the test case process system that makes is absorbed in deadlock, then the process that does not also have operation to finish will be killed by system behind one section special time, if kill this process success, it is capable then to continue the operation Next Command; If kill this process failure, then carry out system and restart;
(d) if the operation of the test case process system that makes is absorbed in debugging mode, then this process will be killed by system, if kill this process success, it is capable then to continue the operation Next Command; If kill this process failure, then carry out system and restart;
(e) the Installed System Memory deficiency be lower than the systemic presupposition value if the operation of test case process makes, then carry out system and restart as if the discovery Installed System Memory;
Wherein, can carry out the real-time monitoring of abnormal conditions by deadlock monitor code, debugging mode monitor code, the internal memory monitoring code that in the exploitation code of system, adds through conditional compilation control.
(6) the target machine system transmits this test output information by communicator to the developing engine system;
(7) current test case information of target machine system-kill and test output information;
(8) the target machine system judges whether the test execution script is finished, if be not finished, then returns step (4) operation;
(9) if be finished, then the target machine system transmits end of test (EOT) information by communicator to the developing engine system, and this end of test (EOT) information is test run end mark file;
(10) the developing engine system receives this end of test (EOT) information, and default standard output information and the test output information that receives compared, obtain the test run result, wherein, this standard output information is standard output file, described test output information is the test output file, with default standard output information and the test output information that receives compare into:
Use the file compare tool that default standard output file and the test output file that receives are compared.
In the middle of reality is used, the automatic operating method of embedded OS interface testing of the present invention, finished by developing engine and target machine (being embedded device) cooperation: developing engine compiles out all test run files, adopt communication apparatus to carry out uploading and downloading of file between developing engine and the target machine, download, the operation of test case program carried out in the target machine robotization successively to each test case, upload the test output file, deletion test procedure and the file that is generated; Embedded OS is handled the various system exception situations that may occur in the test procedure operational process automatically, guarantees the automatic continuation operation of follow-on test program.So just, can on the embedded device of limited storage resources, finish the operation of all test case programs automatically, test output file and the standard output file that uses the file compare tool that target machine is uploaded at the developing engine end compares at last, obtains test result.
Above-mentioned test case program has at least:
(1) corresponding standard output file of each test case program has write down the result who writes file after this test case program true(-)running, under this preserves when first operation test case program.
(2) the test case program all can generate an output file of the same name with standard output file at every turn behind the end of run in regression test, record is when inferior operation result, be called the test output file, we can learn whether this test case is moved correctly the comparison by test output file and standard output file in regression test.
(3) need the EXENAME of each test case program of assurance to have nothing in common with each other, avoid causing covering of the same name after the compiling, and the name of the output file of operation generation has nothing in common with each other the output file covering that the output file of avoiding certain test case to move is moved by other test case.
(4) each test case code all is placed in the different catalogues, corresponding one an of test case is carried out script, this execution script is finished when writing use-case, comprise five order lines, be followed successively by: download test procedure, operation test procedure, upload the test output file, delete test procedure, delete the test output file.The execution script of all test cases adopts identical naming.
Briefly, two kinds of correct or wrong situations can appear in the execution of interface method, carrying out correctness all needs to write some statements to output file, and to carry out the statement that correct and execution error writes output file be different, thereby whether the test case of relatively judging of the output file that can generate by operation in standard output file and the regression test is moved correct.Each test case all has an execution script of the same name, and all execution scripts can synthesize a big execution script, as the test execution script.Just annotate corresponding execution script if certain use-case has been made mistakes, there is no need to move once more, after defective (bug) is repaired, revise its execution script again, add operation in the test.
Wherein, above-mentioned target machine has at least:
● communication apparatus can connect with developing engine and carry out data communication;
● corresponding embedded OS possesses the driver of this communication apparatus, can realize a delivery means, utilizes this equipment and developing engine to carry out file transfer;
● corresponding embedded OS possesses control desk and file system at least, can carry out various file operations, can adopt the autoexec working procedure.
And above-mentioned developing engine has at least:
● communication apparatus can connect with target machine and carry out data communication;
● relative operation system possesses this communication apparatus driver, can realize a delivery means, utilizes this equipment and target machine to carry out file transfer;
● can be on the developing engine system platform exploitation code and compiling generate the target machine code.
The step of automatic operating method that realizes embedded OS interface testing of the present invention is as follows:
1, developing engine end:
(1) regularly from the source code server download code and compiling generate the image file of latest edition embedded OS and all test case programs;
(2) each test case is carried out script and synthesize " test execution script ";
(3) send notice reboot flag data by communication apparatus and restart system to the program of the waiting for notification target machine of target machine;
(4) wait certain hour and treat that target machine is restarted after, by communication apparatus the system image file transfer is carried out programming to target machine;
(5) wait for and upload required test execution script of target machine or test case program, wait for test output file and test run end mark file that the receiving target machine sends.
(6) receive the test run end mark file that target machine sends, ends file transfer uses compare tool standard of comparison output file and test output file to obtain the test run result.
2, target machine end:
(1) embedded OS of operation legacy version on the target machine, carry out the program of waiting on it and read the communication apparatus data in circulation always, just restarting systems when receiving the notice reboot flag data that developing engine sends, and prepare to receive the image file that developing engine sends;
(2) target machine receives image file and programming to embedded device by communication apparatus;
(3) start embedded OS, can call an autoexec operation automatically under control desk, this autoexec is carried out following operation:
A, system start-up can be divided into two kinds of situations: start first after system's programming newly is intact with new system and restart unusually because of generation in the test run process.This step is carried out different processing at these two kinds of different situations:
If the programming of new system starts after finishing first, then use transmission procedure to download " test execution script " from developing engine; If new system restarts unusually because of generation in the test run process, then according to the order line that writes down in " order line log file ", the test execution script from this order line deletion that comprises this order line more than order line, is only kept this order line order line content down.
" order line log file " write down the order line of new system because of occurring carrying out at last before the abnormal restarting, is that the execution of this order line causes system to be restarted.Because the test execution script is a fill order row successively, the order line of having carried out in order line excision test execution script according to record in " order line log file ", thus guarantee that test begins to carry out from the follow-up order line of not carrying out.
B, call " test execution script " operation, circulation is carried out following steps up to having moved all order lines (the circulation implementation sees also shown in Figure 2):
A) use transmission procedure to download a test case program from developing engine;
B) to note the program command of current operation before start carrying out this test case program capable in the order line log file for control desk.This document is all opened in the mode of writing at every turn, but not the mode of appending, no matter therefore control desk execution how many times is opened the operation that writes this document, this document all only writes down and opens the content that writes for the last time.
C) control desk is created the process of this test case program and is begun and carries out.In the implementation of test cases program process, various abnormal conditions may occur, take different robotizations to handle means at different abnormal conditions:
● being absorbed in deadlock (Deadlock)---the operation of test code may cause deadlock, if do not add the operation that processing will hinder the follow-on test code.System can monitor the operation of this process, can kill the process that behind one section special time, does not also have operation to finish automatically, if then continuation operation Next Command is capable to kill this process success, then restart system if kill the failure of this process, before restarting this order line the Be Controlled platform be recorded in the order line log file.
● be absorbed in that debugging mode (Debug)---test code may be absorbed in debug in operational process, if do not add the operation that processing will hinder the follow-on test code.After being absorbed in debug, system will attempt killing this process automatically, and then to continue the operation Next Command capable if kill the success of this process, then restarts system automatically if kill this process failure, before restarting this order line the Be Controlled platform be recorded in the order line log file.
● low memory (Out of Memory) if---system exists internal memory to reveal, the test procedure of carrying out some consumes memory may cause low free memory, this moment is if continue the situation that failure will appear causing moving because of low memory in other test procedure of operation, and being a last test procedure, this mistake causes, therefore control desk all was necessary Installed System Memory is monitored before test case program of every operation, if find that Installed System Memory is lower than certain designated value, then restart system, the test procedure action command row that causes low memory before restarting Be Controlled platform is recorded in the order line log file.
If abnormal conditions do not occur in the test case implementation, then continue to carry out following steps.
D) wait for that this test case program run finishes, and uploads the test output file to developing engine;
E) deletion test case program and test output file;
C, upload the end of test (EOT) logo file, notice developing engine end of test (EOT).
Above-mentioned in order to realize the robotization exception handling procedure, the special-purpose code of some tests that can in the exploitation code of system, add, for example deadlock monitor code and internal memory monitoring code etc., these codes are only just used by compiling when regression test through conditional compilation control, guarantee the independence of exploitation code and test code.
Above-mentioned institute is aided with script in steps and can realizes automatic operation, and has realized the function that automatic processing is unusual for embedded OS specially, thereby can finish the execution of all test cases automatically, need not manual intervention.
The present invention is described in further detail below in conjunction with description of drawings and instantiation.
The present invention can realize the automatic operating of interface testing on the embedded device of Elastos embedded OS and support thereof.Elastos is 32 a embedded OS, and it comprises system API and system services such as graphics system, file system and network system such as process, thread.Elastos can be widely used in the various embedded devices in fields such as industrial equipment, information household appliances, automotive electronics, handheld device.Target machine described here is the ARM embedded device of operation Elastos, and described developing engine is the computing machine that Windows2000 operating system is housed, and communication apparatus adopts serial equipment commonly used in the embedded development.
At first introduce some tool software of using in this automatic test example, comprising:
(1) CVS instrument.CVS is the source code management software that a cover is increased income, and adopts the CVS instrument to download required source code automatically from CVS source code server.The various correlated source codes of Elastos on stream all by Checkin to the CVS server, can be during test from the Elastos and the test code thereof of Checkout latest edition on this server.
(2) st/stt file transfer instrument.St/stt is that a cover that adopts serial port drive to realize is used for the instrument that file is uploaded and downloaded, and file is uploaded and promptly read file data and write serial ports, downloads promptly to read the file data that serial ports receives and write file again.St runs on target machine, and stt runs on developing engine.File transfer is finished in the st/stt collaborative work.At first developing engine end operation stt waits for the serial ports read-write and carries out corresponding file and write read operation, target machine end action command row " st FileName " expression is downloaded the FileName file from developing engine, and action command row " st^FileName " expression is uploaded the FileName file to developing engine.Transmission course sees also shown in Figure 3.
(3) armsys image file programming instrument.Promptly adopt armsys to be transferred to target machine on by serial ports (default serial port 1) the image file elastos.img of Elastos and write target machine RAM at action command row on the developing engine " armsys/w elastos.img ", can start Elastos after the programming success.
(4) wait/notify wait/notification tool.The step that adopts armsys programming image file is that developing engine is carried out the armsys order line earlier, restarts the transmission that the target machine system just begins image file then.In order to reach the order of automation mechanized operation, realized that wait/notify waits for notification tool.This instrument also is to adopt serial port drive to realize.Target machine operation wait reads serial data by circulation and waits for developing engine and send special data and finish just to wait for that developing engine is carried out notify and write special data toward serial ports, and the notification target machine finishes wait and also restarts, so that the programming system.
(5) cutbat batch processing cutting implement.This instrument from this order line deletion that comprises this order line more than order line, only keeps this order line order line content down with test execution script runtest.bat according to the order line that writes down in the order line log file.
(6) Windows Scheduled Tasks plan target.Developing engine adopts Windows plan target function to realize regularly carrying out a batch processing script.
(7) Windows windiff file compare tool.Windiff is used for the output file of compare test standard output file and test generation, obtains test result.
Preparation before the automatic test: adopt serial ports to link to each other target machine and developing engine, the operation wait of the target machine system order machine that awaits development is notified; Configure the Windows plan target.
The automatic test flow process is as follows:
Step 1: developing engine is the batch processing script of executive plan task regularly, and this script carries out following operation earlier:
Step 1.1: use the CVS instrument to download Elastos system and test source code;
Step 1.2: enter Elastos SDK development environment compiling system and test source code, all file destinations of compiling back are created under the bin catalogue;
Step 1.3: each test case is carried out script synthesize test execution script runtest.bat, use the copy order that the runtest.bat copy is a under the bin catalogue, and current directory is switched to the bin catalogue;
Step 1.4: carry out notify order notification target machine and restart;
Step 1.5: carry out " armsys/w elastos.img " order and wait for beginning programming image file;
Step 2: the target machine serial ports receives the reboot flag data that notify sends, and finishes wait, waits for and restarting after 5 seconds;
Step 3: developing engine armsys is uploaded to target machine with elastos.img, and the stt of developing engine operation afterwards waits for serial ports read-write transfer files;
Step 4: target machine receive and programming elastos.img file after start automatically, can call an autoexec autorun.bat operation automatically after entering system console, autorun.bat carries out following operation:
Step 4.1: system start-up can be divided into two kinds of situations: start first after system's programming newly is intact with new system and restart unusually because of generation in the test run process.This step is carried out different processing at these two kinds of different situations:
Start for the first time if the programming of new system is intact, then action command row " st runtest.bat " is downloaded test execution script runtest.bat from developing engine; If new system restarts unusually because of generation in the test run process, then move cutbat, according to the order line that writes down among the order line log file runcmd.log, runtest.bat from this order line deletion that comprises this order line more than order line, is only kept this order line order line content down.See following errorlevel:
if?exist?runcmd.log(
cutbat.exe?runtest.bat
)
if?not?exist?runcmd.log(
st?runtest.bat
)
Because runcmd.log generates in when test operation, and if found to have the runcmd.log file when starting would represent this startup since in the test run process generation restart unusually, need call cutbat; Start for the first time otherwise be that system's programming is intact, need to download the runtest.bat file.
Step 4.2: call test execution script runtest.bat operation, circulation is carried out following steps up to executing all order lines:
Step 4.2.1: use the st instrument to download a test case program from developing engine;
Step 4.2.2: control desk obtains current system free memory value, if the free memory value is lower than certain internal memory limits value (for example limiting minimum free memory is 500 pages), then restarts system, otherwise continues operation.So just, solved the unusual of low memory in the test process;
Step 4.2.3: the program command that control desk is noted current operation is capable in the runcmd.log file, promptly calls as minor function and carries out:
void?LogCmdLine()
{
wchar_t?szFullName[_MAX_PATH];
// open empty file runcmd.log with WriteMode, if this document exists, empty its content
FILE*pfout=_wfopen(L"runcmd.log",L"w");
assert(pfout!=NULL);
// record action command walks in the file
fwprintf(pfout，L"％s"，g_wszCmdLine);
fclose(pfout);
}
Wherein " g_wszCmdLine " is the order line that control desk is resolved the current operation of runtest.bat acquisition.
Step 4.2.4: control desk starts the deadlock watchdog routine, begins to enter and restarts countdown, promptly calls as minor function and carries out:
void?StartRebootCountDown()
{
ECODE?ec;
IDriver *pTestingDriver;
// obtain monitor service
ec=EzFindService(L"device:testingserver"，(IObject**)&pTestingDriver);
if(FAILED(ec)){
printf("Error:EzFindService?testingserver?failed?ec=0x％x\n",ec);
HaltTesting();
}
Be 300 seconds // maximum working time
UINT?uMaxTime=300000;
// add 10 seconds stand-by period again, after promptly arriving maximum working time, there is 10 second time to kill deadlock and advances
// journey if kill failure, will be restarted system after 10 seconds
uMaxTime+=10000;
EzByteBuf_Box?ezbbTimeOut(&uMaxTime,wcslen(wszMaxTime)+1);
// begin to restart countdown
pTestingDriver-＞Control(TSCommand_StartRebootCountDown,
ezbbTimeOut,
EZBYTEBUF_NULL,
NULL);
pTestingDriver-＞Release();
}
" device:testingserver " service is a kind of service that provides for test specially that realizes in system kernel in this function.The Elastos system provides timer routine (Timer), can carry out its call back function after a period of time of appointment, and call back function existed with the form of kernel thread after Timer created.Testingserver utilizes this specific character of Timer, (this time can be set to other value at 310 seconds before starting test process Timer to be set, wherein 300 seconds is maximum working time of test case process, waiting system killed the deadlock process in other 10 seconds, if kill failure and then restarted system after 10 seconds) enter call back function thread execution system afterwards and restart.The test case process should be finished or be killed within 310 seconds, and stopped the operation of Timer, otherwise the call back function thread will be performed, and restarted.The main code of " device:testingserver " service routine is as follows:
class?CTestingServer:public?Driver{
public:
CARAPI?Read(
/*[in]*/UINT64?u64Offset,
/*[in]*/UINT?uNumberOfBytesToRead，
/*[out]*/EzByteBuf?ebbData,
/*[out]*/IEvent**ppCompletionEvent);
CARAPI?Write(
/*[in]*/UINT64?u64Offset,
/*[in]*/EzByteBuf?ebbData,
/*[out]*/UINT*puNumberOfBytesWritten,
/*[out]*/IEvent**ppCompletionEvent);
CARAPI?Control(
/*[in]*/INT?nControlCode,
/*[in]*/EzByteBuf?ebbInData,
/*[out]*/EzByteBuf?ebbOutData,
/*[out]*/IEvent**ppCompletionEvent);
virtual?void?Dispose();
public:
ECODE?Initialize();
public:
DzTimer*m_pTimer;
};
void?CDECL?TimerRoutine(void*pvParameter)
{
kprintf("Testing-System:Timer?control?Rebooting...\n:);
BspReboot();
}
EXTERN?IDriver*CDECL?CreateTestingServer(uint_t?uDeviceNo,void*pvParameter)
{
CTestingServer*pTestingServer=new?CTestingServer;
if(NULL==pTestingServer){
kprintf("ERROR:new?CTestingServer:Not?enough?memory!\n");
return?NULL;
}
ECODE?ec=pTestingServer-＞Initialize();
if(FAILED(ec)){
delete?pTestingServer;
return?NULL;
}
pTestingServer-＞AddRef();
return?pTestingServer;
}
ECODE?CTestingServer∷Initialize()
{
uint_t?uTicks=DzMillisecondsToTicks(1000*1000);
m_pTimer=new?DzTimer(uTicks,TimerRoutine,NULL);
if(NULL==m_pTimer){
kprintf("ERROR:new?Timer:Not?enough?memory!\n");
return?E_OUT_OF_MEMORY;
}
return?NOERROR;
}
ECODE?CTestingServer∷Control(
/*[in]*/INT?nControlCode,
/*[in]*/EzByteBuf?ebbInData,
/*[out]*/EzByteBuf?ebbOutData,
/*[out]*/IEvent**ppCompletionEvent)
{
uint32_t?uTime=0;
uint_t?uTicks=0;
switch(nControlCode){
case?TSCommand?StartRebootCountDown:
uTime=*(uint32_t*)(wchar_t*)ebblnData;
uTicks=DzMillisecondsToTicks(uTime);
m_pTimer-＞Restart(uTicks);
break;
case?TSCommand_CancelRebootCountDown:
m_pTimer-＞Cancel();
break;
default:
kprintf("Unknown?TestingServer?Command.\n");
break;
}
return?NOERROR;
}
The CTestingServer class is to drive the pseudo-class that drives that programmed method is realized according to Elastos, compile with kernel code, call during system start-up that CreateTestingServer has created the CTestingServer object and " device:testingserver " service that it is registered as allows control desk obtain and calls correlation technique.Call CTestingServer ∷ Initialize during the CTestingServer Object Creation and created the Timer object.The TimerRoutine function is the Timer call back function, and it calls the BspReboot function and is used to restart system.CTestingServer ∷ Control has two control words: the TSCommand_StartRebootCountDown control word is used to start the Timer object, begin to restart countdown, parameter ebbInData is used to transmit the relative expiration time of Timer object (promptly restarting the countdown time) of control desk appointment; The TSCommand_CancelRebootCountDown control word is used to cancel the Timer object of operation, ends to restart countdown.
Step 4.2.5: control desk is created test case process and operation, promptly calls as minor function and carries out:
ECODE?RunExe(wchar_t*pwszCmd,wchar_t*pwszArgs,BOOL?bBackGround)
{
ECODE?ec=NOERROR;
IProcess*pIProcess;
// establishment test case process
ec=EzCreateProcess(pwszCmd,pwszArgs,&pIProcess);
if(ec==NOERROR){//Create?process?succeeded
ECODE?ec1;
WaitResult?wr;
INT?ms=300000;
// waiting process is end of run in 300 seconds
ec1=pIProcess-＞WaitForExit(ms,&wr);
if(SUCCEEDED(ec1)&&(WaitResult_TimedOut==wr)){
// generation is overtime, kills this process
pIProcess-＞Kill();
wprintf(L"Testing-System:Deadlock?process?was?killed.\n");
}
}
pIProcess-＞Release();
}
return?ec;
}
After creating the success of test case process, (this time can be set to other value) allows process move to wait for 300 seconds at most, if wait timeout then kills this process, so that the operation of follow-up process.If entered debug in this process operational process, system can jump among the DebuggerHandler automatically and carry out, and special in DebuggerHandler is that following processing function has been added in test, just calls this function and carry out when entering DebuggerHandler:
void?TestingDebuggerHandler()
{
// judge it is kernel debug or user is debug
if(IS_IN_KERNEL_MODE(pContext)){
kprintf("Kernel?debugger!\n");
}
else{
kprintf("User?debugger!\n");
if(NULL!=pCurrentProcess){
// obtain current process
CProcess*pCurrentProcess=GetCurrentProcess();
// kill the process that enters user debug
pCurrentProcess-＞Kill();
}
}
// enter kernel debug or kill the failure of user debug process, restart system
BspReboot();
return;
}
Kill the debug process if system is absorbed in user debug, so that operation follow-on test code, then call the BspReboot function and restart system if kill failure; If be absorbed in kernel debug, then call the BspReboot function and restart system.So just, solved and entered the unusual of debug in the test process.
Step 4.2.6: control desk is ended the operation of deadlock watchdog routine, and countdown is restarted in cancellation, promptly calls as minor function and carries out:
void?CancelRebootCountDown()
{
ECODE?ec;
IDriver *pTestingDriver;
// obtain monitor service
ec=EzFindService(L"device:testingserver"，(IObject**)&pTestingDriver);
if(FAILED(ec)){
printf("Error:EzFindService?testingserver?failed?ec=0x％x\n",ec);
HaltTesting();
}
Countdown is restarted in // cancellation
pTestingDriver-＞Control(TSCommand_CancelRebootCountDown,
EZBYTEBUF_NULL,
EZBYTEBUF_NULL,
NULL);
pTestingDriver-＞Release();
}
Call " device:testingserver " out-of-service Timer operation, be absorbed in deadlock and can not be killed if process has taken place step 4.2.5, control desk just can not call the CancelRebootCountDown function so, system can enter Timer call back function thread execution system automatically after the process operation begins 310 seconds restarts, and has so just solved and has been absorbed in the unusual of deadlock in the test process.
Step 4.2.7: use st to upload the output file that this test case generates to developing engine;
Step 4.2.8: delete this test case program and output file;
Step 4.3: target machine executes among the runtest.bat after all order lines, and all test case end of runs of runcmd.log file mark are uploaded in operation " st runcmd.log ".
Step 4.4: developing engine end stt monitors when runcmd.log is uploaded and withdraws from automatically, and this moment, stt received all test output files.
Step 4.5: developing engine uses windiff that standard output file is compared with the test output file and draws the test run result.
For the test procedure that causes system exception, they can generate empty output file or not generate output file, need rerun these test case programs with orientation problem.Just annotate corresponding execution script if certain test case program has been made mistakes, there is no need to move once more, after bug repairs, revise its execution script again, add operation in the test.
Above-mentioned is the special code that adds of test in system kernel and control desk, only controls through conditional compilation and just used the independence of assurance exploitation code and test code by compiling when regression test.
Adopted the automatic operating method of interface testing in the above-mentioned embedded OS, owing in the developing engine system, realized automatic compiled code, and notification target machine system begins test, and automatically upload operation system image file and test case program, downloads the test output file automatically; Simultaneously, in the target machine system, realized automatic download, operation and deletion test procedure, upload the test output file, automatically handle various system exceptions, and the test execution script can continue to move next test procedure after the assurance abnormality processing, notify developing engine to finish test at last, thereby realized on the embedded device of limited storage resources, carrying out the automatic operating of embedded OS interface testing, need not manual intervention, human resources have been saved, effectively shorten the regression tested cycle, guaranteed the propelling of embedded system development quick and stable, stable and reliable for performance.Moreover, the automatic operating method of interface testing is not limited to operating system interface in the embedded OS of the present invention, test for the application interface on the embedded OS is suitable for too, can bring benefit for application and development, the scope of application is comparatively extensive, for further developing of embedded system and upper layer software (applications) thereof established solid foundation.
In this instructions, the present invention is described with reference to its certain embodiments.But, still can make various modifications and conversion obviously and not deviate from the spirit and scope of the present invention.Therefore, instructions and accompanying drawing are regarded in an illustrative, rather than a restrictive.
Claims (10)
1, the automatic operating method of interface testing in a kind of embedded OS, the host's test target machine system that comprises developing engine system and embedded OS, communicator in the described developing engine system is connected with communicator in the target machine system by data link, it is characterized in that described method may further comprise the steps:
(1) the developing engine system regularly generates embedded OS tested object, test execution script and test case information processing;
(2) the developing engine system is transferred to described embedded OS tested object in the target machine system by communicator;
(3) the target machine system starts embedded OS and from the processing of developing engine system downloads test execution script;
(4) the target machine system carries out the test execution script, from developing engine system downloads test case information;
(5) target machine system operation test case information and generation test output information;
(6) the target machine system transmits this test output information by communicator to the developing engine system;
(7) current test case information of target machine system-kill and test output information;
(8) the target machine system judges whether the test execution script is finished, if be not finished, then returns step (4) operation;
(9) if be finished, then the target machine system transmits end of test (EOT) information by communicator to the developing engine system;
(10) the developing engine system receives this end of test (EOT) information, and default standard output information and the test output information that receives are compared, and obtains the test run result.
2, the automatic operating method of interface testing in the embedded OS according to claim 1 is characterized in that, described regular generation embedded OS tested object, test execution script and test case information may further comprise the steps:
(1) system regularly downloads up-to-date code from the source code server;
(2) above-mentioned code compile is generated image file and all test case programs of embedded OS;
(3) system synthesizes the pairing execution script of each test case program and generation test execution script.
3, the automatic operating method of interface testing in the embedded OS according to claim 2 is characterized in that, the described embedded OS tested object is transferred in the target machine system may further comprise the steps:
(1) the developing engine system sends notice reboot flag data to the target machine system by communicator, and notification target machine system restarts;
(2) the target machine system receives the notice reboot flag data that the developing engine system sends, restarting systems;
(3) after the developing engine system treats that the target machine system restarts, be transferred in the target machine system by the image file of communication device with embedded OS;
(4) the target machine system receives the image file that the developing engine system sends by communicator, and with its programming in the embedded device of target machine system.
4, according to the automatic operating method of interface testing in claim 2 or the 3 described embedded OSs, it is characterized in that described source code server is CVS source code management server, ClearCase source code management server or SourceSafe source code management server.
5, according to the automatic operating method of interface testing in each described embedded OS in the claim 1 to 3, it is characterized in that described startup embedded OS and may further comprise the steps from the processing of developing engine system downloads test execution script:
(1) the target machine system judges that this startup belongs to any in following two kinds of situations: start first after the programming of new system is intact, new system restarts unusually because of taking place in the test run process;
(2) if the programming of new system starts after intact first, then the target machine system by communicator from developing engine system downloads test execution script;
(3) if new system restarts unusually because of generation in the test run process, then, only keep the order line content of not carrying out with the order line deletion of having carried out in the test execution script.
According to the automatic operating method of interface testing in each described embedded OS in the claim 1 to 3, it is characterized in that 6, described target machine system operation test case information may further comprise the steps:
(1) to note the program command of current operation before start carrying out this test case information capable in system;
(2) process of the corresponding test case information of system creation and begin to carry out, and the appearance of the various abnormal conditions of monitoring in real time in the process of implementation of test cases process;
(3) if the operation of the test case process system that makes is absorbed in deadlock, then the process that does not also have operation to finish will be killed by system behind one section special time, if kill this process success, it is capable then to continue the operation Next Command; If kill this process failure, then carry out system and restart;
(4) if the operation of the test case process system that makes is absorbed in debugging mode, then this process will be killed by system, if kill this process success, it is capable then to continue the operation Next Command; If kill this process failure, then carry out system and restart;
(5) the Installed System Memory deficiency be lower than the systemic presupposition value if the operation of test case process makes, then carry out system and restart as if the discovery Installed System Memory.
7, the automatic operating method of interface testing in the embedded OS according to claim 6, it is characterized in that, carry out the real-time monitoring of abnormal conditions by deadlock monitor code, debugging mode monitor code, the internal memory monitoring code that in the exploitation code of system, adds through conditional compilation control.
According to the automatic operating method of interface testing in each described embedded OS in the claim 1 to 3, it is characterized in that 8, described end of test (EOT) information is test run end mark file.
According to the automatic operating method of interface testing in each described embedded OS in the claim 1 to 3, it is characterized in that 9, described standard output information is standard output file, described test output information is the test output file.
10, the automatic operating method of interface testing in the embedded OS according to claim 9 is characterized in that, described with default standard output information and the test output information that receives compare into:
Use the file compare tool that default standard output file and the test output file that receives are compared.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101168679A CN100458729C (en) | 2006-09-29 | 2006-09-29 | Automatic operating method for interface test in embedded operating system |
| HK07110143.8A HK1102177A1 (en) | 2006-09-29 | 2007-09-18 | Automatic processing method for interface testing in embedded operation system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101168679A CN100458729C (en) | 2006-09-29 | 2006-09-29 | Automatic operating method for interface test in embedded operating system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1932776A true CN1932776A (en) | 2007-03-21 |
| CN100458729C CN100458729C (en) | 2009-02-04 |
Family
ID=37878621
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101168679A Expired - Fee Related CN100458729C (en) | 2006-09-29 | 2006-09-29 | Automatic operating method for interface test in embedded operating system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100458729C (en) |
| HK (1) | HK1102177A1 (en) |
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101178687B (en) * | 2007-11-26 | 2010-06-09 | 中兴通讯股份有限公司 | Software regression testing method |
| CN101271423B (en) * | 2008-05-19 | 2010-06-16 | 中兴通讯股份有限公司 | Software interface test approach and system |
| CN101944060A (en) * | 2010-09-10 | 2011-01-12 | 华南理工大学 | Embedded software-based fineness detection method |
| CN101615159B (en) * | 2009-07-31 | 2011-03-16 | 中兴通讯股份有限公司 | Off-line test system, local data management method thereof and corresponding device |
| CN102129373A (en) * | 2011-03-09 | 2011-07-20 | 湖南超视物联智能网络科技有限公司 | Method based on internet-of-things terminal equipment driver software design framework |
| CN102222036A (en) * | 2010-04-14 | 2011-10-19 | 阿里巴巴集团控股有限公司 | Automatic testing method and equipment |
| CN102271066A (en) * | 2011-08-22 | 2011-12-07 | 中兴通讯股份有限公司 | Automatic intelligent command line testing method and system |
| CN101351008B (en) * | 2007-07-20 | 2011-12-28 | 英华达（上海）科技有限公司 | Method for debugging a test platform and system for testing handhold set thereof |
| CN101604290B (en) * | 2009-06-05 | 2012-05-16 | 中国移动（深圳）有限公司 | Background module test method and backstage module test system |
| CN102495798A (en) * | 2011-12-01 | 2012-06-13 | 盛科网络（苏州）有限公司 | Automated regression testing method and system |
| CN101527652B (en) * | 2009-04-21 | 2012-07-11 | 杭州华三通信技术有限公司 | Method for resuming default interface configuration and device thereof |
| CN103559114A (en) * | 2013-11-12 | 2014-02-05 | 福建联迪商用设备有限公司 | Embedded module driving functional testing system and method |
| CN103631713A (en) * | 2013-11-04 | 2014-03-12 | 中安消技术有限公司 | ERP software automated testing system and method |
| CN103995777A (en) * | 2014-05-29 | 2014-08-20 | 上海科梁信息工程有限公司 | Automatic embedded software block box testing system and method |
| CN104360920A (en) * | 2014-12-02 | 2015-02-18 | 微梦创科网络科技（中国）有限公司 | Automatic testing method and device for interface |
| CN104731701A (en) * | 2013-12-23 | 2015-06-24 | 展讯通信（上海）有限公司 | Test system and method and device for executing test tasks |
| WO2017036068A1 (en) * | 2015-08-28 | 2017-03-09 | 中兴通讯股份有限公司 | Method and system for realizing software automatic test |
| CN108572892A (en) * | 2017-03-14 | 2018-09-25 | 大唐移动通信设备有限公司 | A kind of off-line test method and apparatus based on PowerPC multi-core processors |
| CN108647141A (en) * | 2018-04-26 | 2018-10-12 | 腾讯科技（深圳）有限公司 | Automatic test approach, device, computer-readable medium and electronic equipment |
| CN109189672A (en) * | 2018-08-13 | 2019-01-11 | 中国平安人寿保险股份有限公司 | Automatic test approach, server and the computer readable storage medium of micro services |
| CN110287126A (en) * | 2019-07-04 | 2019-09-27 | 上海睿赛德电子科技有限公司 | A kind of unit testing frame suitable for embedded system |
| CN110737581A (en) * | 2018-07-20 | 2020-01-31 | 北京君正集成电路股份有限公司 | testing methods and devices |
| CN111538599A (en) * | 2020-04-23 | 2020-08-14 | 杭州涂鸦信息技术有限公司 | LINUX-based multithreading deadlock problem positioning method and system |
| CN112035346A (en) * | 2020-08-25 | 2020-12-04 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Automatic testing method, system and medium based on embedded DSP operating system |
| CN112202628A (en) * | 2020-09-08 | 2021-01-08 | 杭州涂鸦信息技术有限公司 | WiFi module serial port protocol automatic test system and method |
| CN116185880A (en) * | 2023-04-27 | 2023-05-30 | 北京翼辉信息技术有限公司 | Automatic test method, device, equipment and medium for embedded system |
| CN116820992A (en) * | 2023-07-05 | 2023-09-29 | 上海灵动微电子股份有限公司 | Automatic testing method and system for embedded software |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102023033B (en) * | 2009-09-09 | 2012-12-05 | 北大方正集团有限公司 | Automatic test method and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW581968B (en) * | 2000-08-21 | 2004-04-01 | Bsquare Corp | Method and apparatus for producing user interfaces and device functionality for processor-based devices having embedded operating system and programming framework |
| CN1310446C (en) * | 2002-08-20 | 2007-04-11 | 华为技术有限公司 | Mirror image test method |
| CN1310150C (en) * | 2002-11-21 | 2007-04-11 | 中兴通讯股份有限公司 | Embedded software test method |
| CN100359485C (en) * | 2003-07-10 | 2008-01-02 | 华为技术有限公司 | Testing device and method for flush-bonding system |
-
2006
- 2006-09-29 CN CNB2006101168679A patent/CN100458729C/en not_active Expired - Fee Related
-
2007
- 2007-09-18 HK HK07110143.8A patent/HK1102177A1/en not_active IP Right Cessation
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101351008B (en) * | 2007-07-20 | 2011-12-28 | 英华达（上海）科技有限公司 | Method for debugging a test platform and system for testing handhold set thereof |
| CN101178687B (en) * | 2007-11-26 | 2010-06-09 | 中兴通讯股份有限公司 | Software regression testing method |
| CN101271423B (en) * | 2008-05-19 | 2010-06-16 | 中兴通讯股份有限公司 | Software interface test approach and system |
| CN101527652B (en) * | 2009-04-21 | 2012-07-11 | 杭州华三通信技术有限公司 | Method for resuming default interface configuration and device thereof |
| CN101604290B (en) * | 2009-06-05 | 2012-05-16 | 中国移动（深圳）有限公司 | Background module test method and backstage module test system |
| CN101615159B (en) * | 2009-07-31 | 2011-03-16 | 中兴通讯股份有限公司 | Off-line test system, local data management method thereof and corresponding device |
| CN102222036A (en) * | 2010-04-14 | 2011-10-19 | 阿里巴巴集团控股有限公司 | Automatic testing method and equipment |
| CN102222036B (en) * | 2010-04-14 | 2014-11-12 | 阿里巴巴集团控股有限公司 | Automatic testing method and equipment |
| CN101944060A (en) * | 2010-09-10 | 2011-01-12 | 华南理工大学 | Embedded software-based fineness detection method |
| CN102129373A (en) * | 2011-03-09 | 2011-07-20 | 湖南超视物联智能网络科技有限公司 | Method based on internet-of-things terminal equipment driver software design framework |
| CN102271066A (en) * | 2011-08-22 | 2011-12-07 | 中兴通讯股份有限公司 | Automatic intelligent command line testing method and system |
| CN102495798A (en) * | 2011-12-01 | 2012-06-13 | 盛科网络（苏州）有限公司 | Automated regression testing method and system |
| CN103631713A (en) * | 2013-11-04 | 2014-03-12 | 中安消技术有限公司 | ERP software automated testing system and method |
| CN103631713B (en) * | 2013-11-04 | 2017-01-04 | 中安消技术有限公司 | ERP software automatization test system and method |
| CN103559114A (en) * | 2013-11-12 | 2014-02-05 | 福建联迪商用设备有限公司 | Embedded module driving functional testing system and method |
| CN103559114B (en) * | 2013-11-12 | 2015-08-19 | 福建联迪商用设备有限公司 | Flush bonding module drives function test system and method |
| CN104731701A (en) * | 2013-12-23 | 2015-06-24 | 展讯通信（上海）有限公司 | Test system and method and device for executing test tasks |
| CN104731701B (en) * | 2013-12-23 | 2018-04-27 | 展讯通信（上海）有限公司 | Test system and the method and apparatus for performing test assignment |
| CN103995777A (en) * | 2014-05-29 | 2014-08-20 | 上海科梁信息工程有限公司 | Automatic embedded software block box testing system and method |
| CN104360920B (en) * | 2014-12-02 | 2018-06-26 | 微梦创科网络科技（中国）有限公司 | A kind of automatic interface testing method and device |
| CN104360920A (en) * | 2014-12-02 | 2015-02-18 | 微梦创科网络科技（中国）有限公司 | Automatic testing method and device for interface |
| WO2017036068A1 (en) * | 2015-08-28 | 2017-03-09 | 中兴通讯股份有限公司 | Method and system for realizing software automatic test |
| CN108572892A (en) * | 2017-03-14 | 2018-09-25 | 大唐移动通信设备有限公司 | A kind of off-line test method and apparatus based on PowerPC multi-core processors |
| CN108572892B (en) * | 2017-03-14 | 2020-10-27 | 大唐移动通信设备有限公司 | PowerPC multi-core processor-based offline test method and device |
| CN108647141B (en) * | 2018-04-26 | 2022-09-09 | 腾讯科技（深圳）有限公司 | Automatic test method, device, computer readable medium and electronic equipment |
| CN108647141A (en) * | 2018-04-26 | 2018-10-12 | 腾讯科技（深圳）有限公司 | Automatic test approach, device, computer-readable medium and electronic equipment |
| CN110737581A (en) * | 2018-07-20 | 2020-01-31 | 北京君正集成电路股份有限公司 | testing methods and devices |
| CN109189672A (en) * | 2018-08-13 | 2019-01-11 | 中国平安人寿保险股份有限公司 | Automatic test approach, server and the computer readable storage medium of micro services |
| CN109189672B (en) * | 2018-08-13 | 2024-03-29 | 中国平安人寿保险股份有限公司 | Automatic testing method for micro-service, server and computer readable storage medium |
| CN110287126A (en) * | 2019-07-04 | 2019-09-27 | 上海睿赛德电子科技有限公司 | A kind of unit testing frame suitable for embedded system |
| CN111538599A (en) * | 2020-04-23 | 2020-08-14 | 杭州涂鸦信息技术有限公司 | LINUX-based multithreading deadlock problem positioning method and system |
| CN112035346A (en) * | 2020-08-25 | 2020-12-04 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Automatic testing method, system and medium based on embedded DSP operating system |
| CN112202628A (en) * | 2020-09-08 | 2021-01-08 | 杭州涂鸦信息技术有限公司 | WiFi module serial port protocol automatic test system and method |
| CN116185880A (en) * | 2023-04-27 | 2023-05-30 | 北京翼辉信息技术有限公司 | Automatic test method, device, equipment and medium for embedded system |
| CN116820992A (en) * | 2023-07-05 | 2023-09-29 | 上海灵动微电子股份有限公司 | Automatic testing method and system for embedded software |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100458729C (en) | 2009-02-04 |
| HK1102177A1 (en) | 2007-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1932776A (en) | Automatic operating method for interface test in embedded operating system | |
| CN1200345C (en) | Arithmetic processor, method for communication between objects and robot | |
| CN1279449C (en) | Microprocessor | |
| CN1612088A (en) | Processor system, instruction sequence optimization device, and instruction sequence optimization program | |
| CN1313924C (en) | System and method for operation of portable operation | |
| CN1275152C (en) | System and method for manufacturing and updating insertable portable operating system module | |
| CN1581635A (en) | Information processing device and method and readable medium of computer | |
| CN1768275A (en) | Test emulation device, test module emulation device, and recording medium recorded with programs for the devices | |
| CN1677365A (en) | Test case inheritance controlled via attributes | |
| CN1821956A (en) | Using existing content to generate active content wizard executables for execution of tasks | |
| CN101069157A (en) | A method and system for accessing resources | |
| CN1876334A (en) | Device and method for controlling robot | |
| CN1564136A (en) | Realizing method of cross regulator based on EJTAG components of targeting machine | |
| CN1959631A (en) | Self-contained technology for installing application software based on ITRON | |
| CN1612122A (en) | Service provision device, service provision program, recording medium, and service provision method | |
| CN1808393A (en) | Automatic backup and recovery device for computer system and implementation method method thereof | |
| CN1862511A (en) | Method for testing software unit | |
| CN1577291A (en) | Program debug apparatus, program debug method and program | |
| CN1098501C (en) | simulator and method for SQL relational database | |
| CN1776621A (en) | Program converting method | |
| CN1194295C (en) | Program changing device, method and computer program for treating program changing | |
| CN1885263A (en) | Program actuating system, and its programming, analyzing, and managing system, and checking device and programming system therefor | |
| CN1241078C (en) | Programmable controller system | |
| CN1690956A (en) | Programme projecting device and method | |
| CN100343806C (en) | System and method for transplanting central processor to be processed according to requirment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1102177 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: GR Ref document number: 1102177 Country of ref document: HK |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090204 Termination date: 20180929 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |