-
Notifications
You must be signed in to change notification settings - Fork 7
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
Docker based Integration Tests #22
Comments
At the end of this video @shykes briefly describes idea of properly usage Docker for faking remote services (on example of Twitter API). Also the talk is very useful for understanding of Docker basics. |
…ration Tests * gdgomsk/devfest-app-tests-fakeserver:base - Based on Ubuntu 14.04, install binary dependencies and exposes 8081 port; * gdgomsk/devfest-app-tests-fakeserver:v1 - Use lighttpd to server static files. Setup lighttpd config, as well as json manifest and major dependend files. Manifest.json points to tests_data_v1.json, which contain fake data, which are pretty for usage and checking during integration tests;
…ration Tests * gdgomsk/devfest-app-tests-fakeserver:base - Based on Ubuntu 14.04, install binary dependencies and exposes 8081 port; * gdgomsk/devfest-app-tests-fakeserver:v1 - Use lighttpd to server static files. Setup lighttpd config, as well as json manifest and major dependend files. Manifest.json points to tests_data_v1.json, which contain fake data, which are pretty for usage and checking during integration tests;
Spent about 12 hours by learning Docker and playing with it. As I can see it's brilliant and effective solution for our case! I already made image for run Fake Test Server, that's serving static files around manifest.json. Steps to do:
|
…ration Tests * gdgomsk/devfest-app-tests-fakeserver:base - Based on Ubuntu 14.04, install binary dependencies and exposes 8081 port; * gdgomsk/devfest-app-tests-fakeserver:v1 - Use lighttpd to server static files. Setup lighttpd config, as well as json manifest and major dependend files. Manifest.json points to tests_data_v1.json, which contain fake data, which are pretty for usage and checking during integration tests;
Implement several docker containers: one for Android app itself, second for emulation of remote manifest storage and static files providers, third for GCM, and so on.
Test environment should has zero dependency from external world for all features under test.
Use Espresso and/or UiAutomation for automation of user actions.
The text was updated successfully, but these errors were encountered: