By Kanglin Li
The foremost difficulties i have encountered with try out automation aren't technical yet managerial: it is infrequent that people with the making plans and decision-making authority have the neccessary knowing of what try out automation is and the way it matches into the development/testing cycle. it is not "sped-up handbook trying out" and it isn't "record and playback", even though it might include components of either and extra. it is a improvement attempt in its personal correct and desires to be controlled as such.
I've used the various significant commerical automation instruments and constructed others in-house and none of them are the silver bullets their owners (and in-house evangelists) declare they're. some time past, you will were hard-pressed to make the case to administration for writing your individual in-house complete featured GUI checking out instrument. It required a developer ability set that many in QA - even these on automation groups - do not constantly have in adequate intensity (not to say the truth that, so much who do have the abilities decide to make extra dollars over in development).
What the maturing of .NET and Microsoft's UI Automation Library have performed, i feel, is placed the writing at the wall for advertisement UI try instruments equivalent to QTP and sensible Tester (WinRunner is on life-support, quickly to be removed).
As extra computer purposes themselves gravitate in the direction of .NET and, more and more, local 64-bit, advertisement instruments are suffering to maintain speed.
This ebook demonstrates the benefits automation builders have in growing their very own automation instruments for .NET-based functions, thank you basically to the shut tie-in with the mirrored image namespace, UI automation libraries and COM interop serivces. The C# or VB.NET language ability set, whereas now not trival, isn't the similar as writing C++ COM/ATL code, which might were the single believable alternative a decade in the past to create an automation software.
People coming from a script language coding historical past, ideally with a few local Win32 programming of their earlier, should still transition to .NET languages particularly easily. in the event that they have an outstanding seize of the variations among unit trying out, integration and approach trying out, there is a lot during this booklet to use either actually and to take advantage of as a conceptual base for growing an automation device much more adapted on your particular program needs.
I do not often touch upon different experiences yet i must say the examples within the ebook labored simply effective on my XP SP3 machine surroundings, operating the newest model of the .NET framework. Having been round software program improvement and trying out for 20+ years i am definite that person's tricky adventure was once real, yet it truly is unfair to offer all readers the effect the publication comprises undesirable code.
What the e-book does comprise in abundance is painfully undesirable English. i do not say this with any disrespect in the direction of the authors. i am convinced they're doing their most sensible and, as somebody who speaks just one language (and struggles frequently with it), I recognize a person who makes an attempt to profit and use one other, in particular in a technical field.
My feedback is geared toward the Sybex editors, who quite dropped the ball the following by means of letting a massive ebook out the door with out enough review.