Tests #6

Closed
rvagg opened this Issue Jan 21, 2013 · 9 comments

Comments

Projects
None yet
4 participants
Owner

rvagg commented Jan 21, 2013

Currently devoid of tests as they are all in LevelUP. Need to implement a new set just for LevelDOWN.

Contributor

dominictarr commented Jan 21, 2013

do you mind if we make it tap? then we can use it to test browser leveldown shims in ci.testling!

Owner

rvagg commented Jan 21, 2013

No. I don't mind tap (as in node-tap)

Owner

Raynos commented Jan 21, 2013

Try tape!

Owner

rvagg commented Jan 21, 2013

I have. I'm happy to use it on my simpler libs but would prefer tap for something more complex like this. Actually I'd prefer Buster but I understand the barriers that puts in place for the likes of you fellas.

Owner

Raynos commented Jan 21, 2013

Well you can require("tape") in the code. And use tap as the CLI.

Contributor

dominictarr commented Jan 21, 2013

how different are the buster/tap apis?

man, buster has too much documentation!

Just finding an example is kinda hard.

Owner

ralphtheninja commented Jan 21, 2013

Buster is 65M o.O ! That's just insane.

magnus@emachines|00:53|~/src/node-levelup/node_modules (master) $ du --max-depth=1 | sort -nr
67888 .
66372 ./buster
312 ./tar
276 ./fstream
268 ./bufferstream
176 ./mkfiletree
120 ./async
84 ./rimraf
56 ./delayed
48 ./errno
40 ./boganipsum
32 ./slow-stream
32 ./du
24 ./readfiletree
20 ./concat-stream
20 ./bindings
4 ./.bin

Owner

rvagg commented Jan 22, 2013

That's cause it targets browser testing too. The essentials for Node are small and we'll get a buster-node soon! /cc @cjno

Owner

ralphtheninja commented Jan 22, 2013

Sounds good :)

On 22 January 2013 01:05, Rod Vagg notifications@github.com wrote:

That's cause it targets browser testing too. The essentials for Node are
small and we'll get a buster-node soon! /cc @cjno


Reply to this email directly or view it on GitHubhttps://github.com/rvagg/node-leveldown/issues/6#issuecomment-12524333.

@rvagg rvagg closed this Mar 4, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment