What testing do you mean? - unit testing? - integration tests? - smoke tests? - functional tess?
Let's try to search for GIN and MVP ... thats the patterns and principles for better application testability. It is recommended to use command pattern and dispatch service, for easier testing of code which uses RPC services - this allows you to easy mocks the service implementation. Peter On 13. Júl, 14:10 h., mmoossen <[email protected]> wrote: > hi, anabillo! > > for me the best "design for testability" is to start writing the test > cases (at least the unit test cases) before writing the actual code! > > HTH > Michael > > PS: and what has that to do with GWT? > > On Jul 13, 1:17 am, anabillo <[email protected]> wrote: > > > Hello Guys , > > > I start writing a blog about software testing and I really need a hand > > in that, I will write a different chapters of testing the software , I > > will start with the concept of "design for testability" which means > > how to build a software that can be tested in the future , if any one > > know where I can find more resources about this topic or would like > > to participate , please reply to this message even with links, > > thoughts, ideas or any thing that you see useful. > > > Thanks for the efforts -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
