The document discusses different types of software testing including manual testing and automation testing. It describes manual testing as testing done by a human without automation, involving test plans and scenarios. Automation testing uses scripts to rerun manual test cases quickly and repeatedly. The document also outlines various types of testing like unit, integration, system, and user acceptance testing. It provides definitions and examples of each testing type.
2. Testing
• Testing is the process of evaluating a
system or its component(s) with the
intent to find whether it satisfies the
specified requirements or not. In
simple words, testing is executing a
system in order to identify any gaps,
errors, or missing requirements in
contrary to the actual requirements.
3. Manual
testing
• Manual testing includes testing a software manually,
i.e., without using any automated tool or any script. In
this type, the tester takes over the role of an end-user
and tests the software to identify any unexpected
behavior or bug.
There are 5 types for the manual testing
• Manual Testing Types
• unit testing,
• integration testing,
• system testing,
• user acceptance testing.
• Testers use test plans, test cases, or test scenarios to
test a software to ensure the completeness of testing.
Manual testing also includes exploratory testing, as
testers explore the software to identify errors in it.
4. Automation testing
Automation testing, which is also
known as Test Automation, is when
the tester writes scripts and uses
another software to test the product.
This process involves automation of
a manual process. Automation
Testing is used to re-run the test
scenarios that were performed
manually, quickly, and repeatedly.
Apart from regression testing,
automation testing is also used to
test the application from load,
performance, and stress point of
view. It increases the test coverage,
improves accuracy, and saves time
and money in comparison to manual
testing.
5. Various
Types
Testing
• Unit Testing
• Integration Testing
• System Testing
• User Acceptance Testing
• Functional Testing
• Regression Testing
• Stress Testing
• Load Testing
• Performance Testing
6. Unit Testing
• Is a software development process in
which the smallest testable parts of
an application, called units, are
individually and independently
scrutinized for proper operation. This
testing methodology is done during
the development process by the
software developers and sometimes
QA staff.
7. Integration
Testing
• Is a type of software testing in which
the different units, modules or
components of a software application
are tested as a combined entity.
However, these modules may be
coded by different programmers
8. System
Testing
• Is a type of software testing that is
performed on a complete integrated
system to evaluate the compliance of
the system with the corresponding
requirements. In system testing,
integration testing passed
components are taken as input.
9. User
Acceptanc
e Testing
• UAT is also called application testing
or end-user testing, is a phase of
software development in which the
software is tested in the real world by
its intended audience.
10. Functional
Testing
• Is a type of testing that seeks to
establish whether each application
feature works as per the software
requirements. Each function is
compared to the corresponding
requirement to ascertain whether its
output is consistent with the end
user's expectations.
11. Regression
Testing
• Is a software testing practice that
ensures an application still functions
as expected after any code changes,
updates, or improvements.
Regression testing is responsible for
the overall stability and functionality
of the existing features.
12. Stress
Testing
• Is the process of determining the
ability of a computer, network,
program, or device to maintain a
certain level of effectiveness under
unfavorable conditions. The process
can involve quantitative tests done in
a lab, such as measuring the
frequency of errors or system
crashes.
13. Load
Testing
• Examines how the system behaves
during normal and high loads and
determines if a system, piece of
software, or computing device can
handle high loads given a high
demand of end-users. This tool is
typically applied when a software
development project nears
completion.
14. Performance
Testing
• Is a testing measure that evaluates
the speed, responsiveness and
stability of a computer, network,
software program or device under a
workload. Organizations will run
performance tests in order to identify
performance-related bottlenecks.
15. What is
Selenium?
• Selenium is an open-source umbrella
project for a range of tools and
libraries aimed at supporting browser
automation. It provides a playback
tool for authoring functional tests
across most modern web browsers,
without the need to learn a test
scripting language
17. How to
Write Test
Scripts
Using
Selenium
Tool
• Step 1: Get All the Components Ready. ...
• Step 2: Sign Up for the Browser Stack Account. ...
• Step 3: Choose Automate Tab from the Grid Menu. ...
• Step 4: Add the Necessary Codes. ...
• Step 5: Integrate the Changes with Browser Stack.