moving all of core into toplevel, tests fail.
fix requiring core extensions - most tests pass

some message tests are failing for me right now.
move all dependencies into Gemfile

We used to keep them separated so one could require some engines without using the full webapp. We've never really supported this though and probably never will.
update documentation: included core in toplevel

now we only include some engines - we don't build the whole webapp based on them. Reflecting this in the documentation.
moving users: dependencies
moving users: app and test files
move users: config and lib
only load */test/factories from test/factories

prevent recursive loadign of test/factories.rb ** can be empty.
move certs into toplevel

cleaned up all the engine stuff that was never really used.
Afterwards there is not that much left that makes it into the toplevel.
bringing back srp js
make sure billing tests do not interfere with others

they are still broken though.
moving broken billing integration tests out of the way

They are currently using fake_braintree. I think this is not a good approach for integration tests. It's a fake - we should test against braintrees test api. However that requires getting an api key that we want to keep outside the repository. So these test can only run on travis if we manage to setup secret values in .travis.yml - which has been failing so far.

So for now i moved the broken billing integration tests to billing/test/broken to move on.
move engines into engines directory

Also renamed help to support so it's harder to confuse it with documentation
minor: our engines do not have a db directory
move include AssertResponses into test itself

it may not have been required before the RackTest support class.
doc: update list of engines
Merge pull request #146 from azul/refactor/engines

Refactor/engines
refactor nagios tests, remove parse
refactor reporting in webapp login nagios test
refactor: move nagios specifs to nagios_test

nagios_test.run takes a function and executes it.
If it returns nothing or 0 and OK nagios message is printed.
If it returns sth. else this will be printed a a warning
If it raises an exception that will result in a CRITICAL report.

This way we can keep the nagios things outside the test cases and just write simple functions that either return 0, a warnign or raise a meaningful exception