Comments on: 10 Tips you should read before automating your testing work

By: sowmya

sowmya — Mon, 06 Feb 2012 09:43:00 +0000

thank u rahul dude……hw r u

By: sowmya

sowmya — Mon, 06 Feb 2012 09:41:53 +0000

thank u rahul dude

By: teja

teja — Mon, 06 Feb 2012 09:37:48 +0000

hiiiiiiiii sneha

By: sowmya

sowmya — Mon, 06 Feb 2012 09:30:52 +0000

testing is nothing automated u r really waste bhavya from us

By: sowmya

sowmya — Mon, 06 Feb 2012 09:29:27 +0000

gud mrng have a nice day………
i’m very feel about ur bad comments

By: sowmya

sowmya — Mon, 06 Feb 2012 09:28:25 +0000

veryyyyyy bad

By: Joe

Joe — Mon, 12 Dec 2011 14:20:52 +0000

A realistic evaluation of automation candidates needs to be done before the effort is started. From experience, automating highly volatile areas will only result in much more time being spent on automation script maintenance per release, and just as many or more bugs due to less time allocated to manual testing.

By: Twinkle chowdary

Twinkle chowdary — Sat, 27 Aug 2011 11:39:42 +0000

hi vijay,
its really a good explanation of automation.i can agree with ur point Instead of relying 100% on either manual or automation use the best combination of manual and automation testing.it was absolutely a right thing to do…
thanx for giving such an information about automation tool

By: chandra sekar

chandra sekar — Mon, 13 Jun 2011 12:03:06 +0000

can any one tell which are tools not consist of programming knowledge

By: Anish Kumar Bindal

Anish Kumar Bindal — Mon, 15 Nov 2010 10:17:11 +0000

Tests that are not advisable to automate or ROI is very high if we plan to automate
1. Only one time tests
2. Reviewing release notes, documentation
3. UI related tests (e.g. Light grey color background and UI is not disrupted across various browsers)
4. Coverage is less for tests and custom controls being used by Dev. This can still be automate dif we have expertise in creating Win 32libraries and dlls.