http://www.logigear.com/blog/will/my-attempt-to-clarify-my-everything-statement/ Software Testing Community Sun, 22 May 2011 19:44:43 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://www.logigear.com/blog/will/my-attempt-to-clarify-my-everything-statement/comment-page-1/#comment-3 Dmitry Khomikh Wed, 21 Oct 2009 18:11:27 +0000 http://www.logigear.com/blog/?p=221#comment-3 i agree 300% with Bill on automation developed should be exersised constantly on everyday basis, so that it is ready for real battle with new build/release just in time. I would like to stress the special importance of this notion with UI test automation where even 'under the hood' change in the application under test (for example web grid control properties change) would cause UI automation choke. In order UI automation would produce predictable an reliable reults it's got to be run on every single minor release before verifying major release of the product. Working in Agile environment automatically puts automation under test every day or so. Dmitry (#1 automation expert:) i agree 300% with Bill on automation developed should be exersised constantly on everyday basis, so that it is ready for real battle with new build/release just in time. I would like to stress the special importance of this notion with UI test automation where even ‘under the hood’ change in the application under test (for example web grid control properties change) would cause UI automation choke. In order UI automation would produce predictable an reliable reults it’s got to be run on every single minor release before verifying major release of the product. Working in Agile environment automatically puts automation under test every day or so. Dmitry (#1 automation expert:)

]]>