So when you say: >In general, you test the result of a method by creating the >object with all the dependencies set to known values (the fixture), >preferably by injection. Then you call the method with pre-determined >values. Based on the dependencies as the values, you should be able to >predict the answer. You compare this prediction to the object's actual >answer with an assert().
How do you go about creating an object with all the dependencies set to known values by injection? So if i am in the LoginActivity and i want to enter fields into EditText views such as a username and password and then click a button to login which starts another activity that makes a REST call with the appropriate login signature and the second activity parses the XML response which is returned back to the LoginActivity, is there no way of testing that whole process with ActivityInstrumentationTestCase2 or ActivityUnitTestCase? Also you say that: >Both ActivityUnitTestCase and ActivityInstrumentationTestCase2 are (IMHO) "pseudo-unit" test >cases. Then what types of tests are appropriate in each class? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
