Milestones

List view

• Production Releases

  Move bashellite out of beta status and begin doing formal releases. This will involve working out bugs, and making the enhancements necessary to allow for testing/development of non-production repository filters and configs, as well as eliminating any outstanding bug reports once unit testing and integration testing are in-place.

  No due date

  •4/5 issues closed
  80% complete1 open4 closed

• Automated Integration Testing

  Create a CI/CD pipeline to provision an automated test suite (using oneTimeSetUp function in shunit2) on a CI/CD platform (i.e. Travis, Jenkins, etc). Then use git hooks to automate some checks before merging changes to various provider functions. Test the functionality of the main function using a dummy "debug" or "testing" provider that just echos the inputs it receives. From there, use this same mechanism to automate the testing of real providers. Write a CONTRIBUTING.md that outlines the structure of the shunit2 required to fully test providers.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• Full Code Coverage

  Obtain as close as reasonably possible to 100% code coverage for functions in bashellite-libs.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed