Smoke testing with npm modules

[indutny]

One of the main goals for this project is to be used in the node-gyp. This means, though, that we should make sure that the most of the existing binding.gyp files will work with gyp.js. Thus, "smoke testing" is needed badly.

cc @thealphanerd

[MylesBorins]

@indutny are you thinking that this module should be included in citgm? or did you have something else in mind?

[indutny]

@thealphanerd it may be a good idea to include it in cigtm eventually, indeed. However, I was thinking about doing the smoke tests for node.js addons. Added you to cc, because you have tons of experience with smoke testing 😉

[MylesBorins]

definitely interested in helping with this.

If you can come up with a list of requirements I can definitely start digging in.

Specifically outlining the manual process for make sure that the most of the existing binding.gyp files will work with gyp.js would help

[indutny]

@thealphanerd thank you!

What about something like this:

• Have a list of node.js addons that are known to work on linux/windows/osx/..., or at least know on which platform npm test passes
• Build these packages with patched node-gyp (See: shared_library support #2 (comment), WIP)
• Run npm test on each of them

[MylesBorins]

So citgm allows you to provide a custom lookup table, so we could easily make a lookup table of only native modules. Is there a flag or env var that can be passed to npm to use a specific gyp? If so I think this should be pretty painless to do with citgm, we may even be able to do it with the off the shelf citgm

[indutny]

@thealphanerd sounds lovely! I'll get back to you once we will get things moving with node-gyp. Thank you so much for your help!