TEST AUTOMATION
13.1 Features to be
automated
…
…
…
13.2 Features not to
be automated
…
…
…
13.3 Which is the
automation tool you are planning to use
…
13.4 What is the
automation framework you are planning to use
…
We
automate the test cases only after the 1st release (we have studied
this earlier).
13.1 On what basis do we
decide which feature to be automated?
![]() |
| It shows important features and other features |
If
the features are very important and need to be repeatedly tested, then we
automate that feature. Because manually testing the feature takes longer time
and also becomes tedious job.
13.2 How to decide which
features are not to be automated?
® For ex, “HELP” is a
feature that is not repeatedly tested – so we don’t have to automate it.
® If the feature is
unstable and has lot of defects – we will not automate because it has to be
tested repeatedly manually.
® If there is a
feature that has to be repeatedly tested, but we are predicting a requirement
change for that feature – so we don’t automate it as changing the manual test
case is easier than changing the automation script.

No comments:
Post a Comment