Add details on how to test new features locally

[RohanVB]

Probably should be added to the README

[RohanVB]

Note this issue opened is prior to the addition of the testing environment and is subject to using the built-in testing architecture of atom.
The additional environment allows the use of mocks, along with easy to add test cases using setUp and tearDown with a cleaner output.

What this issue entails:

npm install, apm link -d, atom -d being used on the coala-atom directory to try it out in dev mode.

[ajomadlabs]

Can I take up this issue ? I am a beginner and want to really fix this up. Can I also get more details on this

[RohanVB]

Hi @ajomadlabs can you head on to the coala gitter channel and type in Hello world to get invited to the org (this is so I can assign you to the issue).
From there on, this issue involves adding testing instructions to this repo's readme.

[ajomadlabs]

@RohanVB Sure.

[ajomadlabs]

@RohanVB Can I know more about the testing instructions

[RohanVB]

@ajomadlabs It's mentioned in the first post of the issue, instructions on how'd you'd generally test a plugin within the atom environment after making changes.
ie. "first ensure npm install is done to have all the npm packages linked,...etc,."
similarly, apm link -d and what it does, atom -d and what it does.