File size: 5,013 Bytes
4bd6041 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 | 1
00:00:00,000 --> 00:00:05,000
In this session, we are going to understand build and wasn't.
2
00:00:07,000 --> 00:00:14,000
So whenever we are working on any application, I'm thinking example of a project where we are starting
3
00:00:14,000 --> 00:00:18,000
the project and we are having 20 requirements which came from that client side.
4
00:00:19,000 --> 00:00:26,000
So my developers are not going to start working on all their equipment simultaneously means if we have
5
00:00:26,000 --> 00:00:30,000
the 20 requirements, developers are not going to pick all that equipment at the start.
6
00:00:30,000 --> 00:00:37,000
Developers are going to pick one or two requirements and they will complete these requirements and then
7
00:00:37,000 --> 00:00:39,000
they can pick next set of requirements.
8
00:00:40,000 --> 00:00:45,000
So I take an example like I want to generate an email based application.
9
00:00:45,000 --> 00:00:51,000
It's quite similar to the Gmail and we are getting many requirements from the client, but the first
10
00:00:51,000 --> 00:00:57,000
developer picking registration and logging equipment, so they are generating a registration page and
11
00:00:57,000 --> 00:00:58,000
the login page.
12
00:00:58,000 --> 00:01:03,000
And I assume the registration and logging functionality has been developed.
13
00:01:05,000 --> 00:01:12,000
Now, Labor will create a small software having only registration and the login module, and they will
14
00:01:12,000 --> 00:01:14,000
deliver that software to the testing team.
15
00:01:16,000 --> 00:01:23,000
Whenever we are getting any software for the testing inside the company, we don't call it software.
16
00:01:23,000 --> 00:01:25,000
We normally call it build.
17
00:01:25,000 --> 00:01:31,000
So whenever we are getting any software, any application from the development team for the testing
18
00:01:31,000 --> 00:01:33,000
we call it, it's build.
19
00:01:35,000 --> 00:01:41,000
Every build is having a unique number, so whenever we are getting any build from the development side
20
00:01:41,000 --> 00:01:41,000
for the testing.
21
00:01:42,000 --> 00:01:46,000
So every builder is having a unique number, it could be one, two, three or four times when we are
22
00:01:46,000 --> 00:01:48,000
getting build, it will be a build one.
23
00:01:48,000 --> 00:01:51,000
Next time we are getting it to build, to build three.
24
00:01:51,000 --> 00:01:53,000
So every build has a unique number.
25
00:01:54,000 --> 00:01:58,000
I'm picking the like, I'm working on a bird when I'm testing on a big one.
26
00:01:59,000 --> 00:02:04,000
I have reported some issues, I found some bugs I reported to the development team.
27
00:02:05,000 --> 00:02:10,000
Now the team is going to fix that bug when development team fix any bug.
28
00:02:11,000 --> 00:02:13,000
They are going to deliver that fixes in the next build.
29
00:02:14,000 --> 00:02:20,000
So like if we find any bug in the build one, so maybe I'll get the solution of that bug from the developer
30
00:02:20,000 --> 00:02:24,000
in the bill too, or maybe even build three or any further build.
31
00:02:24,000 --> 00:02:30,000
So every build which we are getting from the development team can have new functionality.
32
00:02:31,000 --> 00:02:38,000
It can have only bug fixes or it can have new functionality as well as bug fixed.
33
00:02:40,000 --> 00:02:45,000
So we are getting the built in the cyclical like build one, then built to then build three.
34
00:02:47,000 --> 00:02:53,000
A point will come when we will get a bill from development team, we are going to test that bill and
35
00:02:53,000 --> 00:02:54,000
everything is working.
36
00:02:54,000 --> 00:02:59,000
All the requirement has been developed and I have tested everything is working fine.
37
00:02:59,000 --> 00:03:02,000
We are going to release that bill to the blind.
38
00:03:03,000 --> 00:03:09,000
When we release any final, stable build to the kind of testing we are going to give, any wasn't to,
39
00:03:09,000 --> 00:03:13,000
it wasn't no could be anything one two three.
40
00:03:13,000 --> 00:03:17,000
It could be any other was a name like in case of the operating system.
41
00:03:17,000 --> 00:03:22,000
We are getting the words like Windows Vista, Windows eight, Windows 10, when the 12 Windows XP.
42
00:03:23,000 --> 00:03:28,000
So this XP Vista, Windows seven eight 10, these are the words.
43
00:03:29,000 --> 00:03:35,000
Whenever we are releasing any software in the market or whenever we are giving any software to the client,
44
00:03:35,000 --> 00:03:37,000
we are giving the words a number.
45
00:03:37,000 --> 00:03:37,000
So what?
46
00:03:37,000 --> 00:03:38,000
The number could be anything?
47
00:03:41,000 --> 00:03:44,000
So here we have seen what is the difference between the build and was then?
48
00:03:45,000 --> 00:03:47,000
That's all for the session.
49
00:03:47,000 --> 00:03:48,000
Thanks for watching this video.
|