Types of Testing in Software Engineering | Levels of Testing

Summary

This video from Gate Smashers offers a comprehensive guide to various testing types crucial for competitive exams, college, university, and interviews. The presenter categorizes testing into four levels: unit, integration, system, and regression, aligning with the SDLC model. The explanation covers both functional and non-functional testing, including approaches like white box and black box testing, and emphasizes the importance of understanding these concepts for effective software testing and maintenance.

Takeaways

• 📚 The video covers various types of testing that are relevant not just for competitive exams but also for college, university exams, and interviews.
• 🔍 The testing types are categorized into four levels: Unit Testing (Level One), Integration Testing (Level Two), System Testing (Level Three), and Regression Testing (Level Four).
• 👨‍💻 Unit Testing is performed during the development phase, focusing on the smallest elements of the software, such as individual modules or functions.
• 🔄 Integration Testing occurs in the testing phase, combining units to ensure compatibility and proper integration.
• 🚀 System Testing involves testing the entire software system to ensure all components work together as intended, with categories including Alpha, Beta, and Acceptance Testing.
• 🔎 There are two main approaches to designing test cases: Black Box Testing, which focuses on inputs and outputs without considering the internal structure, and White Box Testing, which is based on the internal workings of the software.
• 🛠️ Regression Testing is conducted during the maintenance phase to ensure that upgrades do not affect the functionality of existing features.
• 🔑 Non-functional testing, also known as performance testing, evaluates aspects such as volume, load, stress, security, configuration, and compatibility, which are separate from the functional operation of the system.
• 📝 It's important to take notes of the points discussed in the video, as the categorization presented is unique and not commonly found elsewhere.
• 👍 The video encourages viewers to like, subscribe, and share the content, emphasizing the importance of subscriber support for the channel.
• 🔍 The script provides an overview of testing types and emphasizes the significance of understanding each level and category in the context of software development and quality assurance.

Q & A

What is the main purpose of the video 'Gate Smashers'?

The main purpose of the video is to explain various types of testing that are applicable not only in competitive exams but also in college, university exams, and interviews.

Why are the points discussed in the video important to note down?

The points are important to note down because the categorization presented in the video is unique and not commonly found elsewhere, which can be very helpful for understanding different testing types.

What are the four levels of testing categorization mentioned in the video?

The four levels of testing categorization are: Level One - Unit Testing, Level Two - Integration Testing, Level Three - System Testing, and Level Four - Regression Testing.

How does the video relate the levels of testing to the SDLC model?

The video relates the levels of testing to the SDLC model by explaining that each level corresponds to a phase in the SDLC, such as unit testing during the coding phase, integration and system testing during the testing phase, and regression testing during the maintenance phase.

What is the significance of Unit Testing in the development phase?

Unit Testing is significant as it involves testing the smallest elements of software, such as individual modules or functions, to ensure they work correctly during the development phase.

Can you explain the difference between White Box Testing and Black Box Testing as described in the video?

White Box Testing involves designing test cases based on the internal structure and coding of the software, whereas Black Box Testing is done without knowledge of the internal structure, focusing on inputs and outputs.

What is the purpose of Integration Testing and what are its four types?

Integration Testing is done to check the compatibility and proper integration of combined units or modules. Its four types are Bang-Bang, Top-Down, Bottom-Up, and Mixed.

What is System Testing and how does it differ from other testing types?

System Testing involves testing the entire software or system to ensure it works as intended. It differs from other testing types as it focuses on the overall functionality of the system after individual components have been tested.

What are the three categories of System Testing based on who is performing the test?

The three categories are Alpha, Beta, and Acceptance Testing. Alpha is performed by the development team, Beta by friendly customers, and Acceptance by the end-users to decide whether to accept the product.

How does the video describe Non-Functional Testing?

Non-Functional Testing, as described in the video, checks the non-functional parameters of a system, such as volume, load, stress, security, configuration, and compatibility, rather than its functionality.

What is the purpose of Regression Testing and how is it conducted?

Regression Testing is conducted during the maintenance phase to ensure that after upgrades or changes, the existing features of a product continue to work correctly. It is conducted by introducing artificial errors to check the system's response.

Outlines

00:00

📚 Introduction to Testing Types

This paragraph introduces the video's focus on explaining various testing types that are crucial for competitive exams, college, university exams, and interviews. The speaker emphasizes the uniqueness of the categorization presented and encourages viewers to take notes for future reference. The testing types are categorized into four levels based on the SDLC model: unit testing at the development phase, integration testing in the testing phase, system testing, and regression testing in the maintenance phase. The paragraph also introduces the concept of White Box and Black Box Testing as approaches to designing test cases, rather than types of testing.

05:02

🔍 Deep Dive into Testing Levels and Categories

The second paragraph delves deeper into the specifics of each testing level and category. It explains that unit testing is conducted during the coding phase and involves testing the smallest units or modules of a software. Integration testing follows, combining units to check compatibility and proper integration. The paragraph outlines four types of integration testing: Bang-Bang, Top-Down, Bottom-Up, and Mixed. System testing is described as testing the entire software system, with a distinction made between functional testing (Alpha, Beta, Acceptance) and non-functional testing (Volume, Load, Stress, Security, Configuration Compatibility). The paragraph concludes with a discussion on regression testing, which is performed during the maintenance phase to ensure that upgrades do not affect the functionality of existing features.

Keywords

💡Testing Types

Testing Types refer to the various methods and stages of evaluating software to ensure it meets the required quality standards. In the video, the speaker categorizes testing into different levels based on the Software Development Life Cycle (SDLC) model, emphasizing their importance in competitive exams, college, university exams, and interviews.

💡Unit Testing

Unit Testing is the process of testing individual components or units of a software to determine if they work correctly. It is the lowest level of testing and is conducted during the development phase, specifically in the coding phase. The script mentions that a unit could be a module, a function, or a piece of code, and it is the smallest element of the software being tested.

💡Integration Testing

Integration Testing involves combining individual units that have been tested and verifying their interoperability. It is categorized as Level Two in the video's testing hierarchy and is conducted during the testing phase of SDLC. The script explains that this type of testing checks whether the integrated units are compatible with each other.

💡System Testing

System Testing is the process of testing a completely integrated software system to evaluate the system's compliance with specified requirements. It is categorized as Level Three in the script and is conducted after the integration testing phase. The video uses the analogy of testing a car's performance on the road to illustrate the concept of system testing.

💡Regression Testing

Regression Testing is performed to ensure that changes or bug fixes have not adversely affected existing features of the software. It is categorized as Level Four in the video's testing hierarchy and is conducted during the maintenance phase of SDLC. The script emphasizes that regression testing is crucial to ensure that updates do not break the existing functionality.

💡White Box Testing

White Box Testing is an approach to designing test cases where the tester has knowledge of the internal structure of the system. It is not a type of testing but rather a method of test case design. The script clarifies that this approach is based on understanding the internal workings of the software, as opposed to Black Box Testing.

💡Black Box Testing

Black Box Testing is another test case design approach where the tester focuses on the inputs and outputs of the system without knowledge of the internal workings. The video script uses the example of driving a car without concern for its internal mechanisms to illustrate the concept of Black Box Testing.

💡SDLC Model

The SDLC Model, or Software Development Life Cycle Model, is a process used by developers to plan and manage the development of a software product. In the video, the speaker uses the SDLC model to categorize the different levels of testing, from unit testing during the coding phase to regression testing in the maintenance phase.

💡Functional Testing

Functional Testing is the process of verifying that the software functions according to specified requirements. It is a part of system testing and is mentioned in the script as a way to check how the system works, ensuring that it performs its intended tasks correctly.

💡Non-functional Testing

Non-functional Testing evaluates the software's performance, security, and other attributes that are not directly related to its functionality. The script describes this as a separate category of system testing, focusing on aspects like load, stress, security, and compatibility, rather than the functionality of the software.

💡Maintenance Phase

The Maintenance Phase is the final stage of the SDLC model where the software is updated and refined after it has been released. In the context of the video, regression testing is conducted during this phase to ensure that updates do not negatively impact the existing features of the software.

Highlights

Introduction to various testing types relevant to competitive exams, college, university exams, and interviews.

Categorization of testing types based on four levels derived from the SDLC model.

Level one testing is unit testing, conducted during the development phase focusing on the smallest software elements.

Explanation of white box and black box testing approaches, emphasizing they are not types but methods of test case design.

Integration testing as level two, combining small units to check compatibility and proper integration.

Four types of integration testing: Bang-Bang, Top-Down, Bottom-Up, and Mixed.

System testing as level three, testing the entire software or system after individual module testing.

System testing categories based on who performs the testing: Alpha, Beta, and Acceptance.

Alpha testing by the development team, Beta by friendly customers, and Acceptance by end-users.

Introduction to non-functional testing, which checks system performance parameters rather than functionality.

Types of non-functional testing including Volume, Load, Stress, Security, Configuration, and Compatibility.

Regression testing as level four, conducted during the maintenance phase to ensure upgrades do not affect existing features.

The importance of taking notes on the presented testing types for quick reference.

The uniqueness of the video's categorization of testing types not commonly found elsewhere.

The practical application of testing types in real-world scenarios, such as the car manufacturing analogy.

The significance of subscribers and sharing the video for the channel's growth.

The call to action for viewers to like, subscribe, and share the video from multiple devices.

A reminder that the video provides a comprehensive overview of testing types for last-minute exam preparation.

Transcripts

Dear Students, Welcome to Gate Smashers.

In this video,

I am going to explain various testing types

And guys, these types,

not only in your competitive exam,

even in your College

or University Exam or in interviews,

Ask you anywhere.

Each and every point

will be completed in this video.

And especially, if you are watching

this video at the last moment,

then the whole story of the testing

will be clear to you from this video.

And in this video, whatever points,

I am telling, take note of them.

Its reason is,

Because this type of categorization in a video,

you will not find it anywhere.

So I am telling you all the small points

that will help you.

So guys, immediately like the video

and subscribe to the channel,

if you haven't done it yet.

And even if you do it, do it even from

the other device and also share it.

Because subscribers are very important.

So let's get started.

Here, all the types that I have written here

Let me tell you first.

I have categorized it based on level.

So whenever you get asked

what is the type of testing,

What is the category of testing, etc?

So you have to remember simply in this way.

That we have four levels.

We categorize the types of

testing based on four levels

Now, what does this level mean?

You can say that level one

or the lowest level is unit testing.

Integration in Level Two.

System in level three.

Regression in level four.

Where did these levels come from now?

These levels actually,

the SDLC model, we have done

In that model of SDLC

We have the phase of coding

and development,

in which coding & development is taking place.

Unit testing is being done in that phase,

so first will be this.

After that, in the proper phase of testing,

in that, there will be integration testing

as well as system testing.

& after that the last phase is maintenance,

In that, there will be regression.

So these points are very important,

note them down first.

So first of all, let's go to unit testing.

So when are we doing unit testing?

When it is in the development phase,

it is in the coding phase.

So what is the meaning of this unit?

That, it is a very small unit,

very small module.

You can call a module, a function

or a code of the program

as a unit.

you say the unit is the smallest

element of the software.

So when you are testing each unit

during the development phase.

That will become the unit testing.

Here I will tell you about another category.

Many times, you will find it

in many places in this way.

Beyond this, there are two categories,

White Box Testing and Black Box Testing.

But guys, those are not its types.

It's an approach to designing a test case.

How do we design the test cases?

One way is a black box

and another way is a white box.

So in the black box,

without knowing the internal structure.

We will just give input.

And we'll check the output.

Means let's say, I have a car.

Now in that car,

I just simply drive the car and that's it.

I do not focus on the engine,

tires, and internal structure.

But in the white box,

We design the test cases

based on the internal structure and coding.

Although, we will see it in detail.

I'm just giving you an overview.

Then comes, Integration Testing.

The integration testing is done

in the proper testing phase.

Integration is known from the name itself,

that unit was small units,

when we combine those units,

it becomes integration testing.

Now it may come to your mind that sir,

when we tested the individual units,

then why are we testing them again

by combining two units?

When you test both of them separately.

So brother, here when we compared

both of them then we added both of them.

This means when we integrate unit 1 & unit 2.

After integrating,

does it properly integrated?

Or you can say when you integrate

module one & module two,

Are they compatible with each other?

You'll also have to check this thing.

That's in the integration testing.

And it has four types.

Bang-Bang, Top-Down, Bottom-Up, and Mixed

Then we have system testing.

This means, I tested the small units,

then combined them and tested the modules.

But i didn't test the entire system yet.

when your software has been created.

Now you are testing the entire

software or entire system.

I mean to say that, let's say

if we talk about the car,

first you have checked the engine,

You have checked the tires,

and you have checked the excel.

You have checked its body parts,

which means you have checked all these things.

And then you are integrating them,

you have set up the engine

Then checked it. You put tires,

wheel balancing, you did all this.

Now before launching the car in the market,

the car has been completed,

the paint, interiors, etc. have been done

Now you have to test it properly.

If you bring it on the road,

you will test it on the road.

You will test it with different drivers

and with different scenarios.

That comes in the system testing.

There are two categories in it.

it is very important.

The first categorization is

Based on.

Who is doing the testing?

Who is doing the testing?

There are three categories in it.

or you can say, it has three types.

Alpha, Beta & Acceptance

Alpha is the development team

that made that car or software.

If you are taking it from the car's point of view,

then you will easily remember it.

So the person who made that car is

actually testing the entire car itself.

Beta, friendly customers will check,

which means that like, Toyota made a car.

So, for example, their friendly customers

Let's say Toyota has a good

relationship with Ford, just for example.

So they gave it to the Ford people

that brother, use this car once and see.

Whatever lacking is there, tell us.

Just for example, I am telling you.

Then acceptance, means,

now giving that product in the hands of users.

Give it to the hand of the customer.

Now the customer will check it.

& then decide,

whether should I accept it or not.

So you remember this basic story.

Then comes to the non-functional,

All these are the functional testing.

This means to function. Function means,

how the system is actually working.

Here, we are checking the part in it.

But the performance.

Or non-functional testing,

that too is a different category of system testing.

What do we have in this category?

Volume, Load, Stress, Security,

Configuration Compatibility.

This means we are not checking it working.

You can say, We are checking its

non-functional parameters,

such as, launched the website.

Now after launching the website.

Like I gave it that

if 1,00,000 people are using it once

Then what will happen?

I gave extra load on it,

I put stress on it.

I increased the volume.

In this way when I use functioning,

What will be my response time?

If my website crashes,

at what time can I recover it?

What is the security feature?

It is not that your data is being hacked.

So how are they doing the installation?

Are there any bugs at the time of installation, etc?

So all these non-functional points

come under this testing.

That is called performance testing.

Or comes under non-functional testing.

The rest comes under functional testing.

Finally, we have the last level you can say.

That's the regression testing

which we do in the maintenance phase,

means you made a product,

For example, the customer accepts it.

The customer is using that project.

Now, after using that project,

Will it continue working as it is for 10 years?

No, now you need upgradation regularly.

You feel like you want to bring

this feature a little bit new,

as the updation comes, right?

On your mobile, web application,

you regularly get some updates,

especially in android.

So it's telling for the upgradation,

So you upgraded the system.

After upgrading, It is not that

the old features will stop working.

So this upgradation,

Whether it is useful or not.

Will it work properly?

That we check in regression testing.

We check by seeding artificial errors.

So whatever points I've told you,

These are the superficial points

which will help you. At least,

you got to know how do we

categorize all types of testing.

Otherwise, it is not known.

Some people say it's a black box & white box.

Brother, that is the test design case.

Here, The different cases we create to design the test,

what way do we do?

We use it here. So only in the unit,

you can use it in other places too.

It is a different thing.

But the types of testing,

that we do based on level.

When are we doing it?

Doing it in coding & testing

This is done in the coding phases.

These two are done in the testing phase.

This is in the maintenance phase.

So just remember these points.

These points are more than sufficient.

Thank you.