Different types of testing performed in all phases of CI/CD Pipeline.

1. Plan:
a. Documentation testing: testing effort required and test coverage
It may be a type of black-box testing that ensures that documentation about how to use the
system matches with what the system does, providing proof that system changes and
improvements have been documented.

2. Code:
Single user:
a. Unit testing
Multiple user:
b. Integration testing multiuser
3. Build:
a. Integration testing
b. Security testing
c. Smoke testing: performed on initial builds to check whether the core functionalities
are working fine. It is performed to check to the stability of the build.
d. Regression testing.
4. Test:
a. Unit testing
b. Sanity testing: quick evaluation of build to check weather to determining it is
eligible for further round of testing.
c. Integration testing
d. System testing
e. Performance testing: conducted before the actual release to test the application
performance under specific (unfavorable and favorable) conditions.
f. Reliability testing:
g. Interface testing: when development is completed interface is verified and
validated such as interface between the hardware and software, server communication
etc.
h. Security testing:
5. Release:
a. Alpha
b. Beta
c. UAT: assess weather it is acceptable for production
 d. Regression testing: stability of the product with the changing requirements.
6. Deployment:
a. Installation testing: what customer will need to do to setup and install the
application successfully.
b. Smoke testing: check the core functionality of the application is working fine.
7. Operate:
a. Regression testing.
b. Performance testing.
8. Monitor:
a. Interface testing: once the whole software is ready, deployed and working then
interface needs to be monitored (such as server execution and error handling is proper)
and any new issues due to changes made.
b. Performance testing
Latex.tex:
\documentclass[10pt,journal,compsoc]{IEEEtran}

\usepackage[utf8]{inputenc}

\title{Different types of testing performed in all phases of CI/CD Pipeline.(Assignment)}

\author{Roll number: 19014198-070, Section: B, Name: Syed Rizwan Header}

\date{August 2022}

\begin{document}

\maketitle

\section{Plan}

\subsection{Document Testing}

it is performed to estimate testing effort required and test coverage.

\subsection{For single User}

\subsubsection{Unit Testing}

It is performed by developer to test the individual modules.

\subsubsection{Integration testing}

it is performed by a developer to check the correctness of communication between individual modules.

]\subsection{For multiple user}

\subsubsection{Integration testing}

In case of multiple users code is shared to shared repository and individual modules are combined and
tested together.

\section{Build}

\subsection{Integration Testing}

individual modules coming from different developers, repositories are combined and tested together.

\subsection{Smoke Testing}

It is performed on initial builds to check the whether the core functionality is working fine and whether
it should be passed for further round of testing

\subsection{Regression Testing}

it is performed to evaluate whether any new functionality added affects the existing functionality.

\section{Test}

\subsection{Unit Testing}

in this is it is performed by tester to test the individual modules are working fine.

\subsection{Integration Testing}

in this phase it is performed by tester to evaluate the communication between the different modules.

\subsection{System Testing}

it is performed on a complete integrated system to verify that the system meets the user requirements.
\subsection{Sanity Testing}

it is quick evaluation of build to check weather to determining it is eligible for further round of testing, in
case of little changes made in code.

\subsection{Performance Testing}

it is conducted before the actual release to test the application performance under specific (unfavorable
and favorable) conditions.

\subsection{Security Testing}

it is performed to identify and fix and vulnerability present in the system before the actual release.

\subsection{Reliability Testing}

it is performed before the actual release to test whether the system is fault free and reliable for its
intended purpose.

\section{Release}

\subsection{Alpha}

It is a type of UAT testing performed by internal testers to help identify bugs and other quality issues.

\subsection{Beta}

It is a type of UAT testing performed by real users to help identify bugs and other quality issues.

\subsection{Regression Testing}

it is performed in this phase to check whether any bug fixed or new functionality added affects the
existing functionality.

\section{Deployment}

\subsection{Installation Testing}

it is performed to evaluate what customer will need to do to setup and install the application
successfully.

\subsection{Interface Testing}

in this phase interface is verified and validated such as interface between the hardware and software,
server communication etc.

\subsection{Smoke Testing}
it is performed in deployment stage to check whether the core functionality is working fine.

\hfill

\section{Operate}

\subsection{Performance testing}

during the operate phase performance is evaluated to check the system response time ans stability of
the system.

\subsection{Regression Testing}

during the operate phase when new functionality is added it is tested whether it affects the existing
functionality.

\hfill

\section{Monitor}

\subsection{Interface Testing}

Once the whole software is ready, deployed and working then interface needs to be monitored (such as
server execution and error handling is proper) and any new issues due to changes made.

\subsection{Performance Testing}

In this phase performance is also monitored to maintain the positive customer experience and ensure
that it can handle any load generated by the user and in case of any discrepancy, to fix performance
bottlenecks.

\end{document}