CN112948236A - Breakpoint configuration method, system and device for white box test - Google Patents
Breakpoint configuration method, system and device for white box test Download PDFInfo
- Publication number
- CN112948236A CN112948236A CN202110121702.5A CN202110121702A CN112948236A CN 112948236 A CN112948236 A CN 112948236A CN 202110121702 A CN202110121702 A CN 202110121702A CN 112948236 A CN112948236 A CN 112948236A
- Authority
- CN
- China
- Prior art keywords
- transaction
- value
- signature
- password
- communication packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 83
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000004891 communication Methods 0.000 claims abstract description 84
- 238000012937 correction Methods 0.000 claims abstract description 32
- 230000008569 process Effects 0.000 claims abstract description 15
- 238000012545 processing Methods 0.000 claims abstract description 15
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 238000011161 development Methods 0.000 abstract description 4
- 230000007246 mechanism Effects 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 7
- 230000005856 abnormality Effects 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 3
- 238000012800 visualization Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000011990 functional testing Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 238000004080 punching Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a breakpoint configuration method, a system and a device for white box testing, which comprise the following steps: step 1: determining the transaction type, whether the transaction is positive or negative, a communication mode, a card information acquisition mode, a password value, a signature value and a value range of the transaction amount in the financial transaction process; step 2: listing transaction amount, card input type, communication mode, password input condition, signature input condition and processing mode of the correction point; and step 3: generating a list according to the listed information, and counting cases needing to be tested; and 4, step 4: writing a DEBUG program for the corresponding test point which cannot be realized by external manual operation to perform PC serial port instruction control or financial terminal menu key control; and 5: and sequentially configuring the values of the corresponding test points through the written DEBUG program for testing. The invention tests each point pertinently, improves the comprehensiveness and correctness of the test, and reduces the development period and the development cost.
Description
Technical Field
The invention relates to the technical field of financial payment terminals, in particular to a breakpoint configuration method, a breakpoint configuration system and a breakpoint configuration device for white box testing.
Background
In the field of financial payment terminals, the APP installed on the terminal must be reliably tested before use, and because the financial terminal APP is related to a fund account, the fund account of a customer can be damaged if unknown errors exist on the program.
General financial terminal APP tests are after programs are developed, a tester conducts functional tests according to APP function documents, and the tester does not necessarily know the complete process of an APP flow, so blind spots are always missed in the tests, for example, the blind spots are tested by directly conducting power-off on a financial terminal, and whether the blind spots are generated or not or whether the generated positions are test points needing to be tested or not can not be expected, so that a black box test mode of the tester inevitably misses some test contents, and the test coverage is narrow.
Patent document CN104331361A (application number: cn201410476175.x) discloses a testing apparatus and method for white box test coverage calculation visualization, the testing apparatus includes a source code blocking apparatus and a coverage calculation visualization presentation apparatus, and the method for testing by using the apparatus includes the following steps: a source code blocking step; and calculating the coverage rate and visually presenting. By the white box test coverage calculation visualization test device and method, detailed test coverage conditions are provided for testers, users can conveniently and quickly locate the logic error point of the source code, and the users are guided to design test cases which can reach 100% coverage.
Disclosure of Invention
In view of the defects in the prior art, the invention aims to provide a breakpoint configuration method, a system and a device for white box testing.
The breakpoint configuration method for the white box test provided by the invention comprises the following steps:
step 1: determining the transaction type, whether the transaction is positive or negative, a communication mode, a card information acquisition mode, a password value, a signature value and a value range of the transaction amount in the financial transaction process;
step 2: listing transaction amount, card input type, communication mode, password input condition, signature input condition and processing mode of correction point according to the acquired information;
and step 3: generating a list according to the listed information, and counting cases needing to be tested;
and 4, step 4: based on the counted cases needing to be tested, the corresponding test points which cannot be realized through external manual operation are subjected to PC serial port instruction control or financial terminal menu key control by compiling a DEBUG program;
and 5: and sequentially configuring the values of the corresponding test points according to the test case through the compiled DEBUG program for testing.
Preferably, 5 points are selected in listing the transaction amount: any value below a preset range, the lowest value of the preset range, any value within the preset range, the maximum value of the preset range, and any value above the preset range;
the card input types comprise a magnetic stripe card, a contact IC card and a non-contact card;
the communication mode comprises GPRS and WIFI;
the password input condition comprises the following steps: inputting no password, inputting a correct password, inputting an incorrect password, wherein the length of the input password is less than the minimum value and the length of the input password is greater than the maximum value;
the signature input case includes: no signature, signature over signature range box, correct signature, full screen signature and minimum point signature;
the processing mode of the correction points comprises the generation of the correction points and the deletion of the correction points.
Preferably, whether the positive offset is generated is checked, and the checking scene comprises: when the transaction communication packet is packaged, the transaction communication packet is connected with the background successfully, the transaction communication packet is connected with the background before data is sent, the transaction communication packet is connected with the background after the data is sent, and the transaction communication packet is connected with the background before the data is received;
after checking that the transaction is positive, informing a background to inquire whether the transaction exists, and if so, performing cancellation; if the transaction does not exist, the query is ignored.
Preferably, the checking whether the erasure is positive includes: after the transaction communication packet receives the data, after the unpacking of the transaction communication packet after receiving the data fails, after the unpacking of the transaction communication packet after receiving the data is correct but the value of the return domain is not zero, when the value of the unpacking correct return domain of the transaction communication packet after receiving the data is zero and before the transaction information is stored after the transaction is finished;
if the conflict is not deleted, the background is informed to delete, and the financial transaction is continued after the conflict is deleted.
The breakpoint configuration system for the white box test provided by the invention comprises:
module M1: determining the transaction type, whether the transaction is positive or negative, a communication mode, a card information acquisition mode, a password value, a signature value and a value range of the transaction amount in the financial transaction process;
module M2: listing transaction amount, card input type, communication mode, password input condition, signature input condition and processing mode of correction point according to the acquired information;
module M3: generating a list according to the listed information, and counting cases needing to be tested;
module M4: based on the counted cases needing to be tested, the corresponding test points which cannot be realized through external manual operation are subjected to PC serial port instruction control or financial terminal menu key control by compiling a DEBUG program;
module M5: and sequentially configuring the values of the corresponding test points according to the test case through the compiled DEBUG program for testing.
Preferably, 5 points are selected in listing the transaction amount: any value below a preset range, the lowest value of the preset range, any value within the preset range, the maximum value of the preset range, and any value above the preset range;
the card input types comprise a magnetic stripe card, a contact IC card and a non-contact card;
the communication mode comprises GPRS and WIFI;
the password input condition comprises the following steps: inputting no password, inputting a correct password, inputting an incorrect password, wherein the length of the input password is less than the minimum value and the length of the input password is greater than the maximum value;
the signature input case includes: no signature, signature over signature range box, correct signature, full screen signature and minimum point signature;
the processing mode of the correction points comprises the generation of the correction points and the deletion of the correction points.
Preferably, whether the positive offset is generated is checked, and the checking scene comprises: when the transaction communication packet is packaged, the transaction communication packet is connected with the background successfully, the transaction communication packet is connected with the background before data is sent, the transaction communication packet is connected with the background after the data is sent, and the transaction communication packet is connected with the background before the data is received;
after checking that the transaction is positive, informing a background to inquire whether the transaction exists, and if so, performing cancellation; if the transaction does not exist, the query is ignored.
Preferably, the checking whether the erasure is positive includes: after the transaction communication packet receives the data, after the unpacking of the transaction communication packet after receiving the data fails, after the unpacking of the transaction communication packet after receiving the data is correct but the value of the return domain is not zero, when the value of the unpacking correct return domain of the transaction communication packet after receiving the data is zero and before the transaction information is stored after the transaction is finished;
if the conflict is not deleted, the background is informed to delete, and the financial transaction is continued after the conflict is deleted.
According to the breakpoint configuration device for white box testing provided by the invention, normal work or failure work in power failure of input end equipment is realized through the breakpoint configuration device, and the input end equipment comprises: the card information acquisition system comprises a card information acquisition input end, a transaction amount input end, a password input end, a signature input end and communication equipment.
Preferably, the breakpoint configuration device and the DEBUG program are used in combination to test all predictable test points, and a requirement error or a logic error in program writing is eliminated.
Compared with the prior art, the invention has the following beneficial effects:
(1) the invention avoids the tester from blindly simulating various abnormalities by switching on and off during testing, but testing various points in a targeted manner, saves time, energy and manpower, improves the comprehensiveness and correctness of the test, and reduces the development period and the development cost;
(2) the invention can realize automatic asynchronous correction by a correction checking mode, effectively improves the correctness of a transaction result and reduces the workload of manual intervention correction.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments with reference to the following drawings:
FIG. 1 is a flow chart of the method of the present invention;
FIG. 2 is a flow chart illustrating a financial consumption testing transaction point according to an embodiment of the present invention;
FIG. 3 is a flow chart of a financial settlement test forward point according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart of a financial hedge test hedge point according to an embodiment of the present invention;
FIG. 5 is a flow chart illustrating exceptions to the financial consumption hardware according to a second embodiment of the present invention;
FIG. 6 is a flow chart illustrating a sudden power off during financial consumption according to a third embodiment of the present invention.
Detailed Description
The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the invention, but are not intended to limit the invention in any way. It should be noted that it would be obvious to those skilled in the art that various changes and modifications can be made without departing from the spirit of the invention. All falling within the scope of the present invention.
Example 1:
referring to fig. 1, the breakpoint configuration method for white box testing according to the present invention includes:
step 1: determining the transaction type, whether the transaction is positive or negative, a communication mode, a card information acquisition mode, a password value, a signature value and a value range of the transaction amount in the financial transaction process;
step 2: listing transaction amount, card input type, communication mode, password input condition, signature input condition and value taking mode of the correction point according to the acquired information;
and step 3: generating a list according to the listed information, and counting cases needing to be tested;
and 4, step 4: based on the counted cases needing to be tested, the corresponding test points which cannot be realized through external manual operation are subjected to PC serial port instruction control or financial terminal menu key control by compiling a DEBUG program;
and 5: and sequentially configuring the values of the corresponding test points according to the test case through the compiled DEBUG program for testing.
The invention provides a breakpoint configuration method for testing correction, which is applied to financial consumption and relates to whether a customer fund account is short or not, and comprises the following steps:
determining whether conflict is generated when the transaction communication packet is packaged;
determining whether the transaction communication packet generates conflict before the transaction communication packet is successfully connected with the background;
determining whether the transaction communication packet generates conflict after being successfully connected with the background;
determining whether the transaction communication packet generates conflict before sending data;
determining whether the transaction communication packet generates conflict after sending data;
determining whether the transaction communication packet generates conflict before receiving data;
determining whether the transaction communication packet is immediately deleted and corrected after receiving the data;
determining whether the transaction communication packet is immediately deleted and corrected after the unpacking fails after receiving the data;
determining whether the transaction communication packet is immediately deleted and corrected after being unpacked correctly after receiving data;
determining whether the transaction communication packet is correctly unpacked but returns to zero or not when the value of the domain is zero after receiving data or not;
determining whether the transaction communication packet is immediately deleted and corrected when the value of the unpacking correct return field is zero after receiving the data;
and determining whether to immediately delete the transaction before storing the transaction information after the transaction is finished.
The invention provides a device for testing the abnormality of hardware equipment, which is applied to whether a timeout mechanism exists during financial consumption or not, and comprises the following steps:
determining whether the sum can be normally input or not and whether an overtime exit mechanism exists or not;
determining whether the magnetic stripe card can read the card normally or not and whether an overtime exit mechanism exists or not;
determining whether the contact IC card can read the card normally or not and whether an overtime exit mechanism exists or not;
determining whether the non-connected card can read the card normally or not and whether an overtime exit mechanism exists or not;
determining whether the password can be normally input or not and whether an overtime exit mechanism exists or not;
determining whether the signature can be normally input or not and whether an overtime exit mechanism exists or not;
determining whether GPRS communication is normal or not and whether an overtime exit mechanism exists or not;
determining whether WIFI communication is normal or not and whether an overtime exit mechanism exists or not;
and determining whether the file storage system is normal or not and whether a processing mechanism exists in data storage or not.
The invention provides a breakpoint configuration method and a breakpoint configuration device which are used simultaneously, and simulate unknown errors of sudden power failure during financial payment, wherein the method comprises the following steps: and determining whether the abnormal processing of sudden power failure is correct or not in the process of starting to send data to the transaction storage success after the transaction communication packet is successfully connected with the background.
Example 2:
financial transactions are divided into two categories, one category of transactions can generate positive conflict, and the other category of transactions can not generate positive conflict. The transaction is also a transaction type, but belongs to a notification type transaction, and the function of the transaction is to tell the background whether a certain transaction request sent last just now is inquired, and if so, the transaction request is cancelled; if no such transaction exists, the query is ignored. Financial payments involve the general consumption, withdrawal of consumption, pre-authorization, etc. of financial transactions that must be supported. The information at the two sides of the background and the financial terminal is not equal due to the communication reason or the data packet processing reason, and if the transaction is not timely flushed, the short payment phenomenon of the fund account of the customer can occur. And the check-in, settlement and balance inquiry type transactions do not involve fund exchange, so that the transaction types can not be used for correction. Therefore, the positive impact generation is not considered in the non-deductive transaction.
The positive impact is divided into two cases, with or without. In addition, in the third case, after the forward-backward movement is generated, a forward-backward movement packet needs to be sent, and forward-backward movement transaction is query type transaction, so the forward-backward movement packet itself is not forward-backward movement, but if the forward-backward movement packet cannot receive normal return of the background due to communication reasons or abnormality of the forward-backward movement packet itself, the financial terminal cannot continue transaction if the forward-backward movement packet is not processed, because the forward-backward movement packet must be sent to the background for processing before the normal transaction packet is sent. Therefore, the Union of the.
In this embodiment, the cases to be tested include:
1. calling pack _8583 to set a breakpoint;
2. setting a breakpoint before calling tcp _ connect;
3. setting a breakpoint after calling tcp _ connect;
4. setting a breakpoint before calling tcp _ send;
5. setting a breakpoint after calling tcp _ send;
6. setting a breakpoint before calling tcp _ recv;
7. setting a breakpoint after calling the tecp _ recv;
8. setting a breakpoint at the failure position of invoking unpack _ 8583;
9. calling the successful position of unpack _8583 to set a breakpoint;
10. a bit39 field in the 8583 packet returns a position other than 0 to set a breakpoint;
11. a breakpoint is set at the position where the bit39 field in the 8583 packet returns to 0;
12. a breakpoint is set before the call Trans save.
The flow of the embodiment refers to consumption transaction, and the consumption transaction is that the positive-going is necessary, so the embodiment refers to whether the positive-going flag bit is normally set and deleted in time.
In this embodiment, the current device does not have a contact IC card, which is swiped by the testing device, the input is the 6-digit password 123456, the transaction amount is 0.01 yuan, the communication device is normal, and all operations are correctly completed before the transaction communication packet is packaged.
As shown in fig. 2, the flow of this embodiment is as follows:
step S1, selecting the consumption menu, inputting the transaction amount of 0.01 yuan, inserting the contact IC card to read the card number, inputting the transaction password 123456 according to the prompt, signing, checking whether the current transaction is positive or negative, and the current terminal is not positive.
And step S2, making 8583 transaction communication packets, wherein when making 8583 transaction packets, the program will make a correction packet of the transaction at the same time, but will not set the correction flag bit. Therefore, a breakpoint is set here to see that there is no error-free positive flag bit in the program.
Step S3, enter the communication function to start network connection background, where a breakpoint is set, and see that there is no error flag bit before the program is connected to the background.
Step S4, after the background connection is successful, a breakpoint is set here, and the program is checked that there is no erroneous positive flag after the background connection.
In step S5, before data transmission, a breakpoint is set here to see that the program has no error un-reset flag before data transmission.
Step S6, setting a breakpoint at three places after data transmission, before data reception, and after receipt reception, and checking whether the current positive flag bit of the program is still in place.
And S7, unpacking the 8583 packet, respectively setting break points at positions where unpacking succeeds and fails, analyzing whether a bit39 field in the 8583 packet is 0 or not after unpacking succeeds, and respectively setting break points at positions 0 and non-0.
And step S8, the transaction is successfully saved, and a breakpoint is set before the transaction is saved.
The correct alignment position and the breakpoint of deletion in this embodiment are the alignment flag bit in the tcp _ send preamble, and because the terminal cannot predict whether the data sent by itself is received in the background, the alignment position must be set, and then the alignment flag bit is deleted when the 8583 packet 39 field returns to the background and is not 0, whereas if the field 39 is 0, the alignment flag bit must be deleted after the transaction data is successfully stored. Because the 39 field returns to non-0, which represents that the background does not allow the consumption to be successful, it is not necessary to send a correction to the background to delete the transaction which does not exist, and when the 39 field returns to 0, because the problem that the account is counted by the terminal is involved, the correction must be deleted only after the transaction is successfully saved, because if power failure occurs or the transaction data cannot be written into the file system in the process, the correction must be initiated to notify the background to delete the transaction which was just successful when the transaction is unsuccessful.
Example 3:
the flow of the embodiment refers to the settlement transaction, which is not positive, so that the positive cannot be generated in the embodiment.
As shown in fig. 3, in this embodiment, the current device does not have any conflict, and all operations are completed correctly before the settlement communication packet is packaged, and the process is as follows:
and step S11, selecting a settlement menu, checking whether the conflict currently exists, and not checking whether the conflict currently exists in the terminal.
And step S12, making 8583 transaction communication packets, wherein when making 8583 settlement packets, the program does not have a correction packet or a correction position concept. Therefore, a breakpoint is set here to see that there is no error-free positive flag bit in the program.
Step S13, enter the communication function to start network connection background, where a breakpoint is set, and see that there is no error flag bit before the program is connected to the background.
Step S14, after the background connection is successful, a breakpoint is set here, and the program is checked that there is no erroneous positive flag after the background connection.
In step S15, before data transmission, a breakpoint is set here to see that the program has no error un-reset flag before data transmission.
Step S16, setting a breakpoint at three places after data transmission, before data reception, and after receipt reception, and checking whether the current positive flag bit of the program is still in place.
And S17, unpacking the 8583 packet, respectively setting break points at positions where unpacking succeeds and fails, analyzing whether a bit39 field in the 8583 packet is 0 or not after unpacking succeeds, and respectively setting break points at positions 0 and non-0.
And step S18, clearing all transaction records in the terminal and statistical information after settlement is successful.
In the embodiment, because the transaction is a non-deduction type transaction, the transaction is not positively carried out in the whole settlement process.
Example 4:
the flow of the embodiment refers to the settlement transaction, which is not positive, so that the positive cannot be generated in the embodiment.
As shown in fig. 4, in this embodiment, the current device must have a positive conflict, and the flow is as follows:
step S21, select an online transaction menu, such as the selection of settlement at the moment, check whether there is any conflict currently, and the existence of conflict currently exists in the terminal.
The forward transaction refers to the forward transaction which is preferably judged whether the terminal has a forward flag bit or not, and if so, must be initiated before any online transaction is carried out (except for the sign-in transaction).
In step S22, 8583 bursts orthogonal easy communication packets are sent.
And step S23, entering a communication function to start network connection to the background, and sending data after success.
Step S24, a breakpoint is set at the data receiving location, and the breakpoint is always returned as background no data.
And step S25, checking the positive flag bit, continuing to settle if the positive flag bit does not exist, checking whether the current positive flag bit is circulated to the 3 rd time or not if the positive flag bit is present, returning to the step S22 if the positive flag bit is not present, and directly deleting the current positive flag bit if the positive flag bit is present for the 3 rd time.
The embodiment is directed at the processing flow of the forward packet, and mainly means that the forward packet to be tested needs to be deleted in time when the background has no response for 3 times, because the test point is difficult to be made by manual simulation of a tester, the test point can be easily manufactured by the method.
Example 5:
the financial terminal always encounters the problem that certain hardware is damaged in the using process, whether the terminal can work normally or some strange abnormal deduction operations are generated under the damaged condition, and a tester cannot simulate the condition of hardware damage during testing, so that the test cases are perfectly solved due to the existence of the device for testing the abnormality of the hardware equipment.
The consumption transaction is explained in this embodiment, because the influence of the hardware malfunction on the program flow is verified, the initial state of this embodiment does not exist.
As shown in fig. 5, in this embodiment, a 6-digit password 123456 is input to a contact IC card swiped by a device under test, and the transaction amount is 0.01 yuan, and the flow is as follows:
step S31, selecting the consumption menu, inputting the transaction amount of 0.01, where the device controls the input keyboard to fail to input the amount, and then determining whether the transaction is normally exited overtime or has other abnormality.
Step S32, a contact IC card is inserted, where the device controls the IC card reader to fail to read the card, and see whether normal timeout exits or other anomalies exist.
Step S33, enter password 123456, where the device controls the password keypad to fail to enter, see if it normally exits overtime or has other exceptions.
And step S34, signing, wherein the device controls the signature screen to be inoperable to see whether normal overtime exit or other abnormity exists.
Step S35, communication, where the apparatus controls the communication device to be inoperable, and see whether the normal timeout exits or there are other exceptions, and whether the reset position is normally set.
In step S36, the transaction is saved, where the device controls that the FLASH cannot be written to see if the transaction is saved and the correction bit is deleted.
The embodiment is directed to a processing flow of a hardware exception, step S31 should be exited after 60 seconds of input amount timeout, step S32 should be exited after 30 seconds of IC card read timeout, step S33 should be exited after 60 seconds of waiting input timeout, step S34 is signed and enforced, step S35 should be exited when 60 seconds of connection background is unsuccessful, and timeout exits (which is positive at this time) after no response is received for 60 seconds, step S36 judges whether a file is written successfully when a transaction is saved, and if the transaction is not successful, the transaction is flushed, but the default is that the writing is successful.
Example 6:
the financial terminal always encounters the condition of sudden power failure in the using process, the uncertainty can not predict which step the program is running at all, and for financial payment, as long as the positive-going flag bit is well processed, no matter which step the program is in during sudden power failure, the account is not worried about short payment.
The embodiment simulates various sudden power failure conditions by combining the breakpoints and the devices, and covers all test points as much as possible.
In the present embodiment, a consumption transaction is described, because the influence of a sudden power failure on the program flow is verified, the initial state of the present embodiment does not exist.
As shown in fig. 6, in this embodiment, a contact IC card swiped by a device under test inputs a 6-digit password 123456, and the transaction amount is 0.01 yuan, and the flow is as follows:
step S41, selecting the consumption menu, inputting the transaction amount of 0.01 yuan, inserting the contact IC card to read the card number, inputting the transaction password 123456 according to the prompt, signing, checking whether the current transaction is positive or negative, and the current terminal is not positive. Because these operations do not interact with the background, there is no need to test for power outage anomalies in all cases, as there is no concept of account deduction.
And step S42, punching 8583 consumption communication packets, entering a communication function to start network connection to the background, sending data after success, and waiting for background data to return. After the data is sent, the breakpoint begins to be added, and the matched device is powered off. 8583 packets are processed after transmission and after reception, respectively.
Step S43, when the transaction is successful, the transaction is suddenly powered off when the transaction is saved, and it is necessary to add breakpoints at multiple places in the process of saving data to determine what storage sequence is good so as not to cause data inconsistency between the terminal and the background.
The functional test items and results are given in the following table:
in this embodiment, if no breakpoint is added, the tester can determine by eyes, and cannot accurately locate which step the program goes to, and which step the data is stored. The maximum requirement of the financial terminal is that account unevenness can not occur, so all the transaction is sent out to the process of setting the transaction success data storage and correction position. The invention perfectly solves the defect of black box test in the test, can accurately test in an orderly manner, and leads the predictable abnormity to be tested in a covering manner. The breakpoint control method can be configured through keys and can also be controlled through a PC serial port.
Those skilled in the art will appreciate that, in addition to implementing the systems, apparatus, and various modules thereof provided by the present invention in purely computer readable program code, the same procedures can be implemented entirely by logically programming method steps such that the systems, apparatus, and various modules thereof are provided in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Therefore, the system, the device and the modules thereof provided by the present invention can be considered as a hardware component, and the modules included in the system, the device and the modules thereof for implementing various programs can also be considered as structures in the hardware component; modules for performing various functions may also be considered to be both software programs for performing the methods and structures within hardware components.
The foregoing description of specific embodiments of the present invention has been presented. It is to be understood that the present invention is not limited to the specific embodiments described above, and that various changes or modifications may be made by one skilled in the art within the scope of the appended claims without departing from the spirit of the invention. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.
Claims (10)
1. A breakpoint configuration method for white-box testing, comprising:
step 1: determining the transaction type, whether the transaction is positive or negative, a communication mode, a card information acquisition mode, a password value, a signature value and a value range of the transaction amount in the financial transaction process;
step 2: listing transaction amount, card input type, communication mode, password input condition, signature input condition and processing mode of correction point according to the acquired information;
and step 3: generating a list according to the listed information, and counting cases needing to be tested;
and 4, step 4: based on the counted cases needing to be tested, the corresponding test points which cannot be realized through external manual operation are subjected to PC serial port instruction control or financial terminal menu key control by compiling a DEBUG program;
and 5: and sequentially configuring the values of the corresponding test points according to the test case through the compiled DEBUG program for testing.
2. A breakpoint configuration method for a white-box test according to claim 1, wherein 5 points are selected in listing a transaction amount: any value below a preset range, the lowest value of the preset range, any value within the preset range, the maximum value of the preset range, and any value above the preset range;
the card input types comprise a magnetic stripe card, a contact IC card and a non-contact card;
the communication mode comprises GPRS and WIFI;
the password input condition comprises the following steps: inputting no password, inputting a correct password, inputting an incorrect password, wherein the length of the input password is less than the minimum value and the length of the input password is greater than the maximum value;
the signature input case includes: no signature, signature over signature range box, correct signature, full screen signature and minimum point signature;
the processing mode of the correction points comprises the generation of the correction points and the deletion of the correction points.
3. A breakpoint configuration method for white-box testing according to claim 1, wherein checking whether a positive bump is generated, the scenario of checking including: when the transaction communication packet is packaged, the transaction communication packet is connected with the background successfully, the transaction communication packet is connected with the background before data is sent, the transaction communication packet is connected with the background after the data is sent, and the transaction communication packet is connected with the background before the data is received;
after checking that the transaction is positive, informing a background to inquire whether the transaction exists, and if so, performing cancellation; if the transaction does not exist, the query is ignored.
4. The breakpoint configuration method for white-box testing according to claim 1, wherein checking whether to delete a positive erasure, the checking of the scenario includes: after the transaction communication packet receives the data, after the unpacking of the transaction communication packet after receiving the data fails, after the unpacking of the transaction communication packet after receiving the data is correct but the value of the return domain is not zero, when the value of the unpacking correct return domain of the transaction communication packet after receiving the data is zero and before the transaction information is stored after the transaction is finished;
if the conflict is not deleted, the background is informed to delete, and the financial transaction is continued after the conflict is deleted.
5. A breakpoint configuration system for white-box testing, comprising:
module M1: determining the transaction type, whether the transaction is positive or negative, a communication mode, a card information acquisition mode, a password value, a signature value and a value range of the transaction amount in the financial transaction process;
module M2: listing transaction amount, card input type, communication mode, password input condition, signature input condition and processing mode of correction point according to the acquired information;
module M3: generating a list according to the listed information, and counting cases needing to be tested;
module M4: based on the counted cases needing to be tested, the corresponding test points which cannot be realized through external manual operation are subjected to PC serial port instruction control or financial terminal menu key control by compiling a DEBUG program;
module M5: and sequentially configuring the values of the corresponding test points according to the test case through the compiled DEBUG program for testing.
6. A breakpoint configuration system for white-box testing according to claim 5, wherein 5 points are selected in listing the transaction amount: any value below a preset range, the lowest value of the preset range, any value within the preset range, the maximum value of the preset range, and any value above the preset range;
the card input types comprise a magnetic stripe card, a contact IC card and a non-contact card;
the communication mode comprises GPRS and WIFI;
the password input condition comprises the following steps: inputting no password, inputting a correct password, inputting an incorrect password, wherein the length of the input password is less than the minimum value and the length of the input password is greater than the maximum value;
the signature input case includes: no signature, signature over signature range box, correct signature, full screen signature and minimum point signature;
the processing mode of the correction points comprises the generation of the correction points and the deletion of the correction points.
7. A breakpoint configuration system for white-box testing according to claim 5, wherein checking whether a positive bump is generated, the scenario of the checking comprising: when the transaction communication packet is packaged, the transaction communication packet is connected with the background successfully, the transaction communication packet is connected with the background before data is sent, the transaction communication packet is connected with the background after the data is sent, and the transaction communication packet is connected with the background before the data is received;
after checking that the transaction is positive, informing a background to inquire whether the transaction exists, and if so, performing cancellation; if the transaction does not exist, the query is ignored.
8. A breakpoint configuration system for white-box testing according to claim 5, wherein checking whether a deletion is positive comprises: after the transaction communication packet receives the data, after the unpacking of the transaction communication packet after receiving the data fails, after the unpacking of the transaction communication packet after receiving the data is correct but the value of the return domain is not zero, when the value of the unpacking correct return domain of the transaction communication packet after receiving the data is zero and before the transaction information is stored after the transaction is finished;
if the conflict is not deleted, the background is informed to delete, and the financial transaction is continued after the conflict is deleted.
9. A breakpoint configuration device for white box testing, wherein the breakpoint configuration system for white box testing according to any one of claims 5 to 8 is used to implement normal operation or no operation after power failure of an input device through the breakpoint configuration device, and the input device includes: the card information acquisition system comprises a card information acquisition input end, a transaction amount input end, a password input end, a signature input end and communication equipment.
10. The breakpoint configuration device for the white-box test according to claim 9, wherein all predictable test points are tested by using the breakpoint configuration device and the DEBUG program in combination, and a requirement error or a logic error of program writing is eliminated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110121702.5A CN112948236A (en) | 2021-01-28 | 2021-01-28 | Breakpoint configuration method, system and device for white box test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110121702.5A CN112948236A (en) | 2021-01-28 | 2021-01-28 | Breakpoint configuration method, system and device for white box test |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112948236A true CN112948236A (en) | 2021-06-11 |
Family
ID=76239033
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110121702.5A Pending CN112948236A (en) | 2021-01-28 | 2021-01-28 | Breakpoint configuration method, system and device for white box test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112948236A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113822762A (en) * | 2021-09-29 | 2021-12-21 | 上海通联金融服务有限公司 | Method for triggering failure transaction short message in financial transaction authorization process |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050114736A1 (en) * | 2003-11-06 | 2005-05-26 | First Data Corporation | Methods and systems for testing software development |
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN102122265A (en) * | 2011-03-03 | 2011-07-13 | 中国工商银行股份有限公司 | System and method for verifying computer software test results |
| US20130227530A1 (en) * | 2012-02-27 | 2013-08-29 | Yokogawa Electric Corporation | Method and apparatus for debugging a program of a business process |
| CN111221739A (en) * | 2020-01-10 | 2020-06-02 | 中国建设银行股份有限公司 | Service testing method, device and system |
| CN111427790A (en) * | 2020-03-26 | 2020-07-17 | 中国建设银行股份有限公司 | Test method, test device, terminal equipment and storage medium |
-
2021
- 2021-01-28 CN CN202110121702.5A patent/CN112948236A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050114736A1 (en) * | 2003-11-06 | 2005-05-26 | First Data Corporation | Methods and systems for testing software development |
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN102122265A (en) * | 2011-03-03 | 2011-07-13 | 中国工商银行股份有限公司 | System and method for verifying computer software test results |
| US20130227530A1 (en) * | 2012-02-27 | 2013-08-29 | Yokogawa Electric Corporation | Method and apparatus for debugging a program of a business process |
| CN111221739A (en) * | 2020-01-10 | 2020-06-02 | 中国建设银行股份有限公司 | Service testing method, device and system |
| CN111427790A (en) * | 2020-03-26 | 2020-07-17 | 中国建设银行股份有限公司 | Test method, test device, terminal equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113822762A (en) * | 2021-09-29 | 2021-12-21 | 上海通联金融服务有限公司 | Method for triggering failure transaction short message in financial transaction authorization process |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Marick | When should a test be automated | |
| KR102537875B1 (en) | Method and apparatus for dinamically injecting fault for vehicle ecu software test | |
| WO2000079421A2 (en) | Property coverage in formal verification | |
| CN105573911A (en) | Application popup window processing method and apparatus | |
| CN107861832A (en) | Data verification method, device and readable storage medium storing program for executing | |
| CN112199277A (en) | Browser-based defect reproduction method, device, equipment and storage medium | |
| CN112948236A (en) | Breakpoint configuration method, system and device for white box test | |
| CN110362313A (en) | A kind of form validation method, client and server | |
| CN113094251B (en) | Method and device for testing embedded system, computer equipment and storage medium | |
| CN106201787A (en) | Terminal control method and device | |
| CN111639028A (en) | Account checking rule script test method, device, engine and storage medium | |
| CN114578210B (en) | Mainboard testing method, device, equipment and storage medium | |
| CN115840707A (en) | Flash test method, device and medium | |
| CN111176975B (en) | Test method, device, equipment and computer readable storage medium | |
| CN114879647A (en) | ECU fault code test system, electronic controller and car | |
| CN112182586B (en) | MCU read-write protection test method, device and system | |
| CN112463633B (en) | Method, device, equipment and medium for checking address decoding of on-chip memory | |
| US7546589B2 (en) | Semi-automated desk checking system and method | |
| US20020026301A1 (en) | Automatic evaluation method, automatic evaluation system, and storage medium storing automatic evaluation program | |
| CN113360402A (en) | Test method, electronic device, chip and storage medium | |
| CN112749093A (en) | Test case management method, device, equipment and storage medium | |
| KR101251792B1 (en) | Embedded Software Unit Test Automation Tool and Method Using Debugger | |
| CN112965868B (en) | Automatic testing method and device for game controller and readable medium | |
| Ambrosio et al. | A methodology for designing fault injection experiments as an addition to communication systems conformance testing | |
| KR102307997B1 (en) | Method of automating a test of PLC program and PLC server program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |