Skip to content
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.

[WIP] fix: ipns tests using go daemon #360

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vasco-santos
Copy link
Contributor

In the context of having the ipns tests running on js-ipfs-api#841

@@ -125,7 +123,7 @@ module.exports = (createCommon, options) => {
ipfs.name.resolve(keyId, resolveOptions, (err, res) => {
expect(err).to.not.exist()
expect(res).to.exist()
expect(res.path).to.equal(`/ipfs/${value}`)
expect(res.path || res).to.equal(`/ipfs/${value}`) // TODO
Copy link
Contributor

@victorb victorb Aug 31, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems wrong, tests should test one thing and here is a conditional (res.path || res). Also the TODO seems to be missing a comment about what/why

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes! That will be changed 🙂

But for explaining the purpose, I am experiencing different responses when the daemon is online and offline. One has the path property, while the other does not have. I will keep this in WIP before solving this

@@ -83,12 +81,12 @@ module.exports = (createCommon, options) => {

done()
})
}, 1)
}, 10)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than having this is a timeout, we should have something similar to this: https://github.com/ipfs/interface-ipfs-core/blob/master/js/src/pubsub/utils.js#L5-L31

Where we execute the expectations once every 100 milliseconds until either it passes or we've tried 10 times. This will make the test less likely to fail on lower performance machines.

@alanshaw alanshaw changed the title WIP: fix: ipns tests using go daemon [WIP] fix: ipns tests using go daemon Sep 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants