CN102736975A - Test method and test system for testing trusted computing password support platform - Google Patents
Test method and test system for testing trusted computing password support platform Download PDFInfo
- Publication number
- CN102736975A CN102736975A CN2011100925047A CN201110092504A CN102736975A CN 102736975 A CN102736975 A CN 102736975A CN 2011100925047 A CN2011100925047 A CN 2011100925047A CN 201110092504 A CN201110092504 A CN 201110092504A CN 102736975 A CN102736975 A CN 102736975A
- Authority
- CN
- China
- Prior art keywords
- test
- data
- test case
- log file
- value
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 452
- 238000010998 test method Methods 0.000 title claims abstract description 10
- 238000006243 chemical reaction Methods 0.000 claims abstract description 35
- 238000004806 packaging method and process Methods 0.000 claims abstract description 16
- 230000006399 behavior Effects 0.000 claims description 31
- 238000000034 method Methods 0.000 claims description 23
- 238000012795 verification Methods 0.000 claims description 18
- 238000012856 packing Methods 0.000 claims description 12
- 238000013524 data verification Methods 0.000 claims description 5
- 238000000528 statistical test Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 abstract description 8
- 238000007726 management method Methods 0.000 abstract description 2
- 238000007619 statistical method Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012858 packaging process Methods 0.000 description 2
- 238000013522 software testing Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a test method and a test system for testing a trusted computing password support platform. The test method comprises the following steps of: obtaining atom behavior and packaging the atom behavior as a test case; analyzing the test case to obtain the test case data; calling a data conversion interface to convert the analyzed test case data into a network byte order, and outputting a test expected value to a journal file; inputting the analyzed test case data in a trusted computing interface for test, and returning back a test actual value to the journal file; verifying the test actual value and the test expected value, and recording the check result in the journal file; and analyzing and counting the test result, and outputting a test statistical result. By the technology provided by the invention, convenient and fast test management and test statistical analysis functions can be realized, and the test efficiency is improved.
Description
Technical Field
The invention relates to the field of computers, in particular to a testing method and a testing system for testing a trusted computing password support platform.
Background
Software testing is an important means for ensuring software quality, and for some software requiring high reliability and high safety, the testing cost may be 3 to 5 times of all the cost for developing the whole software project, so that the software testing work must be considered and strengthened for successfully developing high-quality software products.
The trusted computing password support platform is a solution for providing high security and high reliability for users, the quality of the product has higher requirements in all aspects, and the existing test of the trusted computing password support platform based on a trusted cryptographic Service module (TSM) (TCM Service module) mainly tests the TSM function based on a business process, the test method is implemented by calling a trusted computing interface Tspi (TCG Service Provider interface) provided by the trusted computing password support platform based on the business function, the test work mainly focuses on verifying the correctness of the forward function of the business, and the software test work is difficult to develop in the type test for other software quality characteristics needing attention, such as the software robustness and the like; and the test data in the test system is hard coded, and the source file of the test system needs to be modified if the addition and deletion or modification of the test data are needed in the test process.
In summary, the testing of the prior art TSM-based trusted computing cryptography support platform has the following disadvantages: the testing function of a trusted computing interface Tspi externally provided by the TSM is lacked; the test behavior cannot be recorded in real time; lack of test statistics and analysis; the function of assembling test cases for atomic behaviors is lacking.
Disclosure of Invention
The invention aims to provide a test method and a test system for testing a trusted computing password support platform, which realize convenient test management and test statistical analysis functions.
In order to solve the technical problem, the invention discloses a testing method for testing a trusted computing password support platform, which comprises the following steps:
acquiring atomic behaviors and packaging the atomic behaviors into a test case;
analyzing the test case to obtain test case data;
calling a data conversion interface to convert the analyzed test case data into a network byte sequence and outputting a test expected value to a log file;
inputting the analyzed test case data into a trusted computing interface for testing, and returning a test actual value to a log file;
verifying the actual test value and the expected test value, and recording the verification result in the log file;
and analyzing and counting the test result and outputting the test statistical result.
Further, the step of obtaining atomic behaviors and packaging into test cases comprises:
establishing a test case template;
acquiring a default test case and an atomic behavior of a system;
selecting needed atomic behaviors to a test case template, and packaging the atomic behaviors into a test case;
and when a plurality of test cases are needed to be used after the test is finished, packaging the test cases one by circulating the steps and establishing a test case library.
Further, the step of analyzing the test case to obtain the test case data includes:
identifying whether the input parameters have test command keywords, if so, triggering a test command alarm switch, and if not, skipping the step;
identifying the name of the test case according to the input parameters, running the test case if the test case exists in the test case library, and returning the wrong test case name if the test case exists in the test case library;
and reading the data of the identified test case name as the data input of the test case, and if the test case corresponds to a plurality of test data, circularly reading the test data and inputting the test data into the test case.
Further, the step of verifying the actual test value and the expected test value and recording the verification result in the log file includes:
obtaining a test expected value and a test actual value in a log file and verifying;
if the test expected value is consistent with the actual value, the test verification result is marked as success in the log, and the test passing of the log is recorded in the log file;
if the test expected value does not accord with the actual value, the test verification result is identified as failure in the log, the test failure is recorded in the log file, and the state of the test command alarm switch is continuously judged.
Further, the judging the state of the test command alarm switch includes:
if the test expected value is not consistent with the actual value and the test command alarm switch is closed, printing an expected result and an actual result in the log and continuing the subsequent operation;
if the expected test value is not consistent with the actual value and the alarm switch is turned on, the expected result and the actual result are printed in the log, and the test process is interrupted.
Further, the step of calling the data conversion interface to convert the analyzed test case data into a network byte sequence and outputting the test expected value to the log file includes:
calling a data conversion interface to print a data label on the input test data according to the data type;
and printing the test expected value to a log file according to the data label and the input test data sequence, and adding a statistical keyword in the log file.
Further, the step of inputting the analyzed test case data into the trusted computing interface for testing and returning the actual test value to the log file comprises:
testing by calling the test data input and analyzed by the trusted computing interface;
judging the state of the returned test result of the trusted computing interface, if the test result is successfully returned, calling the data conversion interface to perform data conversion on the returned test result, marking a data label on the data of the returned test result, printing the actual value returned to the log file according to the sequence of the data of the returned test result, and adding a statistical keyword in the log file; and if the test result is failed to be returned, directly outputting a test result return state to the log file and adding the statistical keywords.
Further, the analyzing the statistical test result and outputting the test statistical result includes:
acquiring a log file in a test process;
analyzing and counting the passing rate of the test cases according to the statistical keywords inserted in the log file;
and outputting a test statistical result.
The invention also discloses a test system for testing the trusted computing password support platform, which comprises the following steps: the system comprises a test case configuration module, a test case analysis module, a test execution module, a test data verification module and a test log analysis module; wherein,
the test case configuration module is used for acquiring atomic behaviors and packaging the atomic behaviors into test cases;
the test case analysis module is used for analyzing the test cases according to the input parameters to obtain test case data;
the test execution module is used for converting the analyzed test case data and executing the test;
the test data verification module is used for verifying the actual test value and the expected test value, if the actual test value and the expected test value are consistent, the verification is successful, the test passing is recorded in the log file, and otherwise, the test failing is recorded in the log file;
and the test log analysis module is used for counting the passing rate of the test cases and outputting test statistical results.
Further, the test execution module includes: the data conversion interface and the trusted computing interface; wherein,
the data conversion interface is used for converting the analyzed test case data into a network byte sequence and outputting a test expected value to a log file; the data conversion interface further comprises a packing unit for performing byte order conversion and packing on the data and a debugging unit for transmitting the data;
and the trusted computing interface is used for inputting the analyzed test case data into the trusted computing interface for testing and returning the actual test value to the log file.
The invention can record detailed test behavior logs when the trusted computing password support platform is tested, test cases can automatically count test results and collect error logs based on the running of the invention, and the invention also provides the function of configuring the test cases according to the test behaviors, thereby improving the test efficiency.
Drawings
FIG. 1 is a flow chart of a test method of the present invention;
FIG. 2 is a logic diagram of the data conversion performed by the data conversion interface (Tspi) according to the present invention;
FIG. 3 is a flow chart of the present invention packing unit (Bsg) converting input data into a network byte-ordered byte stream;
FIG. 4 is a flowchart illustrating a debugging unit (Debug) outputting the converted endian data according to a predetermined output format;
FIG. 5 is a flowchart of the trusted computing interface (Tspi) performing testing in accordance with the present invention;
FIG. 6 is a logic diagram of a verification process of the present invention;
FIG. 7 is a logical block diagram of the test system of the present invention.
Detailed Description
The principles and features of this invention are described below in conjunction with the following drawings, which are set forth by way of illustration only and are not intended to limit the scope of the invention.
An embodiment of the present invention discloses a testing method for testing a trusted computing password support platform, and fig. 1 is a flowchart of the testing method of the present invention, and as shown in fig. 1, the method includes:
step 101: acquiring atomic behaviors and packaging the atomic behaviors into a test case;
wherein the Test Case (Test Case) is a set of Test input conditions, execution conditions and expected results compiled for a particular target in order to Test a certain program path or verify whether a certain specific requirement is met; atomic behavior refers to a specific behavioral step that describes the input conditions, execution conditions, and expected output results of a test.
In this embodiment, the process of packaging the test case is as follows: firstly, starting a test case configuration module, establishing a new test case template, reading a default test case and an atomic behavior in a system, selecting a required atomic behavior or a default test case to the test case template, or manually modifying the required atomic behavior or the default test case according to the requirement and then adding the modified test case template to the test case template, and finally packaging the added or modified test case template into a complete test case; of course, when a test is completed, multiple test cases may be needed, and at this time, the required multiple test cases may be configured through the above-mentioned packaging process according to the test plan, and the configured test cases are stored to form a test case library.
Step 102: analyzing the test case to obtain test case data;
the input parameters refer to keywords for triggering the test case to run, and the keywords comprise test command keywords and test case name keywords; the test case data refers to a set of test input conditions compiled for a certain test case.
In this embodiment, the process of analyzing the test case is as follows: identifying whether the input parameters have test command keywords, in the embodiment, a keyword (such as A) can be set in advance to represent that the test command keywords are stored in the system, if the input parameters contain the keyword A, the test command alarm switch is triggered, and if not, the step is skipped to continue analyzing the subsequent part; and then, identifying the test case name according to the input parameters, running the test case if the test case name exists in the test case library, and returning the wrong test case name if the test case name does not exist in the test case library. The running of the test case refers to reading test data corresponding to the test case as data input of the test case, and if the test case corresponds to a plurality of test data, circularly reading the test data and inputting the test data into the test case. And continuously analyzing whether the input parameters have test cases to be executed or not, and if so, circulating the analysis process until all the test cases corresponding to the input parameters in the test case library are analyzed.
Step 103: calling a data conversion interface to convert the analyzed test case data into a network byte sequence and outputting a test expected value to a log file;
in this embodiment, the expected test result is converted into a data type through a data conversion interface (Tsip) and then output to a log file.
Wherein the data conversion interface (Tsip) comprises a packing unit (Bsg) for performing byte order conversion and packing on data and a debugging unit (Debug) for transmitting data; the trusted computing interface is a Tspi interface provided by the TSM.
Fig. 2 is a logic diagram of data conversion performed by the data conversion interface (Tspi) of the present invention, as shown in fig. 2: in this embodiment, the process of inputting the analyzed test case data into the data conversion interface (Tsip) to perform data conversion is as follows: firstly, calling a packing unit (Bsg), converting input data into a network byte-order byte stream according to an input order, and packing, as shown in fig. 3, which is a flow chart of converting input data into a network byte-order byte stream by the packing unit (Bsg), as shown in fig. 3: adding a command serial number for each input data for controlling the output format of the later command data, adding a type identifier for each type of input data to indicate the data type and the data length, converting the host byte order into the network byte order according to the type of the data identifier and the data length, storing the converted self-order to a specified memory address according to the order of the output data, judging whether unconverted data exist, circularly executing the conversion process if the unconverted data exist until all the input data are converted into the network byte order byte stream, and finally returning the memory address for storing the byte order and the effective byte order length.
Then, data transmission is performed through the Debug unit (Debug), as shown in fig. 4, the Debug unit (Debug) outputs the converted endian according to a predetermined output format, as shown in fig. 4: according to the data label, the input data byte stream (test expected value) converted into the network byte order is printed to the log file according to the input data order, and the statistical keyword is added in the log file, the process is as follows: analyzing the command serial number added in the packaging process from the input byte sequence, searching a template corresponding to the command serial number in a command log format template, if the corresponding template is found, further judging whether the data is input data or output data, respectively printing the input data and the output data, and printing the data to a log file according to the command log format; if no corresponding template is found, the printing mode is exited, and in this embodiment, the command log format template includes the following contents:
[ Command Serial number
Command sequence number name
Input data identification
Data 1 name, data 1 length, data 1 end
Data 2 name, data 2 length, data 2 end
…
Input data end identification
Output data identification
Data 1 name, data 1 length, data 1 end
Data 2 name, data 2 length, data 2 end
…
End of output data identification
The statistical keyword refers to a fixed field convenient for statistics to identify a certain type of data, condition or result, such as [ OutPut ], [ Command ], [ Pass ], [ Failed ], and the like.
Step 104: inputting the analyzed test case data into a trusted computing interface for testing, and returning a test actual value to a log file;
fig. 5 is a flowchart of the test executed by the trusted computing interface (Tspi) according to the present invention, as shown in fig. 5: in this embodiment, the process of inputting the parsed test case data into the trusted computing interface (Tspi) for testing is as follows: calling a trusted computing interface (Tspi) to input test data to execute a test, submitting analyzed test case data (original input data of a host byte order) and transmitting the test case data to the trusted computing interface (Tspi) provided by the TSM for testing; judging the test result state returned by the trusted computing interface (Tspi), if the test result state returned by the trusted computing interface (Tspi) is successful, calling the data conversion interface (Tsip) to convert the returned test result data into a network byte sequence, outputting the test result data converted into the network byte sequence to a log file according to a preset command data output sequence, and adding an output statistical keyword in the log file; and if the test result returned by the trusted computing interface (Tspi) is failed, directly outputting the test result returned state to the log file, and adding an output statistical keyword in the log file. Wherein the OutPut statistical keywords comprise [ OutPut ], [ Command ], and the like.
Step 105: verifying the actual test value and the expected test value, and recording the verification result in the log file;
FIG. 6 is a logic diagram of the verification process, as shown in FIG. 6: in the embodiment, an expected value of a test case and a test actual value returned by a trusted computing interface (Tspi) are obtained and verified; the check result is: if the test expected value is consistent with the actual value, the test verification result is marked to Pass' in the log, and the next test case is verified; if the test expected value does not accord with the actual value, marking the test verification result as Failed in the log, printing the test expected result and the actual result, further judging the state of the test command alarm switch, and if the test command alarm switch is closed, continuing the following operation to enter the verification of the next test case; if the test command alarm switch is on, the test procedure is interrupted.
Wherein, the test actual value refers to a test actual result returned after the test input condition is executed through a trusted computing interface (Tspi).
Step 106: and analyzing and counting the test result and outputting the test statistical result.
In this embodiment, first, a log file in a test process is obtained, a log recorded in the current operation is read from the log file to a buffer, and a tested command interface is read from the buffer; then, the test result is counted according to the statistical keywords inserted in the log file, the number of the test cases and the command sending times are counted through the statistical keywords, the test case passing rate is calculated, a test report is output according to the statistical result, and the failed test cases are collected.
The invention also discloses a test system for testing the trusted computing password support platform, which comprises a test case configuration module, a test case analysis module, a test execution module, a test data verification module and a test log analysis module.
Fig. 7 is a logical structure diagram of the test system of the present invention, and the following describes the test system according to the embodiment of the present invention in detail with reference to fig. 7:
a test case configuration module 701, configured to obtain an atomic behavior and package the atomic behavior as a test case;
in this embodiment, the encapsulation process is: firstly, starting a test case configuration module and establishing a test case template; acquiring a test case and an atomic behavior which are defaulted by a test case configuration module, selecting the needed atomic behavior into a test case template, and packaging the atomic behavior into the test case; and when a plurality of test cases are needed to be used after the test is finished, packaging the test cases one by circulating the steps and establishing a test case library.
A test case analysis module 702, configured to analyze the test case according to the input parameters to obtain test case data;
in this embodiment, the parsing process is: firstly, identifying whether the input parameters have test command keywords, if so, triggering a test command alarm switch, otherwise, skipping the step and continuing the subsequent analysis; then, identifying the name of the test case according to the input parameters, if the test case exists in the test case library, running the test case, and otherwise, returning the wrong test case name; and reading the data of the identified test case name as the data input of the test case, and if the test case corresponds to a plurality of test data, circularly reading the test data and inputting the test data into the test case.
A test execution module 703, configured to convert the analyzed test case data and execute a test;
the test execution module 703 further includes: a data conversion interface (Tsip) 710 for converting input test data and a trusted computing interface (Tspi) 720 for executing test commands for testing; the data conversion interface (Tsip) 710 further includes a packing unit (Bsg) 711 that performs endian conversion and packing of data and a Debug unit (Debug) 712 that transfers data.
In this embodiment, the step of converting the analyzed test case data is to convert the analyzed test case data into a network endian by calling a data conversion interface (Tsip) 710, and output a test expected value to a log file; the execution test is to input the parsed test case data to a trusted computing interface (Tspi) 720 for testing, and return a test actual value to a log file.
The test data checking module 704 is used for checking the actual test value and the expected test value, if the actual test value and the expected test value are consistent, the checking is successful, the test is recorded in the log file that the test passes, and otherwise, the test is recorded in the log file that the test does not pass;
in the embodiment, firstly, a test expected value and an actual value returned by a trusted computing interface (Tspi) are obtained and verified; if the test expected value is consistent with the actual value, the test verification result is marked as success in the log; if the test expected value is not consistent with the actual value, the test verification result is marked as failure in the log, the state of the test command alarm switch is continuously judged, if the test command alarm switch is closed, the expected result and the actual result are printed in the log, and the subsequent operation is continued; if the test command alarm switch is on, the expected result and the actual result are printed in the log, and the test process is interrupted.
The test log analysis module 705 is used for counting the passing rate of the test cases and outputting test statistical results; firstly, acquiring a log file in a test process, counting a test result according to a statistical keyword inserted in the log file, and outputting the test statistical result.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. A test method for testing a trusted computing password support platform is characterized by comprising the following steps:
acquiring atomic behaviors and packaging the atomic behaviors into a test case;
analyzing the test case to obtain test case data;
calling a data conversion interface to convert the analyzed test case data into a network byte sequence and outputting a test expected value to a log file;
inputting the analyzed test case data into a trusted computing interface for testing, and returning a test actual value to a log file;
verifying the actual test value and the expected test value, and recording the verification result in the log file;
and analyzing and counting the test result and outputting the test statistical result.
2. The testing method of claim 1, wherein the step of obtaining atomic behaviors and packaging into test cases comprises:
establishing a test case template;
acquiring a default test case and an atomic behavior of a system;
selecting needed atomic behaviors to a test case template, and packaging the atomic behaviors into a test case;
and when a plurality of test cases are needed to be used after the test is finished, packaging the test cases one by circulating the steps and establishing a test case library.
3. The testing method of claim 1, wherein the step of parsing the test case to obtain test case data comprises:
identifying whether the input parameters have test command keywords, if so, triggering a test command alarm switch, and if not, skipping the step;
identifying the name of the test case according to the input parameters, running the test case if the test case exists in the test case library, and returning the wrong test case name if the test case exists in the test case library;
and reading the data of the identified test case name as the data input of the test case, and if the test case corresponds to a plurality of test data, circularly reading the test data and inputting the test data into the test case.
4. The method of claim 3, wherein the step of verifying the actual test value and the expected test value and recording the verification result in the log file comprises:
obtaining a test expected value and a test actual value in a log file and verifying;
if the test expected value is consistent with the actual value, the test verification result is marked as success in the log, and the test passing of the log is recorded in the log file;
if the test expected value does not accord with the actual value, the test verification result is identified as failure in the log, the test failure is recorded in the log file, and the state of the test command alarm switch is continuously judged.
5. The method of claim 4, wherein determining the state of the test command alarm switch comprises:
if the test expected value is not consistent with the actual value and the test command alarm switch is closed, printing an expected result and an actual result in the log and continuing the subsequent operation;
if the expected test value is not consistent with the actual value and the alarm switch is turned on, the expected result and the actual result are printed in the log, and the test process is interrupted.
6. The test method according to any one of claims 1 to 5, wherein the step of calling the data conversion interface to convert the parsed test case data into a network endian and outputting the test expected value to the log file comprises:
calling a data conversion interface to print a data label on the input test data according to the data type;
and printing the test expected value to a log file according to the data label and the input test data sequence, and adding a statistical keyword in the log file.
7. The testing method of claim 6, wherein the step of inputting the parsed test case data into the trusted computing interface for testing and returning the test actual value to the log file comprises:
testing by calling the test data input and analyzed by the trusted computing interface;
judging the state of the returned test result of the trusted computing interface, if the test result is successfully returned, calling the data conversion interface to perform data conversion on the returned test result, marking a data label on the data of the returned test result, printing the actual value returned to the log file according to the sequence of the data of the returned test result, and adding a statistical keyword in the log file; and if the test result is failed to be returned, directly outputting a test result return state to the log file and adding the statistical keywords.
8. The testing method of claim 7, wherein analyzing the statistical test results and outputting the test statistical results comprises:
acquiring a log file in a test process;
analyzing and counting the passing rate of the test cases according to the statistical keywords inserted in the log file;
and outputting a test statistical result.
9. A test system for testing a trusted computing password support platform, comprising: the system comprises a test case configuration module, a test case analysis module, a test execution module, a test data verification module and a test log analysis module; wherein,
the test case configuration module is used for acquiring atomic behaviors and packaging the atomic behaviors into test cases;
the test case analysis module is used for analyzing the test cases according to the input parameters to obtain test case data;
the test execution module is used for converting the analyzed test case data and executing the test;
the test data verification module is used for verifying the actual test value and the expected test value, if the actual test value and the expected test value are consistent, the verification is successful, the test passing is recorded in the log file, and otherwise, the test failing is recorded in the log file;
and the test log analysis module is used for counting the passing rate of the test cases and outputting test statistical results.
10. The test system of claim 8, wherein the test execution module comprises: the data conversion interface and the trusted computing interface; wherein,
the data conversion interface is used for converting the analyzed test case data into a network byte sequence and outputting a test expected value to a log file; the data conversion interface further comprises a packing unit for performing byte order conversion and packing on the data and a debugging unit for transmitting the data;
and the trusted computing interface is used for inputting the analyzed test case data into the trusted computing interface for testing and returning the actual test value to the log file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110092504.7A CN102736975B (en) | 2011-04-13 | 2011-04-13 | A kind of method of testing that trusted computing password support platform is tested and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110092504.7A CN102736975B (en) | 2011-04-13 | 2011-04-13 | A kind of method of testing that trusted computing password support platform is tested and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102736975A true CN102736975A (en) | 2012-10-17 |
| CN102736975B CN102736975B (en) | 2016-01-20 |
Family
ID=46992516
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110092504.7A Active CN102736975B (en) | 2011-04-13 | 2011-04-13 | A kind of method of testing that trusted computing password support platform is tested and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102736975B (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105740147A (en) * | 2016-01-29 | 2016-07-06 | 四川长虹电器股份有限公司 | Method for automatically testing interfaces of intelligent terminals |
| CN106541716A (en) * | 2015-09-17 | 2017-03-29 | 北大方正集团有限公司 | A kind of shower nozzle emulation board and printing test method for test printing control system |
| CN107948744A (en) * | 2017-12-13 | 2018-04-20 | 深圳市雷鸟信息科技有限公司 | Interface detection method, interface detection device and computer-readable recording medium |
| CN108763006A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of diagnostic method and system of backboard pressure test |
| CN109446065A (en) * | 2018-09-18 | 2019-03-08 | 深圳壹账通智能科技有限公司 | User tag test method, device, computer equipment and storage medium |
| CN109491885A (en) * | 2018-09-26 | 2019-03-19 | 深圳壹账通智能科技有限公司 | Test problem localization method, device, computer equipment and storage medium |
| CN109587351A (en) * | 2019-01-23 | 2019-04-05 | 北京三快在线科技有限公司 | A kind of call test method, device, equipment and storage medium |
| CN109872230A (en) * | 2019-01-23 | 2019-06-11 | 平安科技（深圳）有限公司 | The test method of finance data analysis system, device, medium, electronic equipment |
| CN110489471A (en) * | 2019-07-25 | 2019-11-22 | 北京文渊佳科技有限公司 | A kind of data request processing method, apparatus, storage medium and server |
| CN110727565A (en) * | 2018-07-16 | 2020-01-24 | 普天信息技术有限公司 | Network equipment platform information collection method and system |
| CN113204486A (en) * | 2021-05-20 | 2021-08-03 | 山东英信计算机技术有限公司 | TCM module function stability testing method, device and system |
| CN115086209A (en) * | 2022-05-10 | 2022-09-20 | 浙江众合科技股份有限公司 | Signal system digital intelligent test method based on edge computing platform |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2392276A (en) * | 2002-07-31 | 2004-02-25 | Hewlett Packard Development Co | A method of validating the rights of a user to participate in an interactive computer environment |
| CN101414279A (en) * | 2008-11-18 | 2009-04-22 | 武汉大学 | Test device for credible software stack |
-
2011
- 2011-04-13 CN CN201110092504.7A patent/CN102736975B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2392276A (en) * | 2002-07-31 | 2004-02-25 | Hewlett Packard Development Co | A method of validating the rights of a user to participate in an interactive computer environment |
| CN101414279A (en) * | 2008-11-18 | 2009-04-22 | 武汉大学 | Test device for credible software stack |
Non-Patent Citations (3)
| Title |
|---|
| ZHANG HUANGUO等: "Research on theory and key technology of trusted computing platform security testing and evaluation", 《SCIENCE CHINA(INFORMATION SCIENCES)》 * |
| 何凡等: "可信计算支撑软件测试方法的研究", 《武汉理工大学学报》 * |
| 张焕国等: "可信计算平台测评理论与关键技术研究", 《中国科学》 * |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106541716A (en) * | 2015-09-17 | 2017-03-29 | 北大方正集团有限公司 | A kind of shower nozzle emulation board and printing test method for test printing control system |
| CN105740147A (en) * | 2016-01-29 | 2016-07-06 | 四川长虹电器股份有限公司 | Method for automatically testing interfaces of intelligent terminals |
| CN107948744A (en) * | 2017-12-13 | 2018-04-20 | 深圳市雷鸟信息科技有限公司 | Interface detection method, interface detection device and computer-readable recording medium |
| CN108763006A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of diagnostic method and system of backboard pressure test |
| CN110727565A (en) * | 2018-07-16 | 2020-01-24 | 普天信息技术有限公司 | Network equipment platform information collection method and system |
| CN110727565B (en) * | 2018-07-16 | 2023-06-23 | 普天信息技术有限公司 | Network equipment platform information collection method and system |
| CN109446065A (en) * | 2018-09-18 | 2019-03-08 | 深圳壹账通智能科技有限公司 | User tag test method, device, computer equipment and storage medium |
| CN109491885A (en) * | 2018-09-26 | 2019-03-19 | 深圳壹账通智能科技有限公司 | Test problem localization method, device, computer equipment and storage medium |
| CN109587351A (en) * | 2019-01-23 | 2019-04-05 | 北京三快在线科技有限公司 | A kind of call test method, device, equipment and storage medium |
| CN109872230A (en) * | 2019-01-23 | 2019-06-11 | 平安科技（深圳）有限公司 | The test method of finance data analysis system, device, medium, electronic equipment |
| CN109872230B (en) * | 2019-01-23 | 2024-04-02 | 平安科技（深圳）有限公司 | Test method and device of financial data analysis system, medium and electronic equipment |
| CN110489471A (en) * | 2019-07-25 | 2019-11-22 | 北京文渊佳科技有限公司 | A kind of data request processing method, apparatus, storage medium and server |
| CN113204486A (en) * | 2021-05-20 | 2021-08-03 | 山东英信计算机技术有限公司 | TCM module function stability testing method, device and system |
| CN115086209A (en) * | 2022-05-10 | 2022-09-20 | 浙江众合科技股份有限公司 | Signal system digital intelligent test method based on edge computing platform |
| CN115086209B (en) * | 2022-05-10 | 2024-03-12 | 浙江众合科技股份有限公司 | Signal system digital intelligent test method based on edge computing platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102736975B (en) | 2016-01-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102736975B (en) | A kind of method of testing that trusted computing password support platform is tested and system | |
| CN107122297B (en) | Method and equipment for generating request message of test interface | |
| CN107122258B (en) | Method and equipment for checking state code of test interface | |
| CN109474488A (en) | Interface test method, device and computer equipment | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| EP2381367A1 (en) | Method and apparatus for the performing unit testing of software modules in software systems | |
| CN102457414A (en) | Network security automatic assessment method and system adopting same used in classified security protection assessment | |
| CN107526676B (en) | Cross-system test method and device | |
| Philipps et al. | Model-based test case generation for smart cards | |
| CN109324961B (en) | System automatic test method, device, computer equipment and storage medium | |
| CN110399304B (en) | Script testing method and system | |
| CN102123058A (en) | Test equipment and method for testing network protocol decoder | |
| CN114116496A (en) | Automatic testing method, device, equipment and medium | |
| CN117370203B (en) | Automatic test method, system, electronic equipment and storage medium | |
| CN114185808A (en) | Automatic testing method and device, electronic equipment and computer readable storage medium | |
| KR20190074072A (en) | Message based communicating method of test server and test server communicating based on message | |
| US20110138001A1 (en) | Apparatus and method for testing web service interoperability | |
| US20070245313A1 (en) | Failure tagging | |
| Wang et al. | Intelligent test oracle construction for reactive systems without explicit specifications | |
| CN112131127B (en) | Interface testing method, device and system and electronic equipment | |
| CN112860587B (en) | UI automatic test method and device | |
| CN110287700A (en) | A kind of iOS application safety analytical method and device | |
| CN117194259A (en) | Interface testing method, system, electronic equipment and storage medium | |
| CN115314413B (en) | CAN signal testing method and device | |
| CN111258562A (en) | Java code quality inspection method, device, equipment and storage medium |
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 |