| || |
i need ur expert opinions here ...
if i were to automate my company's future products, what should be the standards to be followed to make my products testable.
what should be sermoned to the developers that they have to follow a certain path/standard to make this application testable in the future?
Most of us here in this forum have programming gbackgrounds and when testing certain applications they wud have thought what if the developer had just done a little different than this, how easy it could have been for me to automate...
this is just a scenario that i often encounter when my testing software fails on certain controls.
i need these scenarios to make a future draft for the things developers should practice.
i hope i have made my points clear.
Re: AUT standards
1) Standards: search this site and follow the links tab upper right on this page. Standards may be too extensive to list here. Bottom line - you want to make sure the tool works with the application-under-test.
2) "Sermoned": I don't believe anyone likes being sermoned to! [img]images/icons/smile.gif[/img] "Testability" is something you can help drive in requirements analyses and design reviews, in addition to following development standards. There are many books and white papers on this topic. You could begin by searching this site. There are also books and white papaers about how to determine what should be automated.
The point I'm trying to make is that the answers to your questions are too voluminous to list here.