Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests are out of sync with Node.js tests #177

Open
vmx opened this issue Jan 9, 2018 · 10 comments
Open

Tests are out of sync with Node.js tests #177

vmx opened this issue Jan 9, 2018 · 10 comments

Comments

@vmx
Copy link
Contributor

vmx commented Jan 9, 2018

When running ./bin/download-node-tests.js it's apparent that the tests are heavily out of sync with the Node tests.

I plan to go over them an resync things. I open this issue to prevent double work, so a "go for it" from the maintainers would be appreciated.

@ralphtheninja
Copy link

I'm not a maintainer, but I'll say "go for it" anyway 😀

vmx added a commit to vmx/buffer that referenced this issue Jan 21, 2018
This commit uses the `test-buffer-alloc.js` from upstream Node.js
as of 2018-01-20.

This is part of feross#177.
vmx added a commit to vmx/buffer that referenced this issue Jan 21, 2018
This commit uses the `test-buffer-alloc.js` from upstream Node.js
as of 2018-01-20.

This is part of feross#177.
@feross
Copy link
Owner

feross commented Feb 16, 2018

Merged @vmx's PR and the tests are closer to node's now, but there's still a lot of differences.

@feross
Copy link
Owner

feross commented Feb 16, 2018

I just spent like 3 hours merging in more changes from Node.js, but there's still more changes to be done... wow. Would appreciate help from other folks, if there's interest. @vmx, any interest?

I've started adding the new test files that were added. Once they're all added in, then we can delete test/node/test-buffer.js which has been removed from the original repo. But I don't want to remove it before the other files are merged in, otherwise we'll lose coverage in the meantime.

EDIT: Here's the changes I've made (committed to master already): e0adc7a...f5aae10

@vmx
Copy link
Contributor Author

vmx commented Feb 16, 2018

Thanks for the review @feross. I still have interest and would spend some time next week. I'll start from the top (alphabetically) and work on the differences. I'll push again in small increments to prevent double efforts.

@feross
Copy link
Owner

feross commented Feb 16, 2018

Great, looking forward to a PR next week, @vmx!

@feross
Copy link
Owner

feross commented Feb 16, 2018

Note to self: When all these tests and code changes are merged in, publish a new major version.

@superguineapig
Copy link

Hey all. It's been some time since this issue was opened and buffer was updated. Has the herd moved to another implementation/fork? Or is there still a roadmap for this one to be actively developed? Just curious.

@vmx
Copy link
Contributor Author

vmx commented Nov 27, 2018

@superguineapig When I was talking with @feross he said he's happy to see those fixes. So my currnet workflow is doing some of those fixes, waiting for a review (wow, it's been a long time for #190 being open) and merge and then doing some more whenever I find time.

@superguineapig
Copy link

Thanks for the info @vmx Glad to hear the project is still alive.

@feross
Copy link
Owner

feross commented Sep 5, 2019

I'm in grad school as of the past year, so I was off GitHub for a while. Still around and still plan to maintain this as good as ever. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants