In this session, we are going to understand build and wasn't.
So whenever we are working on any application, I'm thinking example of a project where we are starting
the project and we are having 20 requirements which came from that client side.
So my developers are not going to start working on all their equipment simultaneously means if we have
the 20 requirements, developers are not going to pick all that equipment at the start.
Developers are going to pick one or two requirements and they will complete these requirements and then
they can pick next set of requirements.
So I take an example like I want to generate an email based application.
It's quite similar to the Gmail and we are getting many requirements from the client, but the first
developer picking registration and logging equipment, so they are generating a registration page and
the login page.
And I assume the registration and logging functionality has been developed.
Now, Labor will create a small software having only registration and the login module, and they will
deliver that software to the testing team.
Whenever we are getting any software for the testing inside the company, we don't call it software.
We normally call it build.
So whenever we are getting any software, any application from the development team for the testing
we call it, it's build.
Every build is having a unique number, so whenever we are getting any build from the development side
for the testing.
So every builder is having a unique number, it could be one, two, three or four times when we are
getting build, it will be a build one.
Next time we are getting it to build, to build three.
So every build has a unique number.
I'm picking the like, I'm working on a bird when I'm testing on a big one.
I have reported some issues, I found some bugs I reported to the development team.
Now the team is going to fix that bug when development team fix any bug.
They are going to deliver that fixes in the next build.
So like if we find any bug in the build one, so maybe I'll get the solution of that bug from the developer
in the bill too, or maybe even build three or any further build.
So every build which we are getting from the development team can have new functionality.
It can have only bug fixes or it can have new functionality as well as bug fixed.
So we are getting the built in the cyclical like build one, then built to then build three.
A point will come when we will get a bill from development team, we are going to test that bill and
everything is working.
All the requirement has been developed and I have tested everything is working fine.
We are going to release that bill to the blind.
When we release any final, stable build to the kind of testing we are going to give, any wasn't to,
it wasn't no could be anything one two three.
It could be any other was a name like in case of the operating system.
We are getting the words like Windows Vista, Windows eight, Windows 10, when the 12 Windows XP.
So this XP Vista, Windows seven eight 10, these are the words.
Whenever we are releasing any software in the market or whenever we are giving any software to the client,
we are giving the words a number.
So what?
The number could be anything?
So here we have seen what is the difference between the build and was then?
That's all for the session.
Thanks for watching this video.