beautiful. Sara J Chipps 862.201.3065
CTO http://levoleague.com #levolove Other projects: http://SaraJChipps.com <http://sarajchipps.com/> http://GirlDevelopIt.com <http://girldevelopit.com/> http://ElizabethandClarke.com <http://elizabethandclarke.com/> --------------------------------------------------- No trees were killed in sending this message but a large number of electrons were terribly inconvenienced. On Tue, Dec 11, 2012 at 8:21 PM, Forrest L Norvell <[email protected]>wrote: > This is awesome, James. I know you've been working on this for a while, > and I'm really impressed. Thanks for offering it to the community! > > F > > > On Tue, Dec 11, 2012 at 5:05 PM, substack <[email protected]> wrote: > >> There are a ton of modules on npm and github that aren't just for node.js >> but for browsers too. However, figuring out *which* browsers these modules >> work with can be tricky. It's often that case that some module used to work >> in browsers but has accidentally stopped working because the developer >> hadn't checked that their code still worked recently enough. If you use npm >> for frontend and backend modules like I do, this can be particularly >> frustrating. >> >> Announcing testling-ci (http://ci.testling.com) a service for running >> your browser tests on every commit. Just add a "testling" field to your >> package.json like this: >> https://github.com/substack/node-falafel/blob/master/package.json#L41-L50 >> then add a github webhook for "http://git.testling.com"; and your browser >> tests will be run on every commit in exactly the browsers you've specified! >> You get a badge you can put in your readme with the current browser test >> status like this one: >> https://github.com/substack/node-falafel#falafel >> and if you click the badge you go to the test status page: >> http://ci.testling.com/substack/node-falafel >> >> All your tests need to do is output TAP-formatted text output. Many test >> harnesses already support this format and the protocol is simple enough >> that you can just console.log() valid output yourself. I recommend using >> https://github.com/substack/tape to output TAP or I have a testling-ci >> example using mocha too: >> https://github.com/substack/mocha-testling-ci-example We'll support many >> more test harnesses later. >> >> Your browser tests can even use node-style require()s bundled with >> browserify so that you can use exactly the same tests for node and the >> browser. If your browser tests aren't written the node way you can still >> run them with the "scripts" field. >> >> This service is free for open source modules published to github. If you >> want to run this service on your private repos, contact pkrumins and I ( >> http://browserling.com/contact) and we can enroll you in our testling >> PROFESH edition beta. >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
