-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Including Hub Server for integration tests #13
Comments
Notes:We don't have to run our hub as a separate process -- we can |
We need to remember to give our install scripts executable permissions with |
Installing the hub server on travis results in a hang after database migrations:
I'm not sure why |
We need to run the hub server as a background process: This means that travis doesn't exit however as it waits for background processes to finish first... |
Caching our hub deps breaks git clone as you must clone into an empty directory. To get around this I'm copying the cached deps in and out of a temporary directory and runtime. E.g. to cache the dependencies at the end of the build process: - mkdir smart-home-auth-server-deps
- cp -R smart-home-auth-server/deps/* smart-home-auth-server-deps |
what |
The hub client process can't connect on travis, i'm not sure why as all ports etc should be the same.... |
Going to try and read our hub logs with |
Multi-container workflows seem to be supported on Circle Ci.... https://circleci.com/blog/setting-up-tricky-containers-in-circle-2-0-multi-image/ |
Worked around with dwyl/smart-home-auth-server#14 |
To be able to properly run integration tests against the
dwyl/smart-home-*
stack we should include the Hub server in our test environment so we can test against it.This has several benefits:
No need to mock a hub client. We can use our actual hub client and run tests to make sure this is functioning as expected. This avoids any errors with our Mock implementation and makes the tests less complex to maintain.
Test the internal API. By testing against our actual hub server, we have the added benefit of checking our internal websocket api still works and we haven't accidentally created any breaking changes.
Integration tests across the whole stack. We can make sure our entire stack functions as expected by running integration tests that encompass the whole stack.
TODO:
The text was updated successfully, but these errors were encountered: