On 9 Dez., 14:20, Mark Murphy <[email protected]> wrote: > On Thu, Dec 9, 2010 at 3:50 AM, Ecthelion <[email protected]> wrote: > > Brilliant. But that essentially means that I cannot be 100% sure that > > my changes would not cause undesired side effects. > > You can't be 100% sure of anything with a third-party library. > > How do you ensure that you are passing the proper parameters to > methods? Testing. > > How do you ensure that you are covering all RuntimeExceptions the > library might throw? Testing. > > How do you ensure that the third-party library handles edge cases > (e.g., WiFi failing over to 3G)? Testing. > > And so on.
The obvious difference is that - at least we should hope so when using other libraries - testing for existing string resources (and other stuff too) in the library has already been done by the company/person creating the library, so that if I do not change code of the library I don't have additional testing effort for checking whether the library works. This necessity only evolves because of the mentioned change in the resource compiler forcing me to modify library resources. -- 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
