Test Notes

I don't make software; I make it better

  Home  |   Contact  |   Syndication    |   Login
  68 Posts | 0 Stories | 22 Comments | 641 Trackbacks

News

  

Please Note
The information in this weblog is provided “AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion.


Google 

Groups
SoftwareTesting
Browse Archives at
groups.google.com



  Page Loads:

Technorati Profile

Click for Hyderabad, India Forecast

Archives

Post Categories

Image Galleries

Friend's Blog's

Groups

Sites

Testing Blog's

If 'B' represents what you need in order to perform satisfactory test automation for your own particular context and 'A' is the set of tools that are available to you, then "Homebrew Test Automation" is what you may need to create on your own in order to bridge the gap between 'A' and 'B'.  
 
"Homebrew Test Automation" may include adding extensions to or modifying existing tools. It may also include writing new tools and/or integrating exiting tools in novel ways.  
 
Whether the tools are commercial or free should be irrelevant. What is relevant is how easily the tools lend themselves to the above activities, either through providing source code, a well thought out extensibility interface or some combination, and whether you can ultimately demonstrate a positive return on investment in time and materials.

--written by Mike Silverstein in Stickyminds Roundtables

posted on Monday, April 12, 2004 10:09 PM