Automation Testing
Let’s
talk about another aspect of Automation Testing.
I am
trying to explore selenium. I believe, one of the best ways to learn it, learn
and share
Here I
am starting with basics post on Automation testing, general topics and I will
move to selenium tool exploration along with you guys.
What is Automation Testing
How Automation testing is different from
Performance testing?
Since I
am Performance tester so first question come in my mind is the difference in
both approach.
The
basic difference is in the verification and assertions done in the two
different test types.
In Automation Testing the verification and assertions
done are all oriented to validating that the actual full functionality as
described in the specification, was passed.
Automation
Testing focuses on the overall functionality of the application. Does it work
the way it is expected to, or does it continue to do (regression) what is known
to do. Automation Testing goes across the system and in-depth as needed.
Whereas
in Performance testing these verification and assertions are focused on
validating that all data and especially the expected data is loaded.
Performance
Testing looks at more narrow sections of the system. It focuses at ‘how well’
the system does under different conditions of load (how much work and by how
many). These are done to prove reliability/stability and ‘performance’ (does it
meet an SLA) of the overall system (hardware, software and architecture).
Types of applications are suitable for
Automation Testing
The answer
is Stable one.
If we
know in advance that much of the functionality in our application will be
stable over time without needing any changes. We can perform automation testing
for this kind of Applications.
In case if any applications
functionality keeps on changing, it means that the application is not stable,
and this kind of applications won’t be suitable for Automation.
Type of test cases which we can automate
As per
my understanding, no application can 100 % automated for testing. So we need to
choose and carefully categories the test cases in boarder way which can be
automated:
·
Stable Tests - The tests that are not going to change in
the upcoming builds
·
Smoke Tests - The tests that give a quick high level
assessment on the quality of the build
·
Data Driven Tests - The tests which test the same functionality
with different inputs and large data sets
·
Highest Priority Tests - The tests that you want to test often
because of their priority over the other tests.
Also depends on the business and size
of the project to decide on the number of scenarios to be automated. Sometimes
we automate 70 to 80% of the scenarios when the business needs them to be
automated.
I will
post more in case we need more concepts-based topic. Now, I am curious to jump
on Selenium learning (new things keep you pulling)
Happy Testing!!!
Comments
Post a Comment