Testing Types:

Smoke Testing
Sanity Testing
Exploratory Testing
Load Testing
Performance Testing
Ad-hoc Testing
Stress Testing
Monkey Testing
STLC

Type of software testing: -

Difference between Functional and Non-Functional Testing

Functional and Non-Functional Testing is what?

Functional testing is performed using the functional specifications provided by the client
or In this, tester has to test the application to see that all requirements of the client
written in SRS and BRS have been incorporated or not.

Non-Functional Testing is that which is always concerned with the client expectations.
Non-functional testing wants to know that the product “behaves” correctly. Like
performance, load and stress issues and so on.

Distinction between Functional and Non-Functional Testing

Functional Testing Non- Functional Testing

1. In functional Testing tester tests how 1. In Non-Functional Testing tester tests
well the system performs. how well the system responds.
2. Functional Testing is based on client 2. Non- Functional Testing is based on
requirements. client expectations.
3. Functional Testing means Testing the 3. Non- Functional Testing means Testing
application against business the application against clients and
requirements. performance requirements.
4. It is a part of System Testing. 4. It is also a part of System Testing
5. Functional Testing Validating the 5. Non- Functional Testing Validating the
behavior of application. performance of application.
6. This Testing covers Unit Testing, 6. This Testing covers Load/Performance
Integration Testing, Smoke Testing, Testing, Stress/Volume Testing, Security
Sanity Testing, Regression Testing and so Testing, Installation Testing and so on.
on.
7. It is always concentrating on customer 7. It is always concentrating on customer
requirements. expectations.
Functional Testing Types:

● Unit Testing
● Smoke testing
● Sanity testing
● Integration Testing
● System Testing
● Regression Testing
● UAT
● ETC…

Non-Functional Testing Types:

● Performance testing
● Load testing
● Stress testing
● Volume testing
● Usability testing
● Security testing
● Scalability testing
● Compatibility testing
● Localization testing and Internationalization testing
● ETC…

Functional Testing Types:

Smoke Testing: Testing the basic and critical feature of an application is

known as smoke testing.

Smoke Testing, also known as “Build Verification Testing”. It is performed to

ensured that the most important functions work.

The result of this testing is used to decide if a build is stable enough to proceed
with further testing.

Smoke testing is a Positive testing and start when the 1st build comes for testing.

Smoke testing covers most of the major functions of the software but none of
them in depth. The result of this test is used to decide whether to proceed with
further testing. If the smoke test passes, go ahead with further testing. If it fails,
halt further tests and ask for a new build with the required fixes. If an
application is badly broken, detailed testing might be a waste of time and effort.
Sanity testing: Sanity testing is the subset of regression testing and it is
performed when we do not have enough time for doing testing.

Sanity testing is performed after the build has cleared the smoke tests and has
been accepted by QA team for further testing. Sanity testing checks the major
functionality with finer details.

Regression Testing: Testing the unchanged features to make sure that it is

not broken because of the changes (addition, modification, deletion of feature or
bug fixes) made is called Regression testing.

Regression testing always starts with 2nd build. Regression testing can’t be
applicable on 1st build.

Any changes in the code might have impact on unchanged [Link] testing
the unchanged feature to find the impact is called as RT.

Types of Regression Testing:

1. Unit Regression Testing

2. Regional Regression Testing
3. Full Regression Testing
Unit Regression Testing: Testing only the changes or defect which is
fixed is Unit Regression Testing.

Unit Regression Testing is also called as Re testing. Here we only test

fixed bug.

Example: Testing the fixed bug of spelling mistake.

Regional Regression Testing: Testing the changes and the impact area
or impact regions is called as RRT.

Full Regression Testing: Testing the changes and all the remaining
features is called as full regression testing.

Non-Functional Testing Types:

Performance testing: First and foremost, type of non-functional testing

is performance testing. In order to ensure that the response time of a
system is acceptable, performance testing is carried out. By setting up a
considerable load and a production-sized database, the system is tested
for response times of several business-critical processes.

Load Testing:
Stress Testing:
This testing is done to pull the system far beyond its capabilities and see
how it reacts. Contrary to load testing in which the maximum allowable
load is generated, in stress testing, the load generated is more than what
the system is expected to handle.

Volume Testing:
When storage requirements and capabilities of the system are to be
tested, volume testing is done. When a huge database size is
encountered, system’s performance and its ability to exchange data and
information are tested in this case.

Usability Testing:
To verify the ease of usage of an interface within an application is what
usability testing is about. Learnability and memorability of the application
are main factors in this case. This testing is particularly important when
testing GUI.

Security Testing:
While performing non functional testing, to test how well the system can
preserve itself and the data it holds in situation of malicious attacks is
called security testing. Confidentiality, integrity, availability,
authentication and authorization are the main areas that are tested when
security testing is considered. Also, network security, system security and
application security are other areas that will be tested in this case.

Scalability testing:
When an application is tested for it ability to increase and scale up on any
of its non-functionality requirements such as load, number of
transactions, number of servers, volume of data etc., it is known as
scalability testing.

Compatibility testing:

An application is tested for its coordination with different hardware and

software that it is expected to work on. Another testing that can be done
is working of the application with different versions or releases of the
same hardware or software.

Volume Testing = Large amounts of data

Load Testing = Large amount of users
Stress Testing = Too many users, too much data, too little time and too little room

1)Do you have any hands on Experience in J-meter, Postman and selenium? If yes,
please elaborate : i have knowledge in selenium in navigation commad, alert popup,
file upload, etc, but i have most of working in codeception (automation).

2) Have you ever work in Agile Environment? : Yes

3) Do you know about Test Plan Creation, Test case Preparation and Bug Logging? If
yes, please elaborate? :

Test Plan Creation : 1 ) Introduction

2)Scope of work
3) Testing Process
4) Functional testing
5) Non functional testing
6) Test Deliverable
7) Enviornments needs
8)Responsibilities
9) Schedule
10) Staffing and Training Needs.

Test Cases Preparation :

1 )Test Scenario
2) Test Cases
3) Test Steps
4) Test Data
5) Expected Result
6) Actual Result
7) Status
8) Comment
9) Priority

4)Do you Know about Regression testing/ User Acceptance Testing and Sanity Testing?
If yes, please elaborate? :
Regression Testing :Testing the unchanged Feature to make sure that it is not broken
because of the changes made is called regression testing (Addition,modification, deletion
etc)

Sanity Testing : Sanity Testing is subset of regression testing it is perfome when we do

not have enough time for doing testing

5)Which different type of test creation and bug logging tools you worked on? : Git lab