Clear? So, we did here with STLC and SDLC in the difference.
Now we will next go to Software Testing levels.
That means that if in the interview you are asked a question like how many levels are there in Software Testing and which all? They might ask a twisted question like how many levels are there in the testing.
Or it will be a normal question like how many phases are there of validation on which all are they? Clear? Your answer is there right in front of you, testing levels means Unit Testing, Integration Testing, System Testing and Acceptance Testing.
These 4 are the Software Testing levels.
Even if you tell validation testing phases names, it is the same.
Even if you are asked Software Testing levels, it is the same.
And if normal testing levels are asked this is the same, it is there in front of you.
Clear? Then what happens here? If you are asked in detail what is Unit Testing? So, you have to give the definition.
What would be the definition of Unit Testing? The smallest testable part of the software.
The small parts in the software, you check it, that is called Unit Testing or Component Testing.
Integration, with the name itself you should get to know that they are talking about integrating, means they are talking about merging.
So, what will happen in this? Integration Testing means that to merge.
You have to perform the integration testing.
Clear? You are performing the integration testing.
In this what happens is that the number of components and system, when you integrate it and do the work in the interface.
That is called as Integration Testing.
So, this kind of questions can come in front of you in the interview.
Now the next thing which will come in this is the difference between the Alpha and the Beta testing.
This question has been asked a lot of times in the interviews.
When you work for your company.
So, there Alpha testing happens.
When the work is not happening in the company and you are checking any software outside that is called as Beta.
You will call that as Beta Testing.
In Alpha Testing, it is written in front of you in the 1st line that Alpha Testing is always performed by the developers at the software development site.
What will happen in Beta Testing? Beta Testing is always performed by the customers at their own site.
It is not open to the market and the public.
Clear? Here it is mentioned, it is always open to the market and the public.
And always performed in the virtual environment.
That means that the work will not happen in the real environment.
The work happening in the company’s server in the company’s limitations is called as Virtual Environment.
And Real Time Environment means that you take any application like Facebook, Instagram, which is there on the real server and everybody is accessing it.
So, guys that is called Beta Testing.
Why? Everyone in the market has it and everyone in the market is accessing it.
So, that is called Beta Testing.
Clear? Then comes the difference between Functional and Non-functional.
Guys, this difference also has been asked many a times.
So, what is the difference between the functional and non-functional.
The functionality that is there in front of you, which you check, that is called there functional testing.
That means the testing based on analysis of the specification of functionality of the component or system.
And here testing the attribute of the component or system that do not relate to functionality.
Which means the work that is not related to functionality is called as non-functional.
The functionality related work is called as functional.
Functional Testing is executed first that means that it is performed 1st.
What happens in Non-Functional? It should be performed after the Functional Testing.
It means that after Functional Testing what happens there is Nonfunctional Testing.
After Functional Testing, what happens here is the Non- Functional Testing.
Easy to do Manual Testing and Tough to do Manual Testing.
This difference you have to keep in mind.
They can also ask that there are how many types in Dynamic Testing Method? So, guys there are 2 types in it.
Functional and Non- Functional.
Functional and Non-Functional Testing is the type of Dynamic Testing.
Clear? The next question that can come to you is that what is a Black Box? Guys, this is a very good question in this.
Black Box means, the gift that you get, a wrapped gift.
What is that? Black Box.
Do you know what is there in that gift? Did you get to know looking at the gift what is there inside it? No.
That is called the there as Black Box.
Guys, you think that there is a website in front of you, any website or any mobile application.
Do you get to know from outside in which file the data will go first and after that it will go in which file and after that in which file, are you getting to see that from outside? No.
That is a Black Box.
If you read its definition, you will easily get to know what is the answer to be given.
What is the answer you will give for Black Box Testing? Black Box Testing is a testing, yes, testing, either functional or non-functional without reference to the internal structural of the component or system.
That is called Black Box.
What is that called? That is called as Black Box Testing.
It has 4 techniques.
If you are asked in the interview, what are the techniques of Black Box? Guys there are 4 main techniques.
1st in it is Equivalence Partitioning, Boundary Value Analysis, Decision Table and the last one is State Transition Testing.
These are the 4 major techniques which comes in Black Box.
The use case that you make.
Use Case Testing can also come in Black Box.
But majorly there are 4.
Next is White Box.
When Black Box comes, we know that White Box will also follow in the interview.
So guys, what is the meaning of White Box? You can see in the internal system from where all the data will be coming.
That all you can see.
Which means you can see the code.
So, you know the internal structure of the component or system.
So, that is called over there, White Box.
Testing based on an analysis of the internal structure of the component or system having knowledge of coding.
This is the definition of White Box.
Clear? What happens in White Box, you are aware about the internal system.
Clear? You are aware of the internal system that it will 1st go here and then it will go here and then from here we are getting the output.
That is called as White Box.
In White Box there are 3 main types of techniques that are covered.
First thing that will be there in this will be, first in this is Statement Coverage, Decision Coverage and the last one is Condition Coverage.
These are the 3 types of coverage through which the White Box Testing is completely covered.
Now, the next question is Adhoc Testing.
By the name itself we get to know, Adhoc, you must have heard this word.
Like in any college a professor is hired as an Adhoc Professor.
He is not permanent.
The permanent ones and the adhoc ones are different.
You have to think as adhoc because adhoc means, they say that Adhoc Testing is an informal testing.
Why? What is its main aim? It is to break the system.
Correct? So, to break the system is called the adhoc testing.
Clear? Because the requirement that will come in it or what you will be performing, what you will test and giving will be done randomly, it will be done randomly.
Clear? You can even be asked the types in the interview.
There are 3 types of Adhoc Testing.
Buddy Testing, Pair Testing and Monkey Testing.
So, guys Monkey testing can be its other name as well.
Buddy Testing means one buddy from the development team, second from the testing team.
When both of them work together, that is called Buddy.
Pair, means when you go to buy footwear, both are same.
Answer is in the pair.
That means that both the tester working on the same model, that is called the Pair Testing.
Monkey Testing is again, random where you have to break the system.
That is easily explained with the example.
Guys, you will like it.
Smoke Testing, without this, Smoke, Sanity, Regression.
Without this question the interview does not end.
In the manual, Smoke Testing.
Smoke Testing is performed after the software build to ascertain that the critical functionalities of the program is working fine.
This is the definition.
You will have to tell this compulsorily.
After that you take an example.
For example, anything, you talk about the application.
Imagine that today What’s app has been launched in the market.
What is there in it? Chat had come for the 1st time.
So, the chat was launched here.
When the chat was launched, after that some in few days some other build was realized in the market.
Another build was also released.
What will happen now? Second build has been realized.
After releasing another build.
We have to check previous build of the critical functionality.
Message is getting properly delivered or not.
Contacts are getting refreshed.
In the 1st build the major and critical functionalities that were there.
Those you check.
That is called smoke Testing.
What comes next inside it? Sanity Testing.
After smoke the sanity comes.
Why? After receiving a software build, with minor changes in code or functionality, Sanity Testing is performed to ascertain that the bugs have been fixed and no further issues are introduced due to these changes.
So, there it is called as Sanity Testing.
What is it called? It is called Sanity Testing.
Clear? That means the new build that you have added, if the bug comes out of that, changing it and fixing it there.
You see that whether you are getting any problem anywhere.
So, that is called Sanity.
Then here comes the difference between Smoke and Sanity.
What was there in Smoke Testing? Performed by the developers or testers.
And what is there in Sanity.
That the Sanity Testing is usually performed by the testers only.
Smoke Testing is usually documented or scripted.
Sanity Testing is usually not documented and is unscripted.
Smoke Testing is the subset of Regression Testing.
Sanity Testing is a subset of Acceptance Testing.
Smoke Testing is like general health checkup.
Sanity Testing is like specialized health checkup.
Guys the example also comes into this.
If I get the CT scan of my body done.
What does that mean? The main parts of my body will be checked, which is called Smoke.
What happens in Sanity? Where there is a pain, we only get that part of the body checked.
That is called as the specialized health checkup.
Like if I am suffering from a heart attack, I will go to a heart specialist.
I won’t go to the medical shop person in my lane.
Clear? That is the kind of Sanity.
What is Regression Testing? Regression testing means what? Regression Testing means testing your software application when it undergoes a code change to ensure that the new code has not affected other parts of the software.
This is the main meaning of Regression Testing.
If you have done the changes in the code or you have developed the functionality.
After doing that in any software how much ever build has come.
It should not be affected anywhere there.
That is called as Regression.
Like what is new in the What’s app? Payment has come.
So, after the new thing, payment which was added in What’s app.
There the chat should not stop, ther emojis should not stop.
There photo sharing should not stop.
Why? Because it has the work of doing Regression.
Clear? That is an example.
If you are adding any new functionality, the previous functionality and the new thing, every thing needs to be checked.
That is called the Regression Testing.
There are 3 techniques there, which are there on your screen.
Retest All, Regression Test Selection, Prioritization of Test Cases.
Mostly in the market Retest All is used.
Check all, the testers are free.
Give it everything, regression techniques.
Now comes here Types of Defects find from Static Testing.
This is a rare question that is asked in the interview.
Why? Because if you go to any place.
There the Static Testing work comes.
You have to remove the defects from the documentation, what will you remove? Clear? We are talking about before coding.
Before doing the coding the document that is there with you, form that how will you remove the defects? So, the deviation from the standards, that is the kind of defect.