kasperanalytics.

com

+918130877931

Testing

[email protected]

kasper-analytics
 What is Software Testing?

• Software Testing is the process of evaluating and verifying that a software product or
application is functioning right.
• Software Testing can be stated as the process of Verifying and Validating whether a software or
application is bug-free, meets the technical requirements as guided by its design and development, and
meets the user requirements effectively and efficiently by handling all the exceptional and boundary
cases.

• The process of software Testing aims not only at finding faults in the existing software but
also at finding measures to improve the software in terms of efficiency, accuracy and usability.

Who does Testing?

• Software Tester
• Software Developer
• Project Lead/Manager
• End User

Difference between Testing and Debugging:

Testing:

➢ It involves the identification of bug/error/defect in the software without correcting it.

Debugging:

➢ It involves identifying, isolating and fixing the problems/bug. Software Testing

can be divided into two steps:

➢ Verification
➢ Validation

Verification:

➢ It is a process of confirming whether the software meets its requirement or not.

➢ Process of examining/reviewing of work product.
➢ Are we building the product right?
➢ It is a QA activity.
➢ It’s a static process performed at compile time.
➢ Cost and Time effective.
➢ Activities involved in this are inspections, reviews, walk-through.
 Validation:

♦ It is a process of confirming whether the software meets user’s requirement or not.

♦ Process of executing a product and examining how it behaves.

♦ Are we building the right product?
♦ It is a QC activity.
♦ It’s a dynamic process performed at run time.
♦ It is performed by a QC team.
♦ Cost and time taking.
♦ Activities involved in this are testing the application.

Importance of Software Testing:

 Defects can be identified early.
 Improves quality of software
 Increased customer satisfaction
 It helps with scalability.
 Saves time and money.

What Is Software Testing Life Cycle?

Software Testing Life Cycle is a process used to test software and ensure that quality standards
are met. Tests are carried out systematically over several phases. During product development,
phases of the STLC may be performed multiple times until a product is deemed suitable for
release.
Common Activities included in STLC are:

➢ Analysis of client and stakeholder system requirements.

➢ Creation of a traceability matrix.
➢ Identification of testing techniques and types needed for each feature.
➢ Prioritization of features to be targeted.
➢ Analysis of how tasks can be automated.
➢ Identification of environment information.

STLC Phases:
Defect Logging:

Any defects or issues that are found during the test execution are logged in a defect tracking
system, along with details such as severity, priority and description of this issue.
Defect Life Cycle:

During testing, if tester find any bug/defect, report that to the developer immediately.

The developer will fix the issue and reassign it to the testing team.

Then, the testing team will retest again. So, until all the bugs get closed, we should not close
the testing process cycle.

It is important to note that test execution is an iterative process and may need to be repeated multiple
times until all identified defects are fixed and the software is deemed fit for release.
Test Closure:

Test closure is the final stage of the STLC where all testing related activities are completed and
documented. The main activities that take place during the test closure stage include:

o Test Summary Report

o Defect Tracking
o Test Environment Clean-up
o Test Closure Report
o Knowledge Transfer
o Feedback and Improvements

Test Summary Report:

A report is created that summarizes the overall testing process, including the number of test cases
executed, the number of defects found and the overall pass/fail rate.

Defect Tracking:

All defects that were identified during testing are tracked and managed until they are resolved.
Test Environment Clean-up:
The test environment is cleaned up, and all the test data and test artifacts are archived.
Test Closure Report:

A report is created that documents all the testing related activities that took place, including the
testing objectives, scope, schedule and resources used.
Knowledge Transfer:

Knowledge about the software and testing process is shared with the rest of the team and any
stakeholders who may need to maintain to support the software in the future.
Feedback and improvements:

Feedback from the testing process is collected and used to improve future testing processes.

Levels of Testing in Software Testing:

 UNIT Testing:

➢ A unit is the smallest testable part of any software.

➢ It is the level of software testing where individual components of a software are tested.
➢ Unit testing is a White box Testing technique that is usually performed by the developer

Unit Testing Tools:

o Junit
o NUnit
o JMockIt
o EMMA
o PHPUnit

INTEGRATION TESTING
➢ It is a level of software Testing where Individual units are combined and tested as a group.
➢ Integration Testing focuses on checking data communication amongst the modules.

Methodologies of Integration Testing:

o Big bang Approach
o Incremental Approach

System Testing:

➢ It is a level of software Testing where a complete and integrated software is tested. The purpose
of the test is to evaluate the system’s compliance with specified requirements.
➢ It falls under The Black Box Testing category of Software Testing.
➢ It is the third level of testing performed after Integration Testing and before.

Acceptance Testing:

It is a level of the software Testing process where a system is tested for acceptability.
➢ Internal Acceptance Testing, known as Alpha Testing, is performed by members of the
organization. Usually, it is done by the members of Product Management, Sales and Customer
Support.
➢ User Acceptance Testing, known as Beta Testing, is performed by the end users of the
software. They can be the customers themselves or the customers’ customers.

Regression Testing:

➢ After enhancements in the application, testing is done to ensure that the existing functionality
of the application is working fine.

Retesting:
➢ It is running the previously failed test cases again on the new software to verify whether the
defects posted earlier are fixed or not.
Smoke Testing:

➢ Build Verification test done to ensure the major functionalities of the application are
working fine.
Sanity Testing:

➢ It is done to ensure that the addressed scope of the release is tested and the same works
fine.
Exploratory Testing:

➢ It is done with the experience of the tester to explore the application to understand the
functionality and find the defects. This is done without formal documentation.

Secure Testing:

➢ It is done to check how the application is secure from internal and external threats like viruses,
malicious programs.

Types Of S/W Testing:

 Manual Testing:

It is a kind of software Testing in which a Software tester develops and executes the test cases
without using any automated testing tools

Types:

• White Box Testing:

o It is done by developers.
o This testing is focused on Internal Structure and logic of the code. o Structural Based
Technique.
o They are also called Glass box testing.

• Black Box Testing:

o It is done by testers.
o This testing focuses only on what kind of Inputs we are giving. And it checks
whether the output meets the requirements.
o This is a specification-based technique.

• Gray Box Testing:

o It is a combination of white-box testing and black-box testing.
o The aim of this testing is to search for defects, if any due to improper structure or
improper usage of application.

Non- Functional Testing:

Performance Testing:
Testing the performance of an application by providing some workload (number of users).
Load Testing: If workload is between the limits.
Stress Testing: If the workload is beyond the limits.
Scalability Testing:
o If the number of users is to the maximum limit, to test the system is not getting crash or not.
Stability Testing:
o To test the application is stable or not, when we give the maximum workload.
Compatibility Testing:
o Testing the app whether it works on different OS, devices, different browsers and its versions.
Usability Testing: It is done to test whether the application is user-friendly.

Automation Testing:

o It is the application of software tools to automate a human-driven manual

process of reviewing and validating a software product.
o It is used to reduce the testing efforts, also testing faster delivery capability.