WO2020103545A1 - Blockchain-based smart contract debugging and releasing method and system - Google Patents
Blockchain-based smart contract debugging and releasing method and systemInfo
- Publication number
- WO2020103545A1 WO2020103545A1 PCT/CN2019/106021 CN2019106021W WO2020103545A1 WO 2020103545 A1 WO2020103545 A1 WO 2020103545A1 CN 2019106021 W CN2019106021 W CN 2019106021W WO 2020103545 A1 WO2020103545 A1 WO 2020103545A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- test
- smart contract
- channel
- contract
- transaction
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- 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/362—Software debugging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Definitions
- the invention relates to the field of blockchain technology, in particular to a method and system for debugging and issuing blockchain smart contracts.
- an embodiment of the present invention provides a method for debugging and issuing a blockchain smart contract to overcome the need to frequently perform contract content on the transaction channel for each modification and deployment of smart contracts in the prior art
- the consensus has increased the workload of various parties in the blockchain, and added many worthless test data to the transaction channel, affecting the query and storage of blocks and transactions on the channel.
- a method for debugging and releasing a blockchain smart contract includes the following steps:
- test channel is automatically created at the same time when the trading channel is created, and when the user joins or exits the trading channel, the user is simultaneously added or exited from the test channel;
- S2 Deploy the smart contract to be tested on the test channel, and all users on the test channel jointly perform business tests on the contract content;
- step S3 Determine whether the test of the smart contract to be tested passes. If it passes, perform step S4. If it fails, return the smart contract to the developer to modify or select a new smart contract and then return to step S2. Test it;
- the smart contract to be tested includes a newly submitted smart contract and / or a historical version of the smart contract.
- the S3 specifically includes:
- step S4 is executed, and if the test fails, the smart contract is returned to the developer and then returned to step S2 after modification to retest it; and / or,
- step S4 is executed. If the test fails, a new smart contract is selected and the process returns to step S2 to test it again.
- the S2 further includes:
- test data generated by running the smart contract on the test channel is recorded on the test channel, and the user can query the test data on the test channel.
- step S2 further includes:
- the user may delete the test data.
- step S4 further includes:
- a blockchain smart contract debugging and release system at least including:
- a new module is provided for users to create a trading channel, and a test channel is automatically created when the trading channel is created;
- the registration module is used to provide users to join or exit the trading channel, and when the user joins or exits the trading channel, the user is added or exited from the test channel synchronously;
- a test module which is used to deploy the smart contract to be tested on the test channel, and all users on the test channel jointly perform business tests on the contract content;
- the judgment module is used to judge whether the test of the smart contract to be tested passes. If it passes, the smart contract to be tested is sent to the release module. If it fails, the smart contract is returned to the developer for modification or Select a new smart contract and send it to the test module to test it again;
- the release module is used for all users on the test channel to reach a consensus on the content of the smart contract, and after obtaining feedback that the deployment is agreed, deploy the smart contract on the transaction channel.
- system further includes:
- a first storage module for recording test data generated by the smart contract running on the test channel in the test channel
- the first query module is used for the user to query the test data in the test channel.
- system further includes:
- the deletion module is used for the user to delete the test data after obtaining the consensus of all users on the test channel.
- system further includes:
- a second storage module configured to record the blocks and / or transaction data generated by the smart contract running on the transaction channel on the transaction channel;
- the second query module is used for the user to query the block and / or transaction data in the transaction channel.
- the method and system for debugging and issuing a blockchain smart contract provided by an embodiment of the present invention.
- the system automatically creates a test channel with the same participants for the transaction channel, which is used for testing before the contract is officially deployed.
- the content of the smart contract only needs to be guaranteed by the participants of the transaction channel during the test whether it is in line with its business. It is not necessary to conduct consensus certification of the contract content before each deployment test, reducing the workload of the participants and shortening the operation cycle of updating the contract;
- the method and system for debugging and issuing blockchain smart contracts provided by the embodiments of the present invention store test data and transaction data separately, and the two sets of data do not interfere with each other, which effectively improves the operation and query efficiency of the underlying network of the blockchain and improves stability. Sex
- the method and system for debugging and releasing blockchain smart contracts provided by the embodiments of the present invention introduces the process standardization and manageability in the software development project into the contract debugging and release of the blockchain channel, reducing contract maintenance costs Maximize the team's cooperation efficiency.
- Fig. 1 is a flowchart of a method for debugging and issuing a blockchain smart contract according to an exemplary embodiment
- Fig. 2 is a schematic structural diagram of a blockchain smart contract debugging and issuance system according to an exemplary embodiment.
- Fig. 1 is a flowchart of a method for debugging and issuing a blockchain smart contract according to an exemplary embodiment. Referring to Fig. 1, the method includes the following steps:
- test channel is automatically created when a trading channel is created, and when a user joins or exits the trading channel, the user is simultaneously added or exited from the test channel.
- blockchain users create a new transaction channel according to business needs.
- the system will automatically create a test channel for users with the same participating users when they create a transaction channel.
- New blockchain users join or exit the transaction channel At the same time, it will also join or exit the corresponding test channel synchronously.
- S2 Deploy the smart contract to be tested on the test channel, and all users on the test channel jointly perform business tests on the contract content.
- users in the blockchain can deploy the smart contract to be tested submitted by the contract developer to the test channel, and all users on the test channel jointly conduct business tests on the contract content.
- the content of the smart contract only needs to be guaranteed by the participants of the test channel (these parties are also participants of the transaction channel) during the test, and does not need to be Before each deployment test, the consensus authentication of the smart contract content is performed, which reduces the workload of each participant and shortens the operation cycle of updating the contract.
- Each participant can use the following process to test whether the content of the smart contract is consistent with its business:
- the user enters test parameters on the functional test page and performs functional tests on the smart contract to be tested.
- test data generated by running the smart contract on the test channel is recorded on the test channel, and the user can query the test data on the test channel.
- test data generated by running on the test channel will be recorded on the test channel, and the test data will be queried and displayed on the test channel, which means that the user can query on the test channel Test Data.
- the user may delete the test data.
- the consensus of all users on the channel needs to be obtained, and it cannot be deleted by itself.
- the channel user occupying more storage space for the test data can initiate the deletion of the test data, and the storage space occupied by the data can only be used after consensus of all users on the test channel To release. By doing so, you can ensure that the data on the blockchain cannot be deleted at will.
- the application can call the SDK to write transactions to the test channel, and can limit the transaction submission speed in the SDK when the application calls the SDK to write transactions to the test channel, preventing The test operation of the test channel interferes with the performance of the trading channel.
- step S3 Determine whether the test of the smart contract to be tested passes. If it passes, perform step S4. If it fails, return the smart contract to the developer to modify or select a new smart contract and then return to step S2. It's tested.
- step S4 After all users on the test channel jointly conduct a business test on the contract content, according to the test result, it is determined whether the test of the smart contract to be tested passes, if the test passes, step S4 is executed, and if the test fails, the smart contract is transferred After modifying or selecting a new smart contract for the developer, return to step S2 to test it again.
- the blocks and / or transaction data generated by the smart contract running on the transaction channel are recorded on the transaction channel, and the user can query the blocks and / or transaction data on the transaction channel.
- the block and / or transaction data generated by the smart contract running on the transaction channel will be recorded on the transaction channel, and the block and / or transaction data will be queried and displayed in the transaction channel, that is to say, the user can Channel query block and / or transaction data.
- the data of the transaction channel and the test channel will have the characteristics that the data on the blockchain cannot be tampered with. And store the test data and transaction data separately, so that the two sets of data do not interfere with each other, effectively improve the operation and query efficiency of the underlying network of the blockchain, and further improve the stability.
- the smart contract to be tested includes a newly submitted smart contract and / or a historical version of the smart contract.
- the S3 specifically includes:
- step S4 is executed, and if the test fails, the smart contract is returned to the developer and then returned to step S2 after modification to retest it; and / or,
- step S4 is executed. If the test fails, a new smart contract is selected and the process returns to step S2 to test it again.
- the smart contract to be tested includes a newly submitted smart contract and / or a historical version of the smart contract. Regardless of whether it is a newly submitted smart contract or a historical version of a smart contract, if the test passes, step S4 is performed. However, if the two fail the test, the subsequent operations will be slightly different. The details are as follows: if the newly submitted smart contract test fails, the smart contract is returned to the developer and then modified to return to step S2 to re-test it; and if the smart contract test of the historical version fails, the new smart contract is selected Return to step S2 and test it again.
- users in the blockchain can choose to use the new smart contract submitted by the developer or use it on the current transaction channel
- the historical version of the smart contract is deployed on the test channel, and all users of the test channel conduct business tests on the contract content of the test channel. If the test fails, the newly submitted smart contract can be transferred to the contract developer for modification and then submitted and tested. The historical version of the smart contract cannot be modified, and only the new smart contract can be selected for redeployment into the test channel
- the test is conducted, and the last officially deployed contract is still executed in the transaction channel. If the test passes, all users in the channel agree on the content of the smart contract and get feedback on the deployment of the agreement, then officially deploy the updated contract to the transaction Used on the channel.
- Fig. 2 is a schematic structural diagram of a blockchain smart contract debugging and issuance system according to an exemplary embodiment. Referring to Fig. 2, the system includes at least:
- a new module is provided for users to create a trading channel, and a test channel is automatically created when the user creates a trading channel, where the test channel corresponds to the trading channel.
- the registration module is used to provide users with access to or exit from the trading channel, and to synchronously add or exit users to the test channel when the user joins or exits the trading channel.
- the test module is used to deploy the smart contract to be tested on the test channel, and all users on the test channel jointly perform business tests on the contract content.
- the content of the smart contract only needs to be guaranteed by the participants of the test channel (these parties are also participants of the transaction channel) during the test, and does not need to be checked every time. Consensus certification of smart contract content is carried out before deployment testing, which reduces the workload of each participant and shortens the operation cycle of updating contracts.
- the judgment module is used to judge whether the test of the smart contract to be tested passes. If it passes, the smart contract to be tested is sent to the release module. If it fails, the smart contract is returned to the developer for modification or Select a new smart contract and send it to the test module to test it again.
- the smart contracts to be tested include newly submitted smart contracts and / or historical versions of smart contracts. If the test fails, the newly submitted smart contract can be transferred to the contract developer for modification and then submitted and tested. The historical version of the smart contract can no longer be modified, and only a new smart contract can be selected for redeployment into the test channel test.
- the release module is used for all users on the test channel to reach a consensus on the content of the smart contract, and after obtaining feedback that the deployment is agreed, deploy the smart contract on the transaction channel.
- system further includes:
- a first storage module for recording test data generated by the smart contract running on the test channel in the test channel
- the first query module is used for the user to query the test data in the test channel
- the deletion module is used for the user to delete the test data after obtaining the consensus of all users on the test channel;
- a second storage module configured to record the blocks and / or transaction data generated by the smart contract running on the transaction channel on the transaction channel;
- the second query module is used for the user to query the block and / or transaction data in the transaction channel.
- the data of the transaction channel and the test channel will have the characteristics that the data on the blockchain cannot be tampered with. And store the test data and transaction data separately, so that the two sets of data do not interfere with each other, effectively improve the operation and query efficiency of the underlying network of the blockchain, and further improve the stability.
- the method and system for debugging and issuing a blockchain smart contract provided by an embodiment of the present invention.
- the system automatically creates a test channel with the same participants for the transaction channel, which is used for testing before the contract is officially deployed.
- the content of the smart contract only needs to be guaranteed by the participants of the transaction channel during the test whether it is in line with its business. It is not necessary to conduct consensus certification of the contract content before each deployment test, reducing the workload of the participants and shortening the operation cycle of updating the contract;
- the method and system for debugging and issuing blockchain smart contracts provided by the embodiments of the present invention store test data and transaction data separately, and the two sets of data do not interfere with each other, which effectively improves the operation and query efficiency of the underlying network of the blockchain and improves stability. Sex
- the method and system for debugging and releasing blockchain smart contracts provided by the embodiments of the present invention introduces the process standardization and manageability in the software development project into the contract debugging and release of the blockchain channel to reduce the maintenance cost of the contract. Maximize the team's cooperation efficiency.
- the program may be stored in a computer-readable storage medium.
- the mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Claims (10)
- 一种区块链智能合约调试发布方法,其特征在于,所述方法包括如下步骤:A method for debugging and issuing a blockchain smart contract, characterized in that the method includes the following steps:S1:在创建交易通道的同时自动创建一条测试通道,且用户加入或退出所述交易通道时同步将用户加入或退出所述测试通道;S1: A test channel is automatically created at the same time when the trading channel is created, and when the user joins or exits the trading channel, the user is simultaneously added or exited from the test channel;S2:将待测试的智能合约部署到所述测试通道上,所述测试通道上所有用户共同对合约内容进行业务测试;S2: Deploy the smart contract to be tested on the test channel, and all users on the test channel jointly perform business tests on the contract content;S3:判断所述待测试的智能合约测试是否通过,若通过,则执行步骤S4,若不通过,则将所述智能合约返回给开发者修改或选择新的智能合约后返回步骤S2,重新对其进行测试;S3: Determine whether the test of the smart contract to be tested passes. If it passes, perform step S4. If it fails, return the smart contract to the developer to modify or select a new smart contract and then return to step S2. Test it;S4:所述测试通道上所有用户对所述智能合约的内容进行共识,得到同意部署的反馈后,将所述智能合约部署到所述交易通道上。S4: All users on the test channel agree on the content of the smart contract, and after obtaining feedback that the deployment is agreed, deploy the smart contract on the transaction channel.
- 根据权利要求1所述的区块链智能合约调试发布方法,其特征在于,所述待测试的智能合约包括新提交的智能合约和/或历史版本的智能合约。The method for debugging and issuing a blockchain smart contract according to claim 1, wherein the smart contract to be tested includes a newly submitted smart contract and / or a historical version of the smart contract.
- 根据权利要求2所述的区块链智能合约调试发布方法,其特征在于,所述S3具体包括:The method for debugging and issuing a blockchain smart contract according to claim 2, wherein the S3 specifically includes:若所述新提交的智能合约测试通过,则执行步骤S4,若测试不通过,则将所述智能合约返回给开发者修改后返回步骤S2,重新对其进行测试;和/或,If the newly submitted smart contract passes the test, step S4 is executed, and if the test fails, the smart contract is returned to the developer and then returned to step S2 after modification to retest it; and / or,若所述历史版本的智能合约测试通过,则执行步骤S4,若测试不通过,则选择新的智能合约返回步骤S2,重新对其进行测试。If the smart contract of the historical version passes the test, step S4 is executed. If the test fails, a new smart contract is selected and the process returns to step S2 to test it again.
- 根据权利要求1至3任意一项所述的区块链智能合约调试发布方法,其特征在于,所述步骤S2还包括:The method for debugging and issuing a blockchain smart contract according to any one of claims 1 to 3, wherein the step S2 further comprises:将所述智能合约在所述测试通道上运行生成的测试数据记录在所述测试通道上,用户可在所述测试通道查询所述测试数据。The test data generated by running the smart contract on the test channel is recorded on the test channel, and the user can query the test data on the test channel.
- 根据权利要求4所述的区块链智能合约调试发布方法,其特征在于,所 述步骤S2还包括:The method for debugging and issuing a blockchain smart contract according to claim 4, wherein the step S2 further comprises:用户在得到所述测试通道上所有用户的共识后,可将所述测试数据删除。After obtaining the consensus of all users on the test channel, the user may delete the test data.
- 根据权利要求1至3任意一项所述的区块链智能合约调试发布方法,其特征在于,所述步骤S4还包括:The method for debugging and issuing a blockchain smart contract according to any one of claims 1 to 3, wherein the step S4 further comprises:将所述智能合约在所述交易通道上运行生成的区块和/或交易数据记录在所述交易通道上,用户可在所述交易通道查询所述区块和/或交易数据。Record the blocks and / or transaction data generated by the smart contract running on the transaction channel on the transaction channel, and the user can query the block and / or transaction data on the transaction channel.
- 一种区块链智能合约调试发布系统,其特征在于,所述系统至少包括:A blockchain smart contract debugging and release system, characterized in that the system includes at least:新建模块,用于提供给用户创建交易通道,且在创建交易通道的同时自动创建一条测试通道;A new module is provided for users to create a trading channel, and a test channel is automatically created when the trading channel is created;注册模块,用于提供给用户加入或退出所述交易通道,且在用户加入或退出所述交易通道时同步将用户加入或退出所述测试通道;The registration module is used to provide users to join or exit the trading channel, and when the user joins or exits the trading channel, the user is added or exited from the test channel synchronously;测试模块,用于将待测试的智能合约部署到所述测试通道上,所述测试通道上所有用户共同对合约内容进行业务测试;A test module, which is used to deploy the smart contract to be tested on the test channel, and all users on the test channel jointly perform business tests on the contract content;判断模块,用于判断所述待测试的智能合约测试是否通过,若通过,则将所述待测试的智能合约发送至发布模块,若不通过,则将所述智能合约返回给开发者修改或选择新的智能合约后发送至测试模块,重新对其进行测试;The judgment module is used to judge whether the test of the smart contract to be tested passes. If it passes, the smart contract to be tested is sent to the release module. Select a new smart contract and send it to the test module to test it again;发布模块,用于在所述测试通道上所有用户对所述智能合约的内容进行共识,得到同意部署的反馈后,将所述智能合约部署到所述交易通道上。The release module is used for all users on the test channel to reach a consensus on the content of the smart contract, and after obtaining feedback that the deployment is agreed, deploy the smart contract on the transaction channel.
- 根据权利要求7所述的区块链智能合约调试发布系统,其特征在于,所述系统还包括:The blockchain smart contract debugging and release system according to claim 7, wherein the system further comprises:第一存储模块,用于将所述智能合约在所述测试通道上运行生成的测试数据记录在所述测试通道;A first storage module for recording test data generated by the smart contract running on the test channel in the test channel;第一查询模块,用于用户在所述测试通道查询所述测试数据。The first query module is used for the user to query the test data in the test channel.
- 根据权利要求8所述的区块链智能合约调试发布系统,其特征在于,所述系统还包括:The blockchain smart contract debugging and release system according to claim 8, wherein the system further comprises:删除模块,用于用户在得到所述测试通道上所有用户的共识后,将所述测 试数据删除。The deletion module is used for the user to delete the test data after obtaining the consensus of all users on the test channel.
- 根据权利要求7或8所述的区块链智能合约调试发布系统,其特征在于,所述系统还包括:The blockchain smart contract debugging and release system according to claim 7 or 8, wherein the system further comprises:第二存储模块,用于将所述智能合约在所述交易通道上运行生成的区块和/或交易数据记录在所述交易通道上;A second storage module, configured to record the blocks and / or transaction data generated by the smart contract running on the transaction channel on the transaction channel;第二查询模块,用于用户在所述交易通道查询所述区块和/或交易数据。The second query module is used for the user to query the block and / or transaction data in the transaction channel.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3161753A CA3161753A1 (en) | 2018-11-19 | 2019-09-16 | Blockchain-smart-contract debugging and releasing method and system thereof |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811381098.4 | 2018-11-19 | ||
CN201811381098.4A CN109670951B (en) | 2018-11-19 | 2018-11-19 | Block chain intelligent contract debugging and publishing method and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020103545A1 true WO2020103545A1 (en) | 2020-05-28 |
Family
ID=66141813
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/106021 WO2020103545A1 (en) | 2018-11-19 | 2019-09-16 | Blockchain-based smart contract debugging and releasing method and system |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN109670951B (en) |
CA (1) | CA3161753A1 (en) |
WO (1) | WO2020103545A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111782551A (en) * | 2020-08-04 | 2020-10-16 | 腾讯科技(深圳)有限公司 | Test method and device for block chain item and computer equipment |
CN113672632A (en) * | 2021-08-06 | 2021-11-19 | 戈尔特西斯科技(济南)有限公司 | Quick query and call method for change records of historical data on chain based on intelligent contract |
CN117667676A (en) * | 2023-11-21 | 2024-03-08 | 上海金仕达卫宁软件科技有限公司 | AIGC-based block chain intelligent contract IDE verification test method and system |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109670951B (en) * | 2018-11-19 | 2021-03-26 | 南京苏宁软件技术有限公司 | Block chain intelligent contract debugging and publishing method and system |
CN110290168B (en) * | 2019-05-08 | 2022-04-12 | 深圳壹账通智能科技有限公司 | Data transmission method, device, server and storage medium |
CN110347609B (en) * | 2019-07-18 | 2023-05-23 | 腾讯科技(深圳)有限公司 | Method and device for testing blockchain software |
CN110543419B (en) * | 2019-08-28 | 2021-09-03 | 杭州趣链科技有限公司 | Intelligent contract code vulnerability detection method based on deep learning technology |
CN111290958B (en) * | 2020-02-20 | 2023-05-30 | 联动优势科技有限公司 | Method and device for debugging intelligent contract |
CN111459504B (en) * | 2020-03-30 | 2023-07-04 | 百度国际科技(深圳)有限公司 | Intelligent contract processing method, device, equipment and storage medium |
CN111723102A (en) * | 2020-08-21 | 2020-09-29 | 支付宝(杭州)信息技术有限公司 | Intelligent contract updating method and device |
CN111984271B (en) * | 2020-08-27 | 2023-11-03 | 京东科技信息技术有限公司 | Block chain application program processing method and device and block chain application system |
CN112433939B (en) * | 2020-11-19 | 2024-08-13 | 腾讯科技(深圳)有限公司 | Intelligent contract testing method and device |
CN113961202B (en) * | 2021-12-21 | 2022-02-22 | 北京中科金财科技股份有限公司 | Method and system for automatically debugging intelligent contract |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9934138B1 (en) * | 2016-12-07 | 2018-04-03 | International Business Machines Corporation | Application testing on a blockchain |
CN107943691A (en) * | 2017-11-17 | 2018-04-20 | 深圳圣马歌科技有限公司 | A kind of method and device for the functional test page for automatically generating intelligent contract |
CN108073513A (en) * | 2017-04-21 | 2018-05-25 | 富士通株式会社 | The apparatus and method tested the intelligent contract based on block chain |
CN108763058A (en) * | 2018-04-24 | 2018-11-06 | 苏州同济区块链研究院有限公司 | A kind of block chain evaluation system |
CN108776890A (en) * | 2018-06-04 | 2018-11-09 | 青岛大学 | A kind of believable intelligent paying out wages method and system based on block chain |
CN109670951A (en) * | 2018-11-19 | 2019-04-23 | 苏宁易购集团股份有限公司 | A kind of block chain intelligence contract debugging dissemination method and system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108304307B (en) * | 2018-01-24 | 2022-03-04 | 深圳圣马歌科技有限公司 | Performance detection method of intelligent contract on block chain |
CN108446947B (en) * | 2018-02-07 | 2021-05-18 | 平安科技(深圳)有限公司 | Real estate transaction method and device |
CN108628745A (en) * | 2018-05-03 | 2018-10-09 | 深圳市牛鼎丰科技有限公司 | Track record system, method, computer equipment and the storage medium of application program |
-
2018
- 2018-11-19 CN CN201811381098.4A patent/CN109670951B/en active Active
-
2019
- 2019-09-16 CA CA3161753A patent/CA3161753A1/en active Pending
- 2019-09-16 WO PCT/CN2019/106021 patent/WO2020103545A1/en active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9934138B1 (en) * | 2016-12-07 | 2018-04-03 | International Business Machines Corporation | Application testing on a blockchain |
CN108073513A (en) * | 2017-04-21 | 2018-05-25 | 富士通株式会社 | The apparatus and method tested the intelligent contract based on block chain |
CN107943691A (en) * | 2017-11-17 | 2018-04-20 | 深圳圣马歌科技有限公司 | A kind of method and device for the functional test page for automatically generating intelligent contract |
CN108763058A (en) * | 2018-04-24 | 2018-11-06 | 苏州同济区块链研究院有限公司 | A kind of block chain evaluation system |
CN108776890A (en) * | 2018-06-04 | 2018-11-09 | 青岛大学 | A kind of believable intelligent paying out wages method and system based on block chain |
CN109670951A (en) * | 2018-11-19 | 2019-04-23 | 苏宁易购集团股份有限公司 | A kind of block chain intelligence contract debugging dissemination method and system |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111782551A (en) * | 2020-08-04 | 2020-10-16 | 腾讯科技(深圳)有限公司 | Test method and device for block chain item and computer equipment |
CN111782551B (en) * | 2020-08-04 | 2021-07-27 | 腾讯科技(深圳)有限公司 | Test method and device for block chain item and computer equipment |
CN113672632A (en) * | 2021-08-06 | 2021-11-19 | 戈尔特西斯科技(济南)有限公司 | Quick query and call method for change records of historical data on chain based on intelligent contract |
CN117667676A (en) * | 2023-11-21 | 2024-03-08 | 上海金仕达卫宁软件科技有限公司 | AIGC-based block chain intelligent contract IDE verification test method and system |
Also Published As
Publication number | Publication date |
---|---|
CN109670951A (en) | 2019-04-23 |
CA3161753A1 (en) | 2020-05-28 |
CN109670951B (en) | 2021-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020103545A1 (en) | Blockchain-based smart contract debugging and releasing method and system | |
EP3504626B1 (en) | Multi-layer test suite generation | |
Molyneaux | The art of application performance testing: from strategy to tools | |
US8356056B2 (en) | Functional extensions for business objects | |
US8635056B2 (en) | System and method for system integration test (SIT) planning | |
US9747194B2 (en) | Systems and methods to maintain consistency between software specification and code | |
WO2019037203A1 (en) | Application program performance testing method, device, computer equipment, and storage medium | |
US20220058115A1 (en) | System and Method for Automated Application Testing | |
JP2010506294A (en) | Method and system for enabling access to development applications via a multi-tenant on-demand database service | |
CN108845954A (en) | Method for testing pressure, system and storage medium | |
WO2019104916A1 (en) | Development role creation method, device and equipment for test case, and storage medium | |
Espadas et al. | Application development over software-as-a-service platforms | |
CN110659018A (en) | Flow engine implementation method and device | |
CN106600226B (en) | Method and device for optimizing process management system | |
Sebu et al. | Applied process mining in software development | |
CN111897738B (en) | Automatic testing method and device based on atomic service | |
Oliveira Junior et al. | SMartySPEM: a SPEM-based approach for variability management in software process lines | |
US11086696B2 (en) | Parallel cloned workflow execution | |
CN111782207A (en) | Method, device and equipment for generating task stream code and storage medium | |
US11232019B1 (en) | Machine learning based test coverage in a production environment | |
CN114756293A (en) | Service processing method, device, computer equipment and storage medium | |
WO2023038716A1 (en) | Source code editing combining edit and continue with hot reload | |
US9990274B2 (en) | Testing integrated business systems | |
CN114936152A (en) | Application testing method and device | |
CN108563578A (en) | SDK compatibility detection method, device, equipment and readable storage medium |
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: 19886102 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19886102 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3161753 Country of ref document: CA |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19886102 Country of ref document: EP Kind code of ref document: A1 |
|
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 1205 DATED 19/01/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19886102 Country of ref document: EP Kind code of ref document: A1 |