reject changes based upon feedback from reviewers voting +2 or -2, respectively. Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted building Hyperledger Fabric for unit testing instructions. See Unit test coverage reports [https://jenkins.hyperledger.org/view/fabric/job/fabric-merge- x86_64/] To see coverage for a package and all sub-packages

reject changes based upon feedback from reviewers voting +2 or -2, respectively. Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted building Hyperledger Fabric for unit testing instructions. See Unit test coverage reports [https://jenkins.hyperledger.org/view/fabric/job/fabric-merge- x86_64/] To see coverage for a package and all sub-packages

reject changes based upon feedback from reviewers voting +2 or -2, respectively. Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted

reject changes based upon feedback from reviewers voting +2 or -2, respectively. • Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted

reject changes based upon feedback from reviewers voting +2 or -2, respectively. Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted

reject changes based upon feedback from reviewers voting +2 or -2, respectively. • Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted

reject changes based upon feedback from reviewers voting +2 or -2, respectively. • Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted

reject changes based upon feedback from reviewers voting +2 or -2, respectively. • Builders: (e.g. Jenkins) May use the build automation infrastructure to verify the change. Maintainers should be familiar of the code and limit possible regressions, we use a Continuous Integration (CI) process based on Jenkins which triggers a build on several platforms and runs tests against every change request being submitted

DK以及智能 合约测试案例可有效覆盖测试案例所执行的路径和范围。自动化的回归测试有助于快速检测并发现 问题，节省大量重复人力，保证合约经历系列修改和测试后，不偏离主干功能。同样，开发者可使 用Jenkins、Travis等工具进行构建和测试。除了执行个别自动化测试无法执行的案例外，人工测试更多 地是确认之前修改的代码是否符合预期，智能合约的运行是否符合当初设计。此外，在合约最终发布 前，人工测试还起到审核检查作用，故而一定要认真对待。 和部署好的区块链打包成一个包裹，类似于将一个 大房子整理成一辆房车。通过这种方式，用户无需关注环境配置问题，可减少部署时间——不用一分 钟就能获得镜像，方便开发者快速上手使用，便于自动化运维。你也可以尝试将这个服务和 JenKins 结 合，进一步优化运维过程。“Python 区块链盒子”可以当成 Python 区块链开发的工作台，一个现拆现用的 工具箱，而且可以保证开发环境的整洁，最重要的是它很轻，就像 Minecraft

DK以及智能 合约测试案例可有效覆盖测试案例所执行的路径和范围。自动化的回归测试有助于快速检测并发现 问题，节省大量重复人力，保证合约经历系列修改和测试后，不偏离主干功能。同样，开发者可使 用Jenkins、Travis等工具进行构建和测试。除了执行个别自动化测试无法执行的案例外，人工测试更多 地是确认之前修改的代码是否符合预期，智能合约的运行是否符合当初设计。此外，在合约最终发布 前，人工测试还起到审核检查作用，故而一定要认真对待。 和部署好的区块链打包成一个包裹，类似于将一个 大房子整理成一辆房车。通过这种方式，用户无需关注环境配置问题，可减少部署时间——不用一分 钟就能获得镜像，方便开发者快速上手使用，便于自动化运维。你也可以尝试将这个服务和 JenKins 结 合，进一步优化运维过程。“Python 区块链盒子”可以当成 Python 区块链开发的工作台，一个现拆现用的 工具箱，而且可以保证开发环境的整洁，最重要的是它很轻，就像 Minecraft