Add how to test IPFS companion.
Antonio Navarro Perez committed
Aug 29, 2022 at 18:36 UTC
7c0dde45e97af4473842d95c1840ded1810ad43c
1 file changed
+6
-1
docs/RELEASE_ISSUE_TEMPLATE.md
+6
-1
@@ -81,7 +81,12 @@ Checklist:
81
- [ ] Ensure the RC is published to [the NPM package](https://www.npmjs.com/package/go-ipfs?activeTab=versions) ([happens automatically, just wait for CI](https://github.com/ipfs/npm-go-ipfs/actions))
82
- [ ] Upgrade to the RC in [ipfs-desktop](https://github.com/ipfs-shipyard/ipfs-desktop) and push to a branch ([example](https://github.com/ipfs/ipfs-desktop/pull/1826/commits/b0a23db31ce942b46d95965ee6fe770fb24d6bde)), and open a draft PR to track through the final release ([example](https://github.com/ipfs/ipfs-desktop/pull/1826))
83
- [ ] Ensure CI tests pass, repeat for new RCs
84
- - [ ] [IPFS Companion](https://github.com/ipfs-shipyard/ipfs-companion) - @lidel
84
+ - [ ] [IPFS Companion](https://github.com/ipfs-shipyard/ipfs-companion)
85
+ - Start kubo daemon of the version to release.
86
+ - Start a fresh chromium or chrome instance using `chromium --user-data-dir=$(mktemp -d)`
87
+ - Start a fresh firefox instance using `firefox --profile $(mktemp -d)`
88
+ - Install IPFS companion for the specific shop.
89
+ - Check that the comunication between Kubo daemon and IPFS companion is working properly checking if the number of connected peers changes.
90
- [ ] **Stage 2 - Community Prod Testing**
91
- [ ] Documentation
92
- [ ] Ensure that [CHANGELOG.md](https://github.com/ipfs/go-ipfs/tree/master/CHANGELOG.md) is up to date