Skip to content

Instantly share code, notes, and snippets.

@barretts

barretts/blue-dev-cycle.md

Last active September 26, 2018 17:07
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save barretts/a6cf495deb322ce9c188eb03f93ae909 to your computer and use it in GitHub Desktop.
Save barretts/a6cf495deb322ce9c188eb03f93ae909 to your computer and use it in GitHub Desktop.
Download ZIP
Blue Dev cycle
Raw
blue-dev-cycle.md

Grab a new issue (ex: #2468) from HuBoard's Next Actions column self assign it and move it to the Development column

Make branch based of the issue number proceeded by x-: git checkout -b x-2468

Finish the issue

Run unit tests: bundle exec rake test:unit

Run interaction tests from Visual Studio

Run integration tests:

  • Run integration tests locally (optional): bundle exec rake test:integration

  • Push branch to GitHub with the f- prefix for build automation: git push origin x-2468:f-2468

  • Check https://build.dovetailtesting.com and the blue-all section to verify everything passed

  • If there were errors fix and test as required

Fix any broken tests

Write new unit, integration and interaction tests for the issue

Rerun unit, integration and interaction tests

Now that all the build is green move the issue(s) into the DevReview column on HuBoard

If the issue is a larger feature branch create a Pull Request on GitHub and reference all included issues

From the #blue channel on Slack request a dev review of your issue branch

Fix any feedback

Move the issue(s) into the Ready to Ship

Push changes to master and delete all the old branches

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