Add automated testing with Travis-CI or similar

[gschneider-r7]

We should be able to run at least some automated testing with Travis-CI or similar service. This will require building out all of the tests.

We can also have automated testing against an actual Nexpose console internally. We could potentially publish pass/fail results of that to github.

This should enable fully automated testing of any pull requests in the future.

[erran]

I suggest that we have two levels of tests.

1. Using a web mocking tool such as vcr/vcr for integration tests.
   1. This provides the ability to store requests as fixtures and run the same tests on Travis for stable API versions.
   2. VCR has the ability to "re-run" tapes which can be used to perform the live requests on a internal system.
2. Unit tests which can use convential mocking with RSpec mocks.

@gschneider-r7 ping me about this as I'd be interested in working on this. I know in Austin it would help the Metasploit and ControlsInsight teams as we have dependencies on the Nexpose gem.

[erran]

/cc @lsanchez-r7

[gschneider-r7]

Your suggestion is pretty spot on with what I was thinking. 👍

[lsanchez-r7]

👍