Welcome to the testing world in this session.
We need to understand what is software testing, so we are going to understand this process in three
steps.
So first of all, we start with software testing can be defined as a process, but does the application
under different conditions?
OK, here we need to understand.
What do you mean by the different conditions?
OK.
Let me move to my application and here I'm just logging out.
So that's my application, and I'm on the login page of my application.
Now I have a task to test this login functionality of the application.
So my first condition would be I'm just putting correct username and correct password.
That's my first condition.
No, in this case, users should be logged in.
Then I'm going for second condition in which I'm giving correct username but incorrect password.
We should not login in that third condition could be we are giving incorrect username, but correct
password.
No, I'm trying to log in.
So that's my third condition now.
My fourth condition is I'm just leaving username bank and giving the correct password.
Now I'm going to check.
So if you see, we're testing our application with different conditions and these conditions involved
positive as well as negative conditions.
Positive means we're giving correct input.
We are following correct steps.
Negative means we are giving incorrect input, incorrect steps.
So here first step is software testing can be defined as a process in which we test our application
under different conditions.
Second is over a period of time.
OK, what does it mean if we started the application today?
Maybe after one month, you get some functionality to test.
So I take an example of the project.
You started on 1st 1st of Gen.
We got the registration page on 1st of Web to test it.
Now we complete the testing of that page.
It's not like we will not start again.
We have to test the same thing again and again many times until we deliver that application to the client.
So we are testing that same thing over a period of time again and again in the cyclically.
So perform testing in the cyclically until you deliver application to the client.
And third point, which is most important evaluating the result.
OK.
What does it mean?
It means whenever we are testing, we have two outputs.
One is expected result and other what is actually the third?
OK.
Let me take you to one more scenario.
So I'm here on the on another application and there is a search functionality.
OK, I'm searching here, iPhone as I click on the search button.
We should get some results, but I'm getting only one result is this functional is working correctly
because we are getting results.
So is this is it working correctly?
I don't know, because it might be possible.
As expected, we should get five result, but we are getting only one result.
So the point is, before going for the testing, we should have expected results and these expected
results will come from the client requirement.
So first of all, we understand the client requirement.
And from there, we get expert result when we are testing our application.
We're getting actual results at the end of each scenario, which we are testing.
We're comparing actual results with expected results.
If it is passed, then testing as fast as it is filled, so expect a result is taken from the client
requirement.
Actual results coming from the application.
When we are testing, we need to compare and evaluate it is bust or not.
So here, if I take an example, my expected result was when you search for the iPhone, we should get
five results.
We should get five iPhones.
But we are getting only one means testing is available here.
But if you're expecting only one result and we are getting one result means testing is passed.
So here what?
Each testing which we are doing, we need to compare results with expected result.
So here we have seen a basic definition, a practical definition.
Also, software testing here, we understand software testing with three simple points.
That's all we have for the session.