Scribd
Upload
29 views7 pages

Automation Testing Unit 4

Uploaded by

Madhavan K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
29 views7 pages

Automation Testing Unit 4

Uploaded by

Madhavan K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Automation Testing

Manual testing vs. Automation testing


Software testing is performed to discover bugs in software during its
development.
The key difference between automation and manual testing are as
follows:

Manual testing Automation testing

In automation testing, automation


Testing in which a human tester
tools are used to execute the test
executes test cases
cases

In this testing, human resources are


It is much faster than the manual
involved, that's why it is time-
testing
consuming

Here automated tools are used


It is repetitive and error-prone that make it interesting and
accurate

BVT (build verification testing) is time- It's easy to build verification


consuming and tough in manual testing testing

Instead of frameworks, this testing use Frameworks like keyword, hybrid,


checklist, guidelines, and stringent and data drive to accelerate the
process for drafting test cases. automation process.
It completes a single round of
The process turnaround time is higher testing within record time;
than the automation testing process therefore, a process turnaround
(one testing cycle takes lots of time) time is much lower than a manual
testing process.

The main goal of manual testing is Automation testing can only


user-friendliness or improved customer guarantee a positive customer
experience. experience and user-friendliness.

It is widely used for performing


It is best for usability, exploratory and
testing, load testing and
adhoc testing
regression testing.

Low return on investment The high return on investment

Automation testing types


Testing is grouped under two types: functional and non-functional
Functional testing
 The first test performed by tester on newly revised software is
called functional testing, which verifies all the software
functions' features per user requirement.
 This testing works on the real-world business application and
obtaining the expected output from a given input.
 All application functions are tested and involve smoke, unit,
and integration testing.
a) Unit testing
 The unit is the smallest component of the software that
functions individually.
 Unit testing simplifies the testing of the whole software, where
each software element is fully tested before the final version is
out.
 Unit testing depicts how the code performs at each part and
has a faster execution time.
 It's the favourite of developers because it consumes less time
and assure the working of each part of the software.
 Before automation testing, the developers write the code for
testing, but now there is no need.
 The unit testing technique is divided into three broad
categories: White box testing, Black box testing and Grey box
testing.
b) Integration testing
 Integration testing is more complicated to set up compared
with other tests.
 All the modules of the application communicate with each
other to perform tasks.
 Therefore, testers group them for testing and exposing the
flaws in maintaining the interaction between these modules.
 Another name for this testing is I&T or string testing,
considered end-to-end.

c) Smoke testing
 This testing checks and defines the product's stability
(whether stable or not).
 If the product result is unstable, it is called an 'unstable build'
and sent back to developers, where they run more test cases
to find out the root cause of the problem.
Non-functional testing
 Non-functional testing focuses on how well application
functions are doing, not on what the product does.
 It is the opposite of functional testing, where application
elements like reliability, usability, performance, etc., are tested.
 Some types of non-functional testing are reliability testing,
load testing, compatibility testing, performance testing,
security testing etc.

a) Performance testing
 This non-functional testing tests the software's stability,
responsiveness and speed under the workload.
 It finds out the potential issues faced by critical software and
medical programs used by the user, like slow operation of
software under stressful circumstances.
 It finds hurdles in the performance of software
 And removes them to increase the ability of software to deliver
the best results to the end user.

b) Regression testing
 When some changes are made to the code of software or
application,
 It needs to be tested to determine whether the software is
working as before the change;
 This purpose, testers use automation regression testing to
automate scripts, applications of workflows, plans and other
activities.
 It tests the system or software workflow after its updation and
functional error.

c) Keyword driven testing


 Keyword-driven testing tests the application using the data
files consisting of the keywords related to the application,
representing a set of actions needed to carry out the step.
 This keyword testing is a popular choice for many businesses
as it's flexible, concise, easy to maintain and reusable.
 Keyword-driven testing is compatible with all kinds of
automation tools in the market.
 Instead of programming experts, functional testers can plan
the testing before the application is fully developed.

d) Data-driven testing
 In data-driven testing, automation is inbuilt and very effective
due to the few facilities provided, like the reusability of code,
change in the script doesn't affect the test cases,
 And this testing can be carried out in the phase of the software
development cycle.
 It provides consistency in results and reduces the investment
of time and resources.
 Test cases use the data separately stored in the table or
spreadsheet format, and testers have multiple data sets for
testing.

You might also like