Scribd
Upload
12 views4 pages

Group 7

Uploaded by

Hemanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
12 views4 pages

Group 7

Uploaded by

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

Non-functional Testing

Non-functional testing is a type of software testing that evaluates the non-functional attributes of a
software application, such as performance, usability, reliability, and security, etc this testing checks
the Quality of the software to be tested.
Types of Non-Functional Testing
1. Performance Testing: Measures the responsiveness, throughput, and scalability of a system under
a specific workload to ensure it meets performance criteria.
2. Load Testing: Testing the software to determine how it performs under various user loads, from
normal to peak load.
3. Security Testing: Testing the software to ensure it is secure and protected against unauthorized
access, data theft, and other security threats.
4. Usability Testing: Testing the software to ensure it is user-friendly, easy to use, and meets the
needs of the end-users.
5. Compatibility Testing: Testing the software to ensure it is compatible with different hardware,
software, and network configurations.
6. Accessibility Testing: Testing the software to ensure it is accessible to users with disabilities, such
as visual or hearing impairments.
7. Scalability Testing: Determines the system's ability to scale up or down in terms of performance
under varying user loads.
FUNCTIONAL TESTING
What is Functional Testing?
Functional testing is testing the ‘Functionality’ of a software or an application
under test.
It tests the behavior of the software under test. Based on the requirement of the client, a
document called a software specification or Requirement Specification is used as a
guide to test the application.
Test data is sculpted based on it and a set of Test Cases are prepared. The software is
then tested in a real environment to check whether the actual result is in sync with the
expected result. This technique is called Black Box Technique and is mostly carried out
manually and is also very effective in finding bugs.
Type Of Functional Testing :

1. Unit Testing: Testing individual units or components of the software to ensure they
work as expected.

2. Integration Testing: Testing the Interaction between different components of the


software to ensure they work together seamlessly.
1. Acceptance Testing: Testing the software from the end-user's perspective to ensure it
meets their requirements and expectations.

2. Regression Testing: Re-testing previously tested functionality to ensure that


changes or updates to the software have not introduced new defects.

3. Smoke Testing: Testing critical functionality of the software to ensure that the
basic features are working correctly before performing more extensive testing.

4. Exploratory Testing: Ad-hoc testing that involves exploring the software to find
defects and unexpected behavior.

5. System Testing: Testing the entire system or software application to ensure it


meets the functional requirements
Defect Life Cycle
Defect/Bug : It is any variance between expected and
actual result

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy