Hacker News new | past | comments | ask | show | jobs | submit login
Show HN: Set up a continuous testing pipeline with Node.js
6 points by creichert on March 24, 2017 | hide | past | favorite | 5 comments
Hey HN,

My brother and I recently wrote a new guide on creating a continuous integration, delivery, and testing pipeline for a Node.js app.

Full post: https://assertible.com/blog/set-up-continuous-testing-with-n...

Example repo: https://github.com/assertible/nodejs-example

The tutorial goes over the different components of a complete CI pipeline:

- Push code to GitHub, build and run unit tests on CircleCI

- Deploy new app version to Heroku

- Post-deployment tests with Assertible

The whole workflow is surprisingly easy to set up. We now run automated testing on all staging and production environments immediately after deployment. This has helped us save a ton of time manually QA testing.

I'd love to hear some feedback on this approach and how other teams manage their CI setups.

What does your CI pipeline look like? Anything you would add or change about this workflow?




Author here - I'm planning a couple new guides with other CI/CD services (like Codeship). Any thoughts on what pipelines/workflows could use a good example?


I posted a question on dev.to a while back asking for general CI/CD preferences as well - here are some good options to peruse - https://dev.to/kellyjandrews/what-tools-do-you-currently-use...


Extremely good list and feedback. That will help a lot, thanks!


Disclaimer - Developer Advocate for Codeship To be honest,the example you have here on Codeship would be much cleaner to set up, and 100% less yaml.


It's in the works, and will be the greatest workflow of all time ;)

In all seriousness though, I'm loving Codeship and it's concept of "pipelines". Really looking forward to working with it more.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: