Testing: Ye Olde Way — ActivityInstrumentationTestCase2extends Activity> — Name of method to be tested starts with test — If something is temporarily broken, either delete it or comment it out. — Testing different data requires a separate test calling a private helper.
Testing: Ye JUnit4 Way — Uses annotations instead of naming conventions — Allows tests to be marked as ignored — Runner has subclasses allowing all sorts of fancy things — Allows you to have tests skipped based on an assumption*
Testing: Ye JUnit4 Way — Uses annotations instead of naming conventions — Allows tests to be marked as ignored — Runner has subclasses allowing all sorts of fancy things — Allows you to have tests skipped based on an assumption* * - in theory
JUnit4 Benefits — Tests don't reference an activity unless they need to — Name things in a way that makes sense to YOU — Run the same test many times with different params
JUnit4 Drawbacks — Assume handling is not presently working. — FlakyTest does not work with JUnit4 tests. — You have to static import a lot more stuff.