Hello, all.
Welcome to the session.
In this session, I'm going to answer software testing interview question and that is, what are the
essentials of software testing?
Let me answer the following are the essentials that are required to perform software testing?
Let me explain all this for you.
Don't.
There are mainly six essentials to perform software testing.
The first essentially is just strategy.
ESTA strategy is a foster solution.
So what is this strategy?
This strategy is all about approach.
What is your approach for testing?
How differently are going to perform testing?
Every company has its own approach.
Are we performing the testing, the complete process, our approach?
You can say, okay, well, you can employ the best practices, the differentiators and all the stuff,
how optimized you are going to perform testing.
I don't want to dig deep, but then approach goes, okay, what is your strategy?
What is your approach for performing that testing?
Okay, that is what is it's just strategy.
Then next one is, is the plan.
You see, before you do something, you need to plan the an example in the real world, if you want
to construct a building, you cannot directly construct the building.
Right.
To prepare a plan, you have to prepare a plan.
You have to think about how many days, how many workers are going to work on deck.
Who you are going to give the contract to.
A lot of things are there to plan before you start actual construction of the building.
In simple words.
In software also same thing.
Software also same thing.
You had to be able to plan how we are going to perform software testing on the given application.
Your plan in advance like well, which team is going to work, who is going to be working and which
role?
Okay, is it?
A The manager will take care of this volition.
What are the deliverables like what you are going to deliver as part of this software testing?
Then what are the artifacts that you are going to create as part of this process?
Like then what are the functionalities that are in scope, out of scope for this application?
Then how are you going to report that if defects are, it can be schedule like at what time you are
going to start and finish up the work schedule kind of things.
And then what are the different roles and responsibilities between the client and the company and the
software testing team and many other stuff?
A lot of like this.
Okay, so we'll plan in advance.
Plan in advance.
So often this strategy will create a discipline.
Okay, so that's when we'll continue all this stuff like schedule, which the work will be done and
all the stuff.
Okay.
So that is what is discipline.
Now.
Next thing, coming to the third one, we will create test cases.
As part of testing, we have to create gaskets.
You see, if you take one function, for example, if we are testing just one functionality, like log
in functionality or that log in functionality, we have to create test cases.
So we in a document auditor tool, if the company projects a tool to create the test because we will
created this test inside the tool or if we can also create the just get inside a document like Excel
Files and all those stuff.
Okay.
So for a log in functionality there can be multiple test gives us plausible.
If I was a negative test cases and many scores are possible log in with valid in log in with invalid
occurrence of log in with valid username invalid password.
Log in without providing the of log in with the invalid with an amended valid password.
Okay.
So reset the password and try to log it.
If you keep on thinking, a lot of this will come up and log in without using your mouse.
Only by using the log in.
Okay.
Like that many.
Okay.
Log in from different environments.
Different environments.
Not in a single environment like that.
Many things are possible.
But a single functionality, multiple desks are possible.
So here, as part of this gets very graphic to our test ideas for testing the each and every functionality
of the application that is there in scope as part of the discourse.
Facebook later after we created the discourse to run this discussion.
So that will the discourse will either serve in the discourse as but no problem if that fails.
Okay.
As per the given requirements, you created this test cases and while testing the test cases, if one
test case is not one of your test case are not actually according to the requirements that they have,
be behaving differently from the expectation, then we are going to report the difference.
Right.
So that's what is the role of the test gives us a distinct.
Then next one strategy is to plan best cases.
And what else we have in testing essential.
We have next one.
S S2 Database A Startup.
You see, we should not use less importance to test that.
This data plays a very important role.
Okay.
It's a very big role investing.
Okay.
So you say if you are using a normal date or something right now, if you are just repeating the date
on the fly and performing a testing, what happens?
You may get some results.
Okay.
You may think that application is working fine tomorrow.
If you get some other type of data, if you do some other type of backup is generally used in realtime
time.
What happens is you will get some defects.
Case Okay.
So there is a possibility that by changing the test data, there is a possibility of getting the defense
case.
Okay, because it may seem that application functionality is working fine at the moment.
If you go right to you would amount of data to the application.
There is a possibility that because of that new type of data, the application functionality which was
working fine, they fail this.
Okay, so we have to give good importance to test data preparation.
Okay.
Well, performing, testing, simply asking does it matter?
Okay, giving the proper data.
Well, testing is important, especially if you can give the realistic data.
Okay.
Which can be which the users will use the application real time like the type of the data that user
generally.
And then during the real time when they actually use application, that kind of data, if you are able
to prepare, okay, we will be able to find most of the difference.
Then next one is environments.
Okay, environments.
Environments.
Best environments are all the same, but I guess I'll get testing it just in the example.
If an application is given to you and that application, if you're testing in one browser, that's not
enough case, okay?
Because the not everyone will open that example.
You are testing an application Chrome browser, right?
And everything is possible.
You cannot conclude that the application itself, the application on site is working fine and testing
is completed.
We cannot say that is because every application need to be tested in all the supported environments.
The bus in real time, the users will not only use the given application in the Chrome browser, they
may use in Firefox browser.
Some people will open the browser.
Some people use exit browsers, some people use a naive browser, safari browser and so on.
Okay, so as software testers, we need to cover all the test environments, the application in all
the tests.
Okay.
So that's why it's, it's not just browsers, it's all about the operating systems.
Okay.
For example, you are yeah.
If you are testing some desktop software, the desktop software can be installed in Windows Mac and
the next different flavors of Linux and so on.
You'll see each and everything.
Each and every variation is a test.
Environmental.
It can be a browser.
Doesn't change a browser.
If again browsers are operating system different versions of operating system, different types devices.
Sometimes you have to send application in mobile device, sometimes you are tested desktop that is laptops
and all those different type of desktops.
So it's a very big story against just environment.
This involvement, we have to make sure our application is working in all the support of test environments
that generally the real public is going to use.
Fine.
Then the last one, the last testing essential is application and application under test without application.
How can we perform this application under test?
So this strategic plan this gives us does that our test involvement and application under test.
Okay.
So if you don't have the application ready for testing, how can we perform testing?
That's why I'm saying.
Application under test user testing essential.
Okay.
So these are the testing essentials that are required for performance, self-criticism, a strategy
to supplant us as a sister to just any woman and application under test.
So whole place, you got the answer for this.
So in the next session, I'm going to answer another empirical question on software testing.
Well, then I'll be.