To run sharness locally, during dev, run this from the test/sharness dir:

TEST_NO_FUSE=1 GOIPFSTEST_SKIP_LOCAL_DEVTREE_DEPS_CHECK=1 make

We need more sharness tests here. In particular we should

1. Like with the previous PR, have a function that will let us test that Ed25519 + RSA keys both work (it's not quite in line with this PR but we need to do it anyway
2. Make sure that we can publish using a b58mh as well as a b36cid. The results can all come out as Publish to ${b36cidKey} though.

I've added a test for (2). For (1), it seems one good strategy is to wrap all tests in a function parameterized by ed25519/rsa and use this to initialize the self ID, because most tests are based on the self id. Would you prefer a different approach?

(1), it seems one good strategy is to wrap all tests in a function parameterized by ed25519/rsa and use this to initialize the self ID, because most tests are based on the self id. Would you prefer a different approach?

We need to test publishing with the --key flag anyway. So maybe something like this:

• Have a function that tests with ed25519, rsa, and self
• Test that publishing with no --key flag means we published with self
• Test that we can publish with --key=peerIDRepresentationOfKey, or --key=friendlyName

(1), it seems one good strategy is to wrap all tests in a function parameterized by ed25519/rsa and use this to initialize the self ID, because most tests are based on the self id. Would you prefer a different approach?

We need to test publishing with the --key flag anyway. So maybe something like this:

• Have a function that tests with ed25519, rsa, and self
• Test that publishing with no --key flag means we published with self
• Test that we can publish with --key=peerIDRepresentationOfKey, or --key=friendlyName

I think now all these cases are covered.