Story

As a developer who uses CMI I want to be able to export CMI and expect it to not require reexports based on heartbeat of diagnostics being updated.

Implementation Details

[] Review all the CMI Varibles and move items that are in CMI to state where appropriate.
[] Ensure that the module can reinitialize the state on cron without issues or CMI headaches

User story

As a developer I want my user to leverage dependency injection so that it's testable, and following drupal best practices.

Implementation Details

[] Run phpcs with drupal-practice standards
[] Ensure that all the dependency injection violations are fixed.
[] see if there are opportunities for better utilizing dependency injection

Story

As a developer I want to store the minimally necessary set of CMI for the Acquia connector module.

Context

Currently there is an insane number of variables being stored in CMI. Many of them may not be necessary.

Implementation details

[] Review the variables
[] Evaluate which ones are actually needed by Acquia/Insights
[] Kill the ones that don't matter

User Story

As a user I want to ensure that the module adheres to drupal coding standards.

Implementation Details

[] Add PHPCS to the travis build.
[] Set it up to scan the files changed in the PR and run the scan only on the changed files. Why only the changed files? There are too many errors to fix in a single PR that require too much code refactor.

User Story

As a user I want a modern travis-ci build.

Implementation Details

[] Take the lightning travis builds as an example and apply it here
[] Confirm that simpletest, phpunit, and behat tests are executed

Update and clean up the test cases so that they actually work and test all different cases and codepath.

Check the code coverage and ensure that PHPUnit tests cover a majority of the code

User Story

As an engineer I want the module to adhere to community coding standards

Implementation Details

[] Run PHPCBF on codebase