Retesting:

Re-executing the failed testcases on a new build is known as ‘Retesting’.

Regression Testing:
Re-executing the old test cases in order to ensure that the changes like addition, deletion, modification or bug fixes does not cause any impact on the unchanged
module/unchanged feature of the application

TYPES OF REGRESSION TESTING

Unit Regression Testing:

When we know that the change is not going to cause an impact on other modules /feature to be tested. This is called Unit regression Testing.
Example: Changing the number of characters to be accepted in pwd from 25 to 35

Regional Regression Testing:

Testing the changes and the impacted regions is region Regression testing

Example: In email, adding newly attachment feature to compose mail checking the compose mail, sent items and drafts is regional regression testing

Full Regression Testing:

As there are lot of changes in app, we test the changes and the complete Application is full regression testing

Example: Data base changes, language changes, web application to desktop application or vise versa

When do we go for full regression testing?

When majority of the features in the application undergoes a change

Whenever there is a change happening in the core engine of the App or in the architect of Application
Example: In Java changing the JVM or JRE and checking if the full app is working or not

Drawbacks of manual regression testing:

Time taken to test the S/W will be more
 The work becomes boring

The level of consistency in performing the task decreases

Acceptance Testing:
It is a testing done by the customer or end user in order to check the created Application is working as per the business needs of the customer.
It is a testing done by the end user in order to check the created Application is working as per the functional needs of the user.
Why we do acceptance testing or Why do customer need to do acceptance testing:

 To check with created Application is working as per the business needs of the customer

 To check if all the req of the customer is been properly met

 To check whether there is outstanding issues present in the S/W

 To check with the Application works in the environment similar to the production environment

Types of Acceptance Testing:

User Acceptance Testing:
This testing is mainly carried out from functionality perspective, validating the fitness of use of the Application by the user.

Operational Acceptance Testing/Production Acceptance Testing:

It is a testing carried out by a system administrator, where we focuses the fitness of use or how much the system can be used on Operational perspective.

It includes the parameter like Back-up and restore Recovery Features, Security features, Maintenance features

Regulatory Acceptance Testing/Compliance Acceptance Testing:

This Testing is mainly carried out in government laboratory focusing on the areas of legal aspects and the safety measures or rules and regulation
Smoke Testing: /Sanity testing/Skim testing/Dry run Testing/Limited testing/Quick testing:
It is initial testing is done to check the given Application is stable enough for further testing. This testing is carried out by testing engineers by identifying the crucial or
the critical functionality present in each module and having them to be tested in a basic manner. In this testing we don’t perfume any exhaustive testing and we identify only
+ve testing TC for having Application tested.

When do we go about doing smoke testing?

Whenever we have a build obtained, Smoke testing is the initial testing done to check the given the build is stable enough for further testing process
We choose +Ve Test cases mainly & that belongs to integration (TC)

Order of execution: [Build given]

 Smoke Testing

 Functionality Testing

 Re-Testing

 Regression Testing

Testing types done by build engg:

 Build Verification Testing (BVT)

 Build Acceptance Testing (BAT)

Part of Smoke Testing done by build engg: (BVT/BAT)

 APP SERVER: ON

 WEB SERVER: ON

 DB SERVER: ON

 FILE SERVER: ON

 TARGET NODE: ON
 Sanity Testing:

It is subset of Regression Testing. When the build obtained is having some minor changes in code, we perform this testing when there is no time for performing a complete
regression testing. Usually this is carried out when there is some enhancements or defect fixes to make sure that this is not impacting other modules. We do this testing only on the impacted
functionality only.

Sanity Testing Smoke Testing

 Tested in narrow and deep manner  It is done in wide range and shallow manner

 e.g., FB clicks on like  Smoke Testing TC remains Same

1. 5 emojis (newly added features)  The TC can be Scripted

Detailed Manner
2. Checking notifications
Basic Manner (Impact)

 Sanity testing TC keeps on changing. For each build TC keeps changing.

Changes can be add, mod, delete, bugfix

 Sanity Testing TC is not Scripted because functionality

keeps on changing

Non-Functionality Testing:
Check non-functionality aspects (performance, usability, reliability, etc) of a software application. It is designed to test the readiness of a system as per non
functionality parameters which are never addressed by functionality testing

Performance Testing:
 Definition:
Testing Stability and response time of an Application by applying the desired load.

Load:
The active no.of users which the Application can handle is what is called Load
 Number of users logged in to the university website at the given point of time (eg: University login)

Response Time:
The time taken for a particular Application to respond is called Response

Load increases Response time increas es

Stability:
How for the Application is able to handle the desired Amount of load

Ex. When the “App” is designed for 5000 users, on applying 1000 users, when the application crashes it is said to be
unstable Application
Once I have confirmed my App is functionally stable then I go for performance testing

When we go about doing performance testing:

When the Application is functionally stable, we can go ahead and do this performance testing

Tools: JMeter, Rational performance Tester, Testing Anywhere, SmartMeter.io, etc.

T
ypes of Performance Testing

 Load testing

 Stress testing

Scalability testing
  Volume testing

Load Testing
Applying a load which is less than or equals to the desired number and checking stability and response time of an application is called Load testing.

Stress Testing
Applying a load which is greater than the desired number and checking stability and response time of an application is called as stress testing

Scalability Testing
Applying a load which is greater than the desired number and checking exact point in which the Application gets crashed is called scalability Testing
Volume Testing/Flood Testing
Transferring huge amount of data from one source to another source and checking the stability and the level of consistency in which data transfer happens
Soak Testing: (Endurance Testing)
Applying a load over a period of time and checking the stability and the response time of an application is called Soak testing

Reliability Testing
It is a testing done to verify the capability of a S/W to perform a failure free operation for a specify period of time in a specified environmental condition

Spike Testing

It is a part of load testing. This testing is performed to verify the stability of an application when there is sudden burst of users. This testing is done by applying varying degree of
load to check behavior of the Application

Compatibility Testing / Cross Browser Testing / Cross Platform Testing:

Testing the application in different H/W configuration and S/W configuration

Usability testing:
 Testing the user friendliness of an Application
1.Easy to use/Access -Struggle/easy access check
2.Understand -how simple/easy to understood check
3.Compatible -Checking usable in different device
4.Time taken -Time taken to done a work (ex: create a Acnt)
5.Look and feel -We See we need feel good -check
6.Performance -ex: IRCTC (Tatkal booking late)
7.Recall -Customer comeback are not
8.Emotional Response -How do you feel while doing a task
9. Accuracy - How much the Application take care you, not doing mistakes.

Accessibility testing/ADA testing/508 Compliance Testing:

ADA-American Disability Act testing

What is accessibility testing?

Testing the Application from the perspective of physically challenged people is caused as accessibility Testing
W3C-World Wide Web consortium
WCAG-Web Content Accessibility Guidelines
Spike Testing
It is a part of load testing. This testing is performed to verify the stability of an application when there is sudden burst of users. This testing is done by applying varying
degree of load to check behaviour of the Application

Security testing
It is a type of Software Testing that uncovers vulnerabilities, threats, risks in a software application and prevents malicious attacks from intruders. The purpose of Security
Tests is to identify all possible loopholes and weaknesses of the software system which might result in a loss of information, revenue, repute at the hands of the employees or
outsiders of the Organization.

INTERNATIONALIZATION TESTING / I’TSN TESTING:

Software which is created by FT,IT,ST,Smoke testing for a region in a particular language is customized to another region in another Language

Definition:
It is a process in which a application which is created for a specific Long and for a specific region this been internationalized to work for diff regions and for diff language
without engineering charges

The content writer in English is provided to the translator to convert to desired language
 The converted content in other language should be tested in languages perspective and functionality perspective

To test the language, we engage language expert to perform “Translation Verification Testing”

Verification Testing:
Language expert checks 1. Spelling 2. Grammar 3. Usage of Words
In functionality perspective we use the same test cases but in cases of name of features or component, we add in specific Language
If an issue occurs in all the languages, we say that it is functionality issue

Example:
If we consider that we try to make payment in Amazon. In Amazon.com, Amazon.UK, it’s not working everywhere then if it’s functionality issue. If the same
make payment section is not working only in Amazon. UK then it is due to internationalation issue

Localization Testing /L1ON Testing:

The Process of customizing the internationalized for different regions is called Localization testing

Ex: Both Telangana and Andhra people speak Telugu. The app which is internationalized for total Telugu people customizing this S/W according to the rules and regulations
of Telangana separately and Andhra Separately is localization testing

Definition:
It is a process of adapting the internationalized S/W a specific region and for a specific Language is Localization Testing

Globalization Testing:
Internationalization testing and Localization testing put together is called Globalization Testing