Software Testing

It is the process of checking Software Application meets the requirement and works as Expected.

Different Types of Software Testing

Functional Testing with Example

It checks whether a software Application works according to the requirements. It Verifies 'What the system does' and checks if the features are working correctly.

a) Unit Testing

It is the process of testing the smallest part (unit) of a program, usually method or function to make sure it works correctly. It is done by developers.

Example: Add(5,3) = 8

b) Integration Testing

Individual modules are combined together and tested as a group to ensure that they work as expected.

c) System Testing

It tests the entire Application. It covers end-to-end functions of the system. Final Phase of testing before the product is released.

Regression Testing

Recent Code-changes haven't negatively impacted existed functionality. Software Continues to work as expected after bug-fixes.

UAT (User Acceptance Testing)

Final Phase of testing where actual users, clients or business representatives verify that the software meets the business requirements.

It is usually performed by:

• Business Users
• Clients / Customers
• Product Owners
• Business Analysts

Performance Testing

• It checks how fast, stable and responsive when an application works under different workloads.
• It checks whether application works smoothly when many users use the same application.

Load Testing

It is a type of performance testing and checks how an application behaves when an expected number of users or requests.

Stress Testing

• It is a type of performance testing and checks how an application behaves when a load goes beyond its expected capacity.
• It happens when the system is overloaded.
• The goal is to find the breaking point of application and see how it recovers.

Scalability Testing

It is a type of performance testing in which application is handled by increasing number of resources, users, transactions or data by adding more resources.

Stability Testing

It is a type of performance testing and checks whether an application can run continuously over long period of time without crashing, slowing down or showing errors.

Example: Video streaming application is expected to run 24/7.

Usability Testing

It is used to check whether the application is easy to use, understand and navigate to end users. It verifies user can use the application comfortably without any confusion.

Compatibility Testing

It is used to check whether the application works correctly on different devices, browsers, OS, Networks and Screen Sizes.

Example: Verify that OK button works fine in Chrome but not in Safari. It is a compatibility issue.

Security Testing

It is the process of checking whether an application is protected from unauthorized access, data thefts and security threats.

End-to-End Testing

It is the process of testing a software application from start to finish. Entire Application is tested from start to finish.

Adhoc Testing

It is the process of testing where tester tests the application without following the predefined testcase or testscripts.

Exploratory Testing

Learns the application, designs the testcases and executes them at the same time without following any pre-defined testcase or testscripts.

Edge Case Testing

How an application behaves during the unusual condition of an input data.

Smoke Testing

Once we get a new build we will start testing all major functionalities are working fine.

Sanity Testing

Quick check performed after a bug fix or small change to verify that the specific functionality works correctly.

SIT Testing (System Integration Testing)

Performed to verify that different systems or applications work together correctly.

Defect Life Cycle

Defect Leakage

Defect Leakage happens when a bug is not found in testing and reaches the customer or production environment.

Defect Rate Metric

It is a metric that measures how many defects (bugs) are found in a software application during a specific period or relative to the size of a software.

Root Cause Analysis (RCA)

It is the process of finding the actual reason (root cause) of a defect instead of just fixing the defect.

Software Development Life Cycle (SDLC)

SDLC in Testing refers to how testing activities are integrated into each phase of software development to ensure quality.

Software Testing Life Cycle (STLC)

STLC is a systematic process followed by the testing team to ensure that software meets the required quality standards.

Scenario

• High-Level description of functionality feature to be tested is Scenario.
• Generally derived from User stories.
• It focuses on What to test, how to test.

Test Case

Test case is a set of steps, inputs, Execution condition and Expected Results designed to verify a particular functionality. It includes Test Case ID, Test Description, Pre-conditions, Test Steps, Input Data, Actual Result, Expected Result, Status and Comments.

Pre-condition in Test Case

• It is something that must be true before executing a test case.
• It is the setup or environment needed before testing can start.

Test Plan

• It is a document that describes What to test, When to test and Who will test it.
• It includes project, scope, objectives, Test-types, Resources, schedule, Tools, Risks.

Test Strategy

• High Level document that explains how testing will be performed for a project.
• It defines the Overall methods, approach & testing types to be used.

RTM (Requirement Traceability Matrix)

• Used in the development of software application to trace the requirements proposed by the client to the system being built.
• It is prepared before the test case execution to make sure all the requirements are covered in the test case.

Agile Methodology

It is a way of developing software in small, manageable parts (sprints) with continuous feedback from the customer. Instead of building the entire product at once, Agile builds it step-by-step, tests it and delivers it frequently.

Agile Testing Lifecycle

1. Requirement Analysis
2. Test Planning
3. Test Case Design
4. Test Execution
5. Defect Reporting and Tracking
6. Regression Testing
7. Sprint Review and Retrospective

Popular Agile Frameworks

• Scrum
• Kanban
• Extreme Programming (XP)
• Lean Software Development

Challenges of Agile Testing

• Frequent requirement changes
• Limited documentation
• Tight sprint timelines
• Requires skilled and collaborative teams
• Continuous regression testing can be demanding

Waterfall Model

• Linear & Sequential Phases (Planning, Design, Implementation, Testing, Deployment) completed in Order
• SDLC is followed
• The Waterfall Model is a sequential software development methodology where each phase is completed before the next phase begins. In testing, the testing phase generally starts after development is completed.