Comments on testing through the GUI
Joe Strazzere <strazzer@shore.net> writes:
"I agree! Again I think the key is for testing to get involved early, so that the inclusion of any "testability aids" is not too burdensome on the project as a whole.
I have often found that just re-ordering the development schedule can provide earlier testability (develop the "export" function before worrying about the Help file).
I'm not sure I would place too much emphasis on memory leak tools as alternative here. While extremely valuable tools, you cannot assume that they can take the place of testability aids built during the project. You have to get involved early, assess the testability, check what you already have in your toolbag, and try to get built or purchased whatever else it is you need!
UI-only testing because it's the "only component that the tester can easily control" is no excuse."