Difference b/w Manual testing & Automation testing and the benefits of QTP?
What
is Manual testing?
Manual testing is the oldest and most
rigorous testing method. Manual testing requires a tester to perform
manual test operations to find defects in a software or application. The tester
ensures that’s the software meets its requirements by writing, understanding
and executing test plans and test cases.
Pros
·
If the test
case only runs twice a coding milestone, it most likely should be a manual test.
·
Less cost than
automating
·
It allows the
tester to perform more ad-hoc (random testing). In my
experiences, more bugs are found via ad-hoc than via automation.
·
The more time a
tester spends playing with the feature, the greater the odds of finding real
user bugs.
Cons
·
Running tests
manually can be very time consuming
·
Each time there
is a new build, the tester must rerun all required tests – which after a while
would become very mundane and tiresome.
What is Automation testing?
Over the years automation
testing has gained a lot of focus in the product development world as it is
more time effective and also more strategic in improving the quality of a
software or product. Automation testing is the process in which a manual test
is automated by using specific testing tools. A popular automated testing tool
is, Quick Test Professional (QTP).
Pros
·
If you have to
run a set of tests repeatedly, automation is a huge win for you.
·
It gives you
the ability to run automation against code that frequently changes to catch regressions in a timely manner.
·
It gives you
the ability to run automation in mainstream scenarios to catch regressions in a
timely manner.
·
Aids in testing
a large test matrix (different languages on different OS platforms). Automated
tests can be run at the same time on
·
Different
machines, whereas the manual tests would have to be run sequentially.
Cons
·
It costs more
to automate. Writing the test cases and writing or configuring the automate
framework you’re using costs more initially than running the test manually.
·
Can’t automate
visual references, for example, if you can’t tell the font color via code or
the automation tool, it is a
manual test.
Regression Test cases and
Automation Testing
Regression testing can be
specific to a module of a project OR for complete project (full regression
testing).
Let’s assume we have 500 test cases to test in Amazon.com.
Choose important test cases
which covers the major functionality of the project. Test case
that covers all the necessary
components, modules and related to the defect fixes should
include. It may also include
testing the performance of the application. It also depends on
project dead lines.
If we have automation test
scripts, we can
perform regression testing on all 500 test cases.In agile methodology, builds
are deployed daily, weekly basis. Automation test scripts can
be executed daily/weekly on
every new build.
How automation is done:
Record the script
Enhance the script by adding
functions and a data driving
Run the scripts
Report results
Job requirements for automation
testing using QTP is abundant at the moment. A quick search on www.dice.com will show you approximately 600
matches using the search string, QTP, quick test or “quick test”
H2KInfosys has an excellent
opportunity for you to learn automation testing using Quick Test
Professional (QTP).
Learn QTP from the comfort of
your own home and classroom. Our online/onsite course
·
offers LIVE
interactive training with an experienced QTP instructor. Our Live training
·
24/7 access to
instructional videos
·
New podcasts
·
Virtual meetings
·
Screen sharing
·
One on one
interactive help
·
24/7 online
resources including videos, demos, software, and examples.
Please refer the following link
for course details
Comments
Post a Comment