-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add a file parser for parsing from the local file system. #22
Conversation
@andrzejchm I now added a |
395f852
to
55bb963
Compare
Tremendous bunch of work, I'll dig into that. |
@@ -145,6 +144,23 @@ RESTMockServer.enableLogging(RESTMockLogger) | |||
RESTMockServer.disableLogging() | |||
``` | |||
|
|||
## Unit Tests with Robolectric | |||
If you want to write unit tests (no emulator or device necessary), you can use [http://robolectric.org](Robolectric) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here it should be (Robolectric)[http://robolectric.org]
@andrzejchm Sure, I'll make the requested documentation changes & rebase the PR. |
When using Roboelectric (or other unit testing framework for Android that does not set up a "real" Android environment), it's necessary to retrieve files based on the local file system of the machine on which the tests are run, rather than the virtual file system expected by the Android operating system. This is due to the fact that, when running these types of tests, most of the Android system is really just a set of mocks. As such, without this file parser, the "assets", "res", and other system-level file system paths are not set up and linked correctly, as the system calls that would normally provide this information are mocked.
@andrzejchm I made the changes to the README you requested. |
thanks! merged |
When using Roboelectric (or other unit testing framework for Android that
does not set up a "real" Android environment), it's necessary to retrieve
files based on the local file system of the machine on which the tests are
run, rather than the virtual file system expected by the Android operating
system. This is due to the fact that, when running these types of tests,
most of the Android system is really just a set of mocks. As such, without
this file parser, the "assets", "res", and other system-level file system
paths are not set up and linked correctly, as the system calls that would
normally provide this information are mocked.