WO2019100655A1 - 发票领用异常的构造方法、装置、计算机设备及存储介质 - Google Patents

发票领用异常的构造方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2019100655A1
WO2019100655A1 PCT/CN2018/084043 CN2018084043W WO2019100655A1 WO 2019100655 A1 WO2019100655 A1 WO 2019100655A1 CN 2018084043 W CN2018084043 W CN 2018084043W WO 2019100655 A1 WO2019100655 A1 WO 2019100655A1
Authority
WO
WIPO (PCT)
Prior art keywords
invoice
information
retrieval
code
terminal
Prior art date
Application number
PCT/CN2018/084043
Other languages
English (en)
French (fr)
Inventor
张二雷
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019100655A1 publication Critical patent/WO2019100655A1/zh

Links

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

Definitions

  • the present application relates to the field of software testing technologies, and in particular, to a method, a device, a computer device and a storage medium for constructing an abnormality of an invoice.
  • the application provides a construction method, a device, a computer device and a storage medium for invoice abnormality, and aims to construct an invoice abnormality to facilitate testing of the invoice management system.
  • the present application provides a method for constructing an invoice retrieval exception, which includes:
  • Executing a preset breakpoint code generates an invoice for the exception data to complete the construction of the invoice retrieval exception.
  • the present application provides an apparatus for constructing an abnormality in an invoice, which includes:
  • An information obtaining unit configured to acquire invoice receiving information sent by the first terminal
  • Generating a sending unit configured to generate invoice distribution information according to the invoice retrieval information, and send the invoice distribution information to the second terminal;
  • An information receiving unit configured to receive confirmation information fed back by the second terminal, where the confirmation information is information generated by the second terminal confirming the invoice distribution information;
  • the execution generating unit is configured to execute the preset breakpoint code to generate the invoice retrieval abnormal data to complete the construction of the invoice retrieval abnormality.
  • the present application further provides a computer device including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor implementing the program
  • a computer device including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor implementing the program
  • the present application also provides a storage medium, wherein the storage medium stores a computer program, the computer program comprising program instructions, the program instructions, when executed by a processor, causing the processor to execute the application
  • the invoice described in any of the provided invoices is subject to an abnormal construction method.
  • the embodiment of the present application obtains the invoice retrieval information sent by the first terminal, generates invoice distribution information according to the invoice retrieval information, and sends the invoice distribution information to the second terminal, and receives the confirmation of the second terminal feedback.
  • Information wherein the confirmation information is information generated by the second terminal confirming the invoice distribution information; invoking a tax control management system to perform invoice distribution according to the confirmation information; and executing a preset breakpoint code to generate an invoice
  • the exception data is retrieved to complete the construction of the invoice retrieval exception.
  • FIG. 1 is a schematic diagram of an application scenario of an invoice management system according to an embodiment of the present application.
  • FIG. 2 is a schematic flow chart of a method for constructing an invoice exception according to an embodiment of the present application
  • FIG. 3 is a schematic flow chart of a method for constructing an invoice retrieval exception according to another embodiment of the present application.
  • FIG. 4 is a schematic block diagram of an apparatus for constructing an abnormality of an invoice according to an embodiment of the present application
  • FIG. 5 is a schematic block diagram of an apparatus for constructing an abnormality of an invoice according to another embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a computer device according to an embodiment of the present application.
  • the embodiment of the present application provides a method, a device, a computer device and a storage medium for constructing an invoice exception.
  • the invoice adopts an abnormal construction method for testing the invoice management system, and the invoice management system is used for the company's invoice management, and the invoice management system may also be referred to as a VAT management system.
  • the application scenario composition of the invoice management system is first introduced.
  • the application scenario of the invoice management system includes a first terminal, a second terminal, and a server.
  • the first terminal and the second terminal may be electronic devices such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, and a wearable device; the server may be an independent server or a server composed of multiple servers. Cluster.
  • the server is configured to execute any of the invoice-using exception construction methods provided by the present application to construct an invoice-collecting anomaly to facilitate testing of the invoice management system.
  • FIG. 2 is a schematic flowchart of a method for constructing an invoice retrieval exception according to an embodiment of the present application. As shown in FIG. 2, the construction method of the invoice retrieval abnormality includes steps S101 to S109.
  • the server obtains the invoice retrieval information sent by the first terminal, and the invoice retrieval information includes the taxation subject, the receiving institution, the recipient information, the initiation time, the application description, the invoicing terminal, and the invoice information.
  • the invoice information includes the invoice type and the number of applications, and the recipient information includes the name of the recipient and the contact information of the recipient.
  • the invoice retrieval information may be used by the user (ie, the recipient) to fill in the information required for the invoice by the client corresponding to the invoice management system installed in the first terminal, and the user fills in the information and After clicking the confirmation, the first terminal sends the invoice retrieval information to the server.
  • the preset invoice retrieval information may be a pre-set invoice retrieval information by using a preset invoice to receive the information.
  • obtaining the invoice retrieving information sent by the first terminal includes: acquiring the preset invoice retrieving information sent by the first terminal as the invoice retrieving information. Therefore, the process of filling in the user is omitted, thereby speeding up the testing efficiency of the software.
  • S102 Generate invoice distribution information according to the invoice retrieval information, and send the invoice distribution information to the second terminal.
  • the generating the invoice distribution information according to the invoice retrieval information specifically converting the acquired invoice retrieval information into corresponding invoice distribution information.
  • the invoice distribution information includes the originating institution, the initiator information, the originating time, the taxing entity, the core board, the invoicing terminal, the invoice information (invoice type, the number of applications and the number of copies), and the invoice details, specifically the invoice details including the invoice Code, invoice start number, and invoice stop number.
  • the information is generated according to the invoice-receiving information, that is, the invoice distribution information and the invoice-receiving information correspond to each other, for example, the taxpayer and the recipient information respectively correspond to the originating institution and the sponsor information.
  • the invoice distribution information is sent to the second terminal, and the second terminal presents the corresponding invoice management personnel to view the invoice distribution information.
  • S103 Receive confirmation information fed back by the second terminal, where the confirmation information is information generated by the second terminal confirming the invoice distribution information.
  • the invoice manager of the second terminal after checking the invoice distribution information and confirming that there is no problem, may click to confirm the issuance to send the confirmation information to the server through the second terminal, that is, the server receives
  • the confirmation information about the invoice distribution information fed back to the second terminal is performed, and step S104 is performed based on the confirmation information.
  • the tax control management system is invoked according to the confirmation information, wherein the tax control management system is a system used by the state for managing invoices, and all invoice distributions are managed by the system.
  • the tax control management system can be installed in another server, and communication between the server and the server ensures that the invoice tax management system and the tax control management system maintain a communication connection, and the invoice distribution can be performed after the tax control management system is successfully invoked. .
  • S105 Execute the preset breakpoint code to generate an invoice to receive the abnormal data to complete the construction of the invoice receiving abnormality.
  • the preset breakpoint code is a background program code corresponding to the invoice management system including the breakpoint mark, specifically, where the returning call result code of the tax control management system is returned in the background program code.
  • the breakpoint flag is processed to form the preset breakpoint code, by which the code is prevented from further running down, thereby constructing the invoice to receive the abnormal data.
  • the abnormal phenomenon is used, which truly simulates that the invoice management system may have an abnormality in the receipt of the invoice during actual use, and the abnormal construction method is adopted through the invoice, and the invoice to the system is not required to be completed in an extreme case. Testing with exceptions makes it easy for testers to fully test the invoice management system and improve test efficiency.
  • the abnormality display interface is a preset display interface for displaying the invoice retrieval abnormal data.
  • the abnormal display interface may be a WEB display interface or a preset display window, and the specific display manner is not limited herein.
  • the abnormality data may be displayed by using the WEB display interface, or by popping up a preset display window, so that the tester can view the abnormal data of the invoice through the abnormal display interface.
  • the instruction to close the abnormal display interface is detected, that is, the tester is detected to close the abnormal display interface, for example, the tester clicks the close button on the preset display window, that is, the abnormality is detected to be closed.
  • Display interface instructions which in turn generate jump instructions and delete prompt information.
  • the deletion prompt information is used to prompt the tester to delete the breakpoint mark;
  • the jump instruction is used to jump to a preset position of the preset code page, where the preset code page is included in the return call result code.
  • the daemon code page of the invoice management system is used to close the invoice management system.
  • the jump instruction is jumped to the return call result code, and the delete prompt information is displayed through a preset display frame, where the prompt information is used to prompt the tester to delete the breakpoint mark, so that The testers successfully completed other tests on the VAT management system.
  • the abnormal construction method of the invoice of the above embodiment can not only construct the invoice exception phenomenon in an extreme case, but also facilitate the tester to comprehensively test the invoice management system, and display the abnormal data so that the tester can understand the abnormal data.
  • the jump command and the delete prompt information are used to help the tester quickly eliminate the preset breakpoint code, so as to perform other tests on the invoice management system.
  • FIG. 3 is a schematic flowchart of a method for constructing an invoice exception according to an embodiment of the present application.
  • the method can be run in a terminal or a server.
  • the method for constructing an invoice exception includes steps S201 to S210.
  • the obtaining the background program code corresponding to the invoice management system refers to acquiring the corresponding background program code of the tax control management system corresponding to the program code of the invoice management system. Specifically, the obtaining is performed by including the corresponding code identifier of the tax control management system.
  • the background program code performs a search according to the identifier corresponding to the return call result code. For example, if the identifier corresponding to the return call result code is skResult.returncode, the return call result code may be searched according to the identifier.
  • the return call result code corresponding to the tax control management system according to the identifier corresponding to the return call result code, and jumping to the program code line where the call result code is located and the program code
  • the line is preset, for example, the preset code line is marked with a specific color, and is marked in red for the tester to view and compare.
  • a return point tag process is added to the return call result code of the return tax management system to form the preset breakpoint code, and the code is further blocked by the breakpoint mark. Running down, you can construct an invoice to receive abnormal data.
  • the adding a breakpoint mark at the return call result code to generate a preset breakpoint code further includes: adding a preset function code at the preset breakpoint code; and executing the The breakpoint instruction corresponding to the preset breakpoint code is modified to a preset jump instruction.
  • a breakpoint exception is triggered, causing the program to be aborted, and the breakpoint instruction is modified into a preset jump instruction, and the preset function code is executed according to the preset jump instruction, and the original program code is interrupted.
  • the preset function code corresponding to the preset jump instruction may also be executed to implement a new function, for example, the preset function code is used to display abnormal data or notify the user of an abnormality, and the original program code may also be interrupted. Complete the construction of the invoice to receive the abnormal data.
  • the preset function code is added at the preset breakpoint code, and can be added in the form of a code address.
  • acquiring the invoice retrieval information sent by the first terminal including obtaining the tax subject, the receiving institution, the recipient information, the initiation time, the application description, the invoicing terminal, the invoice information, and the like in the invoicing information.
  • the invoice information includes the invoice type and the number of applications
  • the recipient information includes the name of the recipient and the contact information of the recipient.
  • S205 Generate invoice distribution information according to the invoice retrieval information, and send the invoice distribution information to the second terminal.
  • the generating the invoice distribution information according to the invoice retrieval information specifically converting the acquired invoice retrieval information into corresponding invoice distribution information.
  • the invoice distribution information includes the originating institution, the initiator information, the originating time, the taxing entity, the core board, the invoicing terminal, the invoice information (invoice type, the number of applications and the number of copies), and the invoice details, specifically the invoice details including the invoice Code, invoice start number, and invoice stop number.
  • the information is generated according to the invoice-receiving information, that is, the invoice distribution information and the invoice-receiving information correspond to each other, for example, the taxpayer and the recipient information respectively correspond to the originating institution and the sponsor information.
  • S206 Receive confirmation information fed back by the second terminal, where the confirmation information is information generated by the second terminal confirming the invoice distribution information.
  • the invoice manager of the second terminal after checking the invoice distribution information and confirming that there is no problem, may click to confirm the issuance to send the confirmation information to the server through the second terminal, that is, the server receives the The confirmation information about the invoice distribution information fed back by the second terminal is performed according to the confirmation information, and step S207 is performed.
  • the tax control management system is invoked according to the confirmation information, wherein the tax control management system is a system used by the state for managing invoices, and all invoice distributions are managed by the system. It can distribute invoices after the tax management system is successfully called.
  • the preset breakpoint code is a background program code corresponding to the invoice management system including the breakpoint mark, specifically, where the returning call result code of the tax control management system is returned in the background program code.
  • the breakpoint flag is processed to form the preset breakpoint code, by which the code is prevented from further running down, thereby constructing the invoice to receive the abnormal data.
  • the preset processing strategy includes: 1. Entering an invoice flow menu of the invoice management system, and clicking the invoice terminal again; 2. restarting the invoice requisition process for applying the same invoice number and the number of copies; 3, remove the program breakpoints that have been blocked in the program before, let it run normally; 4, distribute invoice data. After all the processes are completed, the previously abnormal invoice data can be cleared and the re-applied invoice data can be distributed to the invoice recipient corresponding to the first terminal.
  • the preset processing policy may also be other policies, for example, to remind the invoice recipient of the current invoice to be used abnormally, and to re-take the invoice receiving process. It can also be other strategies, which are not limited here.
  • the default processing policy is sent to the recipient in the invoice receiving information, and the contact information of the recipient can be obtained from the invoice receiving information, and the contact is contacted according to the recipient.
  • the information sends the preset processing policy to the recipient. If the recipient determines that the preset processing policy is received, the stability of the invoice retrieval function of the invoice management system may be explained.
  • the preset processing policy can be sent to the recipient by means of email to inform the recipient how to handle the abnormality, or by means of a mobile phone number by text message.
  • the preset processing policy is sent to the recipient to inform the recipient how to handle the exception.
  • the abnormal construction method of the invoice of the above embodiment can not only quickly construct an abnormality of the invoice, but also send the preset processing strategy to the employer to verify the stability of the invoice management function of the invoice management system. . The tester's comprehensive testing of the invoice management system is ensured.
  • FIG. 4 is a schematic block diagram of an apparatus for constructing an abnormality of an invoice according to an embodiment of the present application.
  • the invoice-using abnormal construction device 400 can be installed on a server.
  • the invoice-collection abnormality constructing apparatus 400 includes an information acquiring unit 401, a generating and transmitting unit 402, an information receiving unit 403, a call distributing unit 404, an execution generating unit 405, an interface calling unit 406, and a data display unit 407.
  • the information obtaining unit 401 is configured to acquire the invoice retrieval information sent by the first terminal.
  • the generating sending unit 402 is configured to generate invoice distribution information according to the invoice receiving information, and send the invoice distribution information to the second terminal.
  • the information receiving unit 403 is configured to receive the confirmation information fed back by the second terminal, where the confirmation information is information generated by the second terminal confirming the invoice distribution information.
  • the distribution unit 404 is called to invoke the tax management system to perform invoice distribution according to the confirmation information.
  • the execution generation unit 405 executes the preset breakpoint code to generate the invoice retrieval abnormal data to complete the construction of the invoice retrieval abnormality.
  • the interface invoking unit 406 is configured to invoke an abnormal display interface.
  • the data display unit 407 is configured to display the invoice retrieval abnormal data through the abnormality display interface.
  • the instruction generating unit 408 is configured to generate a jump instruction and a deletion prompt information, if the instruction to close the abnormal display interface is detected, wherein the deletion prompt information is used to prompt the tester to delete the breakpoint mark.
  • the jump display unit 409 is configured to jump to the return call result code according to the jump instruction, and display the delete prompt information.
  • FIG. 5 is a schematic block diagram of an apparatus for constructing an abnormality of an invoice according to an embodiment of the present application.
  • the invoice-using abnormal construction device 500 can be installed in a server or a terminal.
  • the invoice-collection abnormality constructing apparatus 500 includes a code acquisition unit 501, a code search unit 502, an addition generation unit 503, an information acquisition unit 504, a generation transmission unit 505, an information reception unit 506, and a call distribution unit 507.
  • the code obtaining unit 501 is configured to acquire a background program code corresponding to the invoice management system.
  • the code searching unit 502 is configured to search, in the background program code, a return call result code corresponding to the tax control management system.
  • the adding generating unit 503 is configured to add a breakpoint mark at the return call result code to generate a preset breakpoint code.
  • the information obtaining unit 504 is configured to acquire invoice retrieval information sent by the first terminal.
  • the generating sending unit 505 is configured to generate invoice distribution information according to the invoice receiving information, and send the invoice distribution information to the second terminal.
  • the information receiving unit 506 is configured to receive the confirmation information fed back by the second terminal, where the confirmation information is information generated by the second terminal confirming the invoice distribution information.
  • the distribution unit 507 is called to invoke the tax control management system to perform invoice distribution according to the confirmation information.
  • the execution generating unit 508 is configured to execute the preset breakpoint code to generate the invoice retrieval abnormal data to complete the configuration of the invoice retrieval abnormality.
  • the policy selection unit 509 is configured to select a preset processing policy corresponding to the invoice retrieval abnormal data.
  • the policy sending unit 510 is configured to send the preset processing policy to the recipient in the invoice receiving information.
  • the abnormal construction device of the invoice of the above embodiment can not only quickly construct an abnormality of the invoice, but also send the preset processing strategy to the employer to verify the stability of the invoice management function of the invoice management system. . The tester's comprehensive testing of the invoice management system is ensured.
  • the above apparatus may be embodied in the form of a computer program that can be run on a computer device as shown in FIG.
  • FIG. 6 is a schematic block diagram of a computer device according to an embodiment of the present application.
  • the computer device 600 device can be a terminal or a server.
  • the computer device 600 includes a processor 620, a memory, and a network interface 650 connected by a system bus 610, wherein the memory can include a non-volatile storage medium 630 and an internal memory 640.
  • the non-volatile storage medium 630 can store an operating system 631 and a computer program 632.
  • the processor 620 can be caused to perform a method of constructing an invoice for an exception.
  • the processor 620 is used to provide computing and control capabilities to support the operation of the entire computer device 600.
  • the internal memory 640 provides an environment for the operation of a computer program in a non-volatile storage medium that, when executed by the processor 620, can cause the processor 620 to perform a method of constructing an invoice for an exception.
  • the network interface 650 is used for network communication, such as sending assigned tasks and the like. It will be understood by those skilled in the art that the structure shown in FIG. 6 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device 600 to which the solution of the present application is applied, and a specific computer device. 600 may include more or fewer components than shown, or some components may be combined, or have different component arrangements.
  • the processor 620 is configured to execute the program code stored in the memory to implement the step corresponding to the constructing method of the invoice retrieval exception provided by the foregoing embodiment.
  • the processor 620 may be a central processing unit (CPU), and the processor 620 may also be another general-purpose processor, a digital signal processor (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • computer device 600 architecture illustrated in FIG. 6 does not constitute a limitation to computer device 600, may include more or fewer components than illustrated, or may combine certain components, or different components. Arrangement.
  • the computer readable storage medium may be a medium that can store program code, such as a magnetic disk, an optical disk, a USB flash drive, a removable hard disk, a magnetic disk, or an optical disk.
  • invoices may be implemented in other manners by employing abnormal construction devices and methods.
  • the embodiment of the construction device described above for invoicing exceptions is merely illustrative.
  • the division of each unit is only a logical function division, and there may be another division manner in actual implementation.
  • multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • the units in the apparatus of the embodiment of the present application may be combined, divided, and deleted according to actual needs.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium.
  • the technical solution of the present application may be in essence or part of the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • There are a number of instructions for causing a computer device (which may be a personal computer, terminal, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.

Abstract

本申请公开一种发票领用异常的构造方法、装置、计算机设备及存储介质，该方法在获取第一终端发送的发票领用信息后，根据发票领用信息生成发票分发信息并发送至第二终端；接收第二终端反馈的确认信息；根据确认信息调用税控管理系统以进行发票分发；以及执行预设断点代码生成发票领用异常数据以完成发票领用异常的构造。

Description

发票领用异常的构造方法、装置、计算机设备及存储介质
本申请要求于2017年11月24日提交中国专利局、申请号为201711190432.3、发明名称为“发票领用异常的构造方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及软件测试技术领域，尤其涉及一种发票领用异常的构造方法、装置、计算机设备及存储介质。
背景技术
目前，在发票管理系统的日常测试过程中，通过发票终端领用发票时出现异常数据的情况不易产生，必须在极端的情况下才可以产生，比如在发票终端领用流程创建后进行发票分发时，发票终端由于突然断电或断网，才会出现发票领用异常现象，这种情况给版本测试覆盖带来很大不便，由此造成无法有效地测试该种场景的功能是否正常。因此需要一种发票领用异常构造方法，用于构造该发票领用异常现象以完成对发票管理系统的全面测试。
发明内容
本申请提供了一种发票领用异常的构造方法、装置、计算机设备及存储介质，旨在构造出发票领用异常现象以方便对发票管理系统进行测试。
第一方面，本申请提供了一种发票领用异常的构造方法，其包括：
获取第一终端发送的发票领用信息；
根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；
接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；
根据所述确认信息调用税控管理系统以进行发票分发；以及
执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
第二方面，本申请提供了一种发票领用异常的构造装置，其包括：
信息获取单元，用于获取第一终端发送的发票领用信息；
生成发送单元，用于根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；
信息接收单元，用于接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；
调用分发单元，用于根据所述确认信息调用税控管理系统以进行发票分发；以及
执行生成单元，用于执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
第三方面，本申请又提供了一种计算机设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述程序时实现本申请提供的任一项所述的发票领用异常的构造方法。
第四方面，本申请还提供了一种存储介质，其中所述存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行本申请提供的任一项所述的发票领用异常的构造方法。
本申请实施例通过获取第一终端发送的发票领用信息；根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；根据所述确认信息调用税控管理系统以进行发票分发；以及执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。通过该方法可以无需在极端的情况下构造出发票领用异常现象，进而方便测试人员对发票管理系统的全面测试，同时方便系统维护。
附图说明
为了更清楚地说明本申请实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以 根据这些附图获得其他的附图。
图1是本申请一实施例提供的发票管理系统的应用场景的示意图；
图2是本申请一实施例提供的一种发票领用异常的构造方法示意流程图；
图3是本申请另一实施例提供的一种发票领用异常的构造方法示意流程图；
图4是本申请一实施例提供的一种发票领用异常的构造装置示意性框图；
图5是本申请另一实施例提供的一种发票领用异常的构造装置示意性框图；
图6是本申请一实施例提供的一种计算机设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的实施例提供了一种发票领用异常的构造方法、装置、计算机设备及存储介质。其中该发票领用异常的构造方法用于测试发票管理系统，该发票管理系统用于公司的发票管理，该发票管理系统也可以称为增值税管理系统。
为了便于理解，先对该发票管理系统的应用场景组成进行介绍，如图1所示，该发票管理系统的应用场景包括第一终端、第二终端和服务器。
其中，第一终端和第二终端可以是智能手机、平板电脑、笔记本电脑、台式电脑、个人数字助理和穿戴式设备等电子设备；服务器可以是独立的服务器，也可以是多个服务器组成的服务器集群。
其中，所述服务器用于执行本申请提供的任意一种发票领用异常的构造方法，以构造出发票领用异常现象，便于该发票管理系统的测试。
基于图1，详细介绍本实施例提供的发票领用异常的构造方法，请同时参阅图2，图2是本申请实施例提供的一种发票领用异常的构造方法的示意流程图。如图2所示，该发票领用异常的构造方法包括步骤S101～S109。
S101、获取第一终端发送的发票领用信息。
在本实施例中，服务器获取第一终端发送的发票领用信息，该发票领用信息包括纳税主体、领用机构、领用人信息、发起时间、申请说明、开票终端和发票信息等。其中发票信息包括发票类型和申请份数等，领用人信息包括领用 名称和领用人联系信息等。
具体地，该发票领用信息可以为用户(即领用人)通过第一终端中安装的发票管理系统对应的客户端填写领用发票时所需的信息，在所述用户填完这些信息并点击确认后，所述第一终端则将所述发票领用信息发送至服务器。
在一实施例中，为了方便快速完成软件测试，也可以通过预设发票领用信息的方式，该预设发票领用信息为预先设置好的发票领用信息。相对应地，获取第一终端发送的发票领用信息，包括：获取所述第一终端发送的预设发票领用信息作为发票领用信息。因此省去用户填写的过程，进而加快了软件的测试效率。
S102、根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端。
在本实施例中，所述根据所述发票领用信息生成发票分发信息，具体是将获取到所述发票领用信息转换成对应的发票分发信息。其中该发票分发信息包括发起机构、发起人信息、发起时间、纳税主体、核心板、开票终端、发票信息(发票类型、申请份数和发放份数)以及发票明细，具体地该发票明细包括发票代码、发票起始号码和发票截止号码等。发票分发信息时根据发票领用信息生成的，即该发票分发信息和发票领用信息时相对应的，比如纳税主体、领用人信息分别与发起机构、发起人信息相对应。
具体地，根据所述发票领用信息生成发票分发信息后，将所述发票分发信息发送至第二终端，由第二终端呈现给相应的发票管理人员以便查看该发票分发信息。
S103、接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息。
在本实施例中，具体地，所述第二终端的发票管理人员在查看发票分发信息后并确认没有问题时，可点击确认发放以通过该第二终端将确认信息发送至服务器，即服务器接收到所述第二终端反馈的关于所述发票分发信息的确认信息，并根据该确认信息执行步骤S104。
S104、根据所述确认信息调用税控管理系统以进行发票分发。
在本实施例中，根据所述确认信息调用税控管理系统，其中该税控管理系统为国家用于管理发票的系统，所有的发票分发均需通过该系统进行管理。其 中该税控管理系统可安装在另一服务器中，通过服务器和服务器之间通信以确保该发票税管理系统和税控管理系统保持通信连接，在调用税控管理系统成功后即可进行发票分发。
S105、执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
在本实施例中，该预设断点代码是包括断点标记的发票管理系统对应的后台程序代码，具体地是在该后台程序代码中有返还调用税控管理系统的返还调用结果代码处添加断点标记处理以形成该预设断点代码，通过该断点标记阻止代码进一步往下运行，由此可以构造出发票领用异常数据。
通过上述构造发票领用异常现象，其真实地模拟出该发票管理系统在实际使用时可能出现发票领用异常现象，通过该发票领用异常构造方法无需在极端的情况下即完成对系统的发票领用异常进行测试，进而方便测试人员对发票管理系统的全面测试，还提高了测试效率。
S106、调用异常显示界面。
具体地，该异常显示界面为预设显示界面用于显示发票领用异常数据。该异常显示界面可以为WEB显示界面，也可以为一个预设显示窗口，具体的显示方式在此不做限定。
S107、通过所述异常显示界面显示所述发票领用异常数据。
具体地，可以通过所述WEB显示界面显示，或者通过弹出预设显示窗口以显示所述异常数据，进而方便测试人员通过该异常显示界面查看所述发票领用异常数据。
S108、若检测到关闭所述异常显示界面的指令，生成跳转指令和删除提示信息，其中所述删除提示信息用于提示测试人员删除断点标记。
在本实施例中，检测到关闭所述异常显示界面的指令，是指检测到测试人员关闭该异常显示界面，比如测试人员点击预设显示窗口上的关闭按钮，即为检测到关闭所述异常显示界面的指令，进而生成跳转指令和删除提示信息。其中所述删除提示信息用于提示测试人员删除所述断点标记；跳转指令用于跳转到预设代码页面某个预设位置，该预设代码页面为包括所述返还调用结果代码的发票管理系统的后台程序代码页。
S109、根据所述跳转指令跳转至返还调用结果代码处，并显示所述删除提 示信息。
在本实施例中，具体根据所述跳转指令跳转至所述返还调用结果代码处同时通过预设显示框显示所述删除提示信息，该提示信息用于提示测试人员删除断点标记，以便测试人员顺利地完成对增值税管理系统的其他测试。
上述实施例的发票领用异常的构造方法不仅可以无需在极端的情况下构造出发票领用异常现象，方便测试人员对发票管理系统的全面测试，同时显示该异常数据以便测试人员了解该异常数据，此外还通过跳转指令和删除提示信息帮助测试人员快速消除该预设断点代码，以便对该发票管理系统进行其他项测试。
请参阅图3，图3是本申请实施例提供的一种发票领用异常的构造方法的示意流程图。该方法可以运行在终端或服务器中，如图3所示，该发票领用异常的构造方法包括步骤S201～S210。
S201、获取所述发票管理系统对应的后台程序代码。
在本实施例中，获取所述发票管理系统对应的后台程序代码，是指获取所述发票管理系统对应程序代码中包含有所述税控管理系统的对应的后台程序代码。具体地，通过包括所述税控管理系统对应代码标识进行获取。
S202、在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码。
在本实施例中，在所述后台程序代码中根据返还调用结果代码对应的标识进行查找，比如返还调用结果代码对应的标识为skResult.returncode，则可以根据该标识查找返还调用结果代码。
具体地，根据返还调用结果代码对应的标识在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码后，并跳转至该调用结果代码所在程序代码行以及将该程序代码行进行预设标记，比如将该预设代码行进行特定颜色标记，进行红色标记，方便测试人员查看和对比。
S203、在所述返还调用结果代码处添加断点标记以生成预设断点代码。
在本实施例中，具体地是在该后台程序代码中有返还调用税控管理系统的返还调用结果代码处添加断点标记处理以形成该预设断点代码，通过该断点标记阻止代码进一步往下运行，由此可以构造出发票领用异常数据。
在一实施例中，所述在所述返还调用结果代码处添加断点标记以生成预设断点代码，还包括：在所述预设断点代码处添加预设功能代码；以及将执行所述预设断点代码对应的断点指令修改为预设跳转指令。执行断点指令时将触发一个断点异常，导致程序异常中断，而将断点指令修改为预设跳转指令，根据所述预设跳转指令执行所述预设功能代码，在原程序代码中断后还可执行所述预设跳转指令对应的预设功能代码，进而实现新的功能，比如预设功能代码用于实现显示异常数据或者通知用户异常等，同时还可中断原来的程序代码以完成构造出发票领用异常数据。具体地，在所述预设断点代码处添加预设功能代码，可以用代码地址的形式添加。
S204、获取第一终端发送的发票领用信息。
在本实施例中，获取第一终端发送的发票领用信息，包括获取该发票领用信息中的纳税主体、领用机构、领用人信息、发起时间、申请说明、开票终端和发票信息等。其中发票信息包括发票类型和申请份数等，领用人信息包括领用名称和领用人联系信息等。
S205、根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端。
在本实施例中，所述根据所述发票领用信息生成发票分发信息，具体是将获取到所述发票领用信息转换成对应的发票分发信息。其中该发票分发信息包括发起机构、发起人信息、发起时间、纳税主体、核心板、开票终端、发票信息(发票类型、申请份数和发放份数)以及发票明细，具体地该发票明细包括发票代码、发票起始号码和发票截止号码等。发票分发信息时根据发票领用信息生成的，即该发票分发信息和发票领用信息时相对应的，比如纳税主体、领用人信息分别与发起机构、发起人信息相对应。
S206、接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息。
在本实施例中，具体地所述第二终端的发票管理人员在查看发票分发信息后并确认没有问题时，可点击确认发放以通过该第二终端将确认信息发送至服务器，即服务器接收到所述第二终端反馈的关于所述发票分发信息的确认信息，并根据该确认信息执行步骤S207。
S207、根据所述确认信息调用税控管理系统以进行发票分发。
在本实施例中，根据所述确认信息调用税控管理系统，其中该税控管理系统为国家用于管理发票的系统，所有的发票分发均需通过该系统进行管理。其在调用税控管理系统成功后即可进行发票分发。
S208、执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
在本实施例中，该预设断点代码是包括断点标记的发票管理系统对应的后台程序代码，具体地是在该后台程序代码中有返还调用税控管理系统的返还调用结果代码处添加断点标记处理以形成该预设断点代码，通过该断点标记阻止代码进一步往下运行，由此可以构造出发票领用异常数据。
S209、选择所述发票领用异常数据对应的预设处理策略。
在本实施例中，具体地，该预设处理策略包括：1、进入发票管理系统的发票流转菜单，再次点击发票终端领用；2、重启申请相同发票号码、份数的发票领用流程；3、去除之前在程序中已经阻断的程序断点，让其正常运行；4、分发发票数据。走完所有流程就可以将之前异常的发票数据清除且重新申请的发票数据可以分发到第一终端对应的发票领用人。
在一实施例中，该预设处理策略也可以为其他策略，比如为提醒所述发票领用人当前发票领用异常、重新走发票领用流程。具体还可以为其他策略，在此不做限定。
S210、将所述预设处理策略发送至所述发票领用信息中的领用人。
在本实施例中，将所述预设处理策略发送至所述发票领用信息中的领用人，可以从所述发票领用信息中获取领用人联系信息，根据所述领用人联系信息将所述预设处理策略发送至所述领用人。如果所述领用人确定收到该预设处理策略，则可说明该发票管理系统的发票领用功能的稳定性。
比如，领用人联系信息为Email或手机号码，则可以通过Email的方式将该预设处理策略发送至领用人以告知所述领用人如何处理该异常，或者通过手机号码以短信的方式将该预设处理策略发送至领用人以告知所述领用人如何处理该异常。
上述实施例的发票领用异常的构造方法不仅可以快速地构造出发票领用异常现象，同时还可将预设处理策略发送至领用人，以验证发票管理系统的发票领用功能的稳定性。确保了测试人员对该发票管理系统的全面测试。
请参阅图4，图4是本申请实施例提供的一种发票领用异常的构造装置的示意性框图。该发票领用异常的构造装置400可安装于服务器。如图4所示，发票领用异常的构造装置400包括信息获取单元401、生成发送单元402、信息接收单元403、调用分发单元404、执行生成单元405、界面调用单元406、数据显示单元407、指令生成单元408和跳转显示单元409。
信息获取单元401，用于获取第一终端发送的发票领用信息。
生成发送单元402，用于根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端。
信息接收单元403，用于接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息。
调用分发单元404，用于根据所述确认信息调用税控管理系统以进行发票分发。
执行生成单元405，执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
界面调用单元406，用于调用异常显示界面。
数据显示单元407，用于通过所述异常显示界面显示所述发票领用异常数据。
指令生成单元408，用于若检测到关闭所述异常显示界面的指令，生成跳转指令和删除提示信息，其中所述删除提示信息用于提示测试人员删除所述断点标记。
跳转显示单元409，用于根据所述跳转指令跳转至所述返还调用结果代码处，并显示所述删除提示信息。
请参阅图5，图5是本申请实施例提供的一种发票领用异常的构造装置的示意性框图。该发票领用异常的构造装置500可安装于服务器或终端中。如图5所示，该发票领用异常的构造装置500包括代码获取单元501、代码查找单元502、添加生成单元503、信息获取单元504、生成发送单元505、信息接收单元506、调用分发单元507、执行生成单元508、策略选择单元509和策略发送单元510。
代码获取单元501，用于获取所述发票管理系统对应的后台程序代码。
代码查找单元502，用于在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码。
添加生成单元503，用于在所述返还调用结果代码处添加断点标记以生成预设断点代码。
信息获取单元504，用于获取第一终端发送的发票领用信息。
生成发送单元505，用于根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端。
信息接收单元506，用于接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息。
调用分发单元507，用于根据所述确认信息调用税控管理系统以进行发票分发。
执行生成单元508，用于执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
策略选择单元509，用于选择所述发票领用异常数据对应的预设处理策略。
策略发送单元510，用于将所述预设处理策略发送至所述发票领用信息中的领用人。
上述实施例的发票领用异常的构造装置不仅可以快速地构造出发票领用异常现象，同时还可将预设处理策略发送至领用人，以验证发票管理系统的发票领用功能的稳定性。确保了测试人员对该发票管理系统的全面测试。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
上述装置可以实现为一种计算机程序的形式，计算机程序可以在如图6所示的计算机设备上运行。
请参阅图6，图6是本申请实施例提供的一种计算机设备的示意性框图。该计算机设备600设备可以是终端或服务器。
参照图6，该计算机设备600包括通过系统总线610连接的处理器620、存储器和网络接口650，其中，存储器可以包括非易失性存储介质630和内存储器 640。
该非易失性存储介质630可存储操作系统631和计算机程序632。该计算机程序632被执行时，可使得处理器620执行一种发票领用异常的构造方法。
该处理器620用于提供计算和控制能力，支撑整个计算机设备600的运行。
该内存储器640为非易失性存储介质中的计算机程序的运行提供环境，该计算机程序被处理器620执行时，可使得处理器620执行一种发票领用异常的构造方法。
该网络接口650用于进行网络通信，如发送分配的任务等。本领域技术人员可以理解，图6中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备600的限定，具体的计算机设备600可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
其中，所述处理器620用于运行存储在存储器中的程序代码，以实现上述实施例提供的发票领用异常的构造方法对应的步骤。
应当理解，在本申请实施例中，处理器620可以是中央处理单元(Central Processing Unit，CPU)，该处理器620还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。其中，通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本领域技术人员可以理解，图6中示出的计算机设备600结构并不构成对计算机设备600的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本领域普通技术人员可以理解的是实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，程序可存储于一存储介质中，该存储介质为计算机可读存储介质。如本申请实施例中，该程序可存储于计算机系统的存储介质中，并被该计算机系统中的至少一个处理器执行，以实现包括如上述各方法的实施例的流程步骤。
该计算机可读存储介质可以是磁碟、光盘、U盘、移动硬盘、磁碟或者光 盘等各种可以存储程序代码的介质。
在本申请所提供的几个实施例中，应该理解到，所揭露的发票领用异常的构造装置和方法，可以通过其它的方式实现。例如，以上所描述的发票领用异常的构造装置实施例仅仅是示意性的。例如，各个单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。
本申请实施例装置中的单元可以根据实际需要进行合并、划分和删减。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，终端，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种发票领用异常的构造方法，用于测试发票管理系统，其包括：
    获取第一终端发送的发票领用信息；
    根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；
    接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；
    根据所述确认信息调用税控管理系统以进行发票分发；以及
    执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
  2. 根据权利要求1所述的发票领用异常的构造方法，其中，在所述获取第一终端发送的发票领用信息之前，还包括：
    获取所述发票管理系统对应的后台程序代码；
    在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码；以及
    在所述返还调用结果代码处添加断点标记以生成预设断点代码。
  3. 根据权利要求2所述的发票领用异常的构造方法，其中，在所述执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造之后，还包括：
    调用异常显示界面；以及
    通过所述异常显示界面显示所述发票领用异常数据。
  4. 根据权利要求3所述的发票领用异常的构造方法，其中，在所述通过所述异常显示界面显示所述发票领用异常数据之后，还包括：
    若检测到关闭所述异常显示界面的指令，生成跳转指令和删除提示信息，其中所述删除提示信息用于提示测试人员删除所述断点标记；以及
    根据所述跳转指令跳转至所述返还调用结果代码处，并显示所述删除提示信息。
  5. 根据权利要求1所述的发票领用异常的构造方法，其中，在所述执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造之后，还包 括：
    选择所述发票领用异常数据对应的预设处理策略；以及
    将所述预设处理策略发送至所述发票领用信息中的领用人。
  6. 根据权利要求1所述的发票领用异常的构造方法，其中，所述获取第一终端发送的发票领用信息，包括：
    获取所述第一终端发送的预设发票领用信息作为发票领用信息
  7. 根据权利要求2所述的发票领用异常的构造方法，其中，所述在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码，包括：
    根据返还调用结果代码对应的标识在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码；
    跳转至该调用结果代码所在程序代码行以及将该程序代码行进行预设标记。
  8. 一种发票领用异常的构造装置，用于测试发票管理系统，其包括：
    信息获取单元，用于获取第一终端发送的发票领用信息；
    生成发送单元，用于根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；
    信息接收单元，用于接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；
    调用分发单元，用于根据所述确认信息调用税控管理系统以进行发票分发；以及
    执行生成单元，用于执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
  9. 根据权利要求8所述的发票领用异常的构造装置，其中，还包括：
    代码获取单元，用于获取所述发票管理系统对应的后台程序代码；
    代码查找单元，用于在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码；以及
    添加生成单元，用于在所述返还调用结果代码处添加断点标记以生成预设断点代码。
  10. 根据权利要求9所述的发票领用异常的构造装置，其中，还包括：
    界面调用单元，用于调用异常显示界面；以及
    数据显示单元，用于通过所述异常显示界面显示所述发票领用异常数据。
  11. 一种计算机设备，其包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如下步骤：
    获取第一终端发送的发票领用信息；
    根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；
    接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；
    根据所述确认信息调用税控管理系统以进行发票分发；以及
    执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
  12. 根据权利要求11所述的计算机设备，其中，所述处理器执行所述计算机程序时实现所述获取第一终端发送的发票领用信息之前，还实现如下步骤：
    获取所述发票管理系统对应的后台程序代码；
    在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码；以及
    在所述返还调用结果代码处添加断点标记以生成预设断点代码。
  13. 根据权利要求12所述的计算机设备，其中，所述处理器执行所述执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造之后，还实现如下步骤：
    调用异常显示界面；以及
    通过所述异常显示界面显示所述发票领用异常数据。
  14. 根据权利要求13所述的计算机设备，其中，所述处理器执行所述通过所述异常显示界面显示所述发票领用异常数据之后，还实现如下步骤：
    若检测到关闭所述异常显示界面的指令，生成跳转指令和删除提示信息，其中所述删除提示信息用于提示测试人员删除所述断点标记；以及
    根据所述跳转指令跳转至所述返还调用结果代码处，并显示所述删除提示信息。
  15. 根据权利要求11所述的计算机设备，其中，所述处理器执行所述执行 预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造之后，还实现如下步骤：
    选择所述发票领用异常数据对应的预设处理策略；以及
    将所述预设处理策略发送至所述发票领用信息中的领用人。
  16. 一种存储介质，其中，所述存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行如下步骤：
    获取第一终端发送的发票领用信息；
    根据所述发票领用信息生成发票分发信息，并将所述发票分发信息发送至第二终端；
    接收所述第二终端反馈的确认信息，其中所述确认信息为所述第二终端对所述发票分发信息进行确认而生成的信息；
    根据所述确认信息调用税控管理系统以进行发票分发；以及
    执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造。
  17. 根据权利要求16所述的存储介质，其中，所述程序指令当被处理器执行时使所述处理器执行所述获取第一终端发送的发票领用信息之前，还执行如下步骤：
    获取所述发票管理系统对应的后台程序代码；
    在所述后台程序代码中查找所述税控管理系统对应的返还调用结果代码；以及
    在所述返还调用结果代码处添加断点标记以生成预设断点代码。
  18. 根据权利要求17所述的存储介质，其中，所述程序指令当被处理器执行时使所述处理器执行所述执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造之后，还执行如下步骤：
    调用异常显示界面；以及
    通过所述异常显示界面显示所述发票领用异常数据。
  19. 根据权利要求18所述的存储介质，其中，所述程序指令当被处理器执行时使所述处理器执行所述通过所述异常显示界面显示所述发票领用异常数据之后，还执行如下步骤：
    若检测到关闭所述异常显示界面的指令，生成跳转指令和删除提示信息， 其中所述删除提示信息用于提示测试人员删除所述断点标记；以及
    根据所述跳转指令跳转至所述返还调用结果代码处，并显示所述删除提示信息。
  20. 根据权利要求16所述的存储介质，其中，所述程序指令当被处理器执行时使所述处理器执行所述执行预设断点代码生成发票领用异常数据以完成所述发票领用异常的构造之后，还执行如下步骤：
    选择所述发票领用异常数据对应的预设处理策略；以及
    将所述预设处理策略发送至所述发票领用信息中的领用人。
PCT/CN2018/084043 2017-11-24 2018-04-23 发票领用异常的构造方法、装置、计算机设备及存储介质 WO2019100655A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711190432.3A CN108255705A (zh) 2017-11-24 2017-11-24 发票领用异常的构造方法、装置、计算机设备及存储介质
CN201711190432.3 2017-11-24

Publications (1)

Publication Number Publication Date
WO2019100655A1 true WO2019100655A1 (zh) 2019-05-31

Family

ID=62722124

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/084043 WO2019100655A1 (zh) 2017-11-24 2018-04-23 发票领用异常的构造方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN108255705A (zh)
WO (1) WO2019100655A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112686307A (zh) * 2020-12-30 2021-04-20 平安普惠企业管理有限公司 基于人工智能获取发票的方法、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1873706A (zh) * 2006-06-30 2006-12-06 邱奇友 自助扣税的税票发票开票系统及其应用方法
CN2852489Y (zh) * 2005-12-21 2006-12-27 成都前锋电子电器集团股份有限公司 税控收款机断电保护电路
CN105138459A (zh) * 2015-09-11 2015-12-09 北京金山安全软件有限公司 一种对软件程序进行测试的方法及装置
CN107341107A (zh) * 2017-07-04 2017-11-10 飞天诚信科技股份有限公司 一种嵌入式开发的自动化测试方法及测试主机

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5050168A (en) * 1989-12-29 1991-09-17 Paterson Timothy L Test coverage analyzer
CN101937372B (zh) * 2010-08-30 2012-10-10 北京数码大方科技有限公司 异常处理的方法及装置
CN102831054B (zh) * 2012-06-30 2015-12-02 华为技术有限公司 程序断点处理方法及装置
CN106126431A (zh) * 2016-08-23 2016-11-16 腾讯科技（深圳）有限公司 性能测试方法及系统
CN106504040A (zh) * 2016-10-31 2017-03-15 青岛瑞宏科技有限公司 一种电子发票开票方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN2852489Y (zh) * 2005-12-21 2006-12-27 成都前锋电子电器集团股份有限公司 税控收款机断电保护电路
CN1873706A (zh) * 2006-06-30 2006-12-06 邱奇友 自助扣税的税票发票开票系统及其应用方法
CN105138459A (zh) * 2015-09-11 2015-12-09 北京金山安全软件有限公司 一种对软件程序进行测试的方法及装置
CN107341107A (zh) * 2017-07-04 2017-11-10 飞天诚信科技股份有限公司 一种嵌入式开发的自动化测试方法及测试主机

Also Published As

Publication number Publication date
CN108255705A (zh) 2018-07-06

Similar Documents

Publication Publication Date Title
US10482161B2 (en) Generating and displaying active reports
US20120144379A1 (en) System and method for updadting software
US9652220B2 (en) Zero down-time deployment of new application versions
US20150281035A1 (en) Monitoring of Node.JS Applications
US10102239B2 (en) Application event bridge
US10110522B1 (en) Setting sharing options for files using a messaging client
US20130073993A1 (en) Interaction with a visualized state transition model
US10536407B1 (en) Converting shared files to message attachments
US10191844B2 (en) Automatic garbage collection thrashing monitoring
WO2019100655A1 (zh) 发票领用异常的构造方法、装置、计算机设备及存储介质
US11243979B1 (en) Asynchronous propagation of database events
US20230092076A1 (en) Data recovery validation test
US9910737B2 (en) Implementing change data capture by interpreting published events as a database recovery log
US11888887B2 (en) Risk-based vulnerability remediation timeframe recommendations
US9542171B2 (en) Managing an application modification process
US9921901B2 (en) Alerting service desk users of business services outages
US20170039065A1 (en) Annotations in software development
US11599422B2 (en) System and method for device independent backup in distributed system
CN111176982A (zh) 一种测试界面生成方法和装置
US20150100615A1 (en) Drag and drop of a uri to link resources
US20150222505A1 (en) Business transaction resource usage tracking
US11928238B1 (en) Protecting customer data using different domains
US11886306B2 (en) Systems and methods for leveraging backup metadata to provide granular options for discovery of deleted items and recovery after data backup
US20220060488A1 (en) Methods for providing malware protection for cloud storage and devices thereof
CN115484149B (zh) 网络切换方法、网络切换装置、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18880744

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.08.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18880744

Country of ref document: EP

Kind code of ref document: A1