[kj4ezj]

Change Description

From EPE-486 and AUTO-311, I was asked to add testing checkboxes to the pull request template for EOSIO:

## Testing Changes
- [ ] New Tests
- [ ] Existing Tests
- [ ] Test Framework
- [ ] CI System
- [ ] Other

This benefits Blockchain by encouraging developers to consider test cases while writing pull requests and submitting new contributions. This benefits Automation by providing a convenient programmatic way to detect, track, notify, or act upon changes to the CI system or test framework(s), like we do with the other check boxes. More broadly, we all stand to benefit from a culture more focused on testing.

The new template has been manually pasted into this pull request so you can see what it looks like, but GitHub will not present the new template to users until it is merged to this repository's default branch:

You must create templates on the repository's default branch. Templates created in other branches are not available for collaborators to use.

See the Pull request templates heading on the About issue and pull request templates page of GitHub's documentation for more information.

See Also

• Pull Request 9662 -- eos:develop
• Pull Request 9663 -- eos:blockvault
• Pull Request 9664 -- eos:develop-boxed
• Pull Request 9665 -- eos:release/2.0.x
• Pull Request 9666 -- eos:release/1.8.x

Change Type

Select ONE:

• Documentation

• Stability bug fix

• Other

Pull request template.

• Other - special case

Testing Changes

Select ANY that apply:

• New Tests

• Existing Tests

• Test Framework

• CI System

• Other

None.

Consensus Changes

• Consensus Changes

None.

API Changes

• API Changes

None.

Documentation Additions

• Documentation Additions

None.