| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
It has not been used (except for one test). By now, espresso is
recommended over robotium in most cases due to the automatic
synchronization.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
For Espresso UI tests it is required to use a newer Google
instrumentation test runner, but that one doesn't support junit reports.
Therefore let's have our own derived test runner, which supports junit
reports.
This change will break existing Eclipse launch configurations for unit
tests. You have to select the new junit runner in the launch config
afterwards.
|
| |
|
|
|
|
|
| |
AssertJ is a fork of FEST. Both are signature compatible in the core
assertions, so we can still switch to FEST should we see a need for it.
If you have trouble compiling or running tests after pulling this
change, please shout out loud.
|
| |
|
|
|
| |
Also, reenable the test. It will be disabled again if it does not work
reliably on the continuous integration server.
|
| | |
|
| | |
|
| | |
|
| |
|
