Working with Visual Studio 2010 - Part 9

 In part 9 I show how to fix a bug reported by the tester, how the tester can verify the bug fix and finally how to close the bug.

0:00

hi my name is julio cassal and in this

0:03

video i will show you

0:04

how a developer can fix a bug reported

0:07

by a tester

0:08

how the tester can verify that that fix

0:11

and finally how he can close the back

0:13

remember we are using visual studio 2010

0:16

beta 2 and also team foundation server

0:18

beta 2

0:19

and test lab manager beta 2. so

0:23

i have received the notice that

0:26

the tester has created a new bug for me

0:30

so what i'm going to do right now is to

0:32

open visual studio

0:36

and see which are my current box

0:39

so i will log into team foundation

0:41

server

0:43

as a developer of course

0:46

okay and in the right hand side

0:50

i will go to my work items team queries

0:53

and see my bugs

0:57

you can see i do have a bug here

1:00

okay and i want to see the information

1:03

about this

1:04

let's see okay here are the steps

1:07

you can see here the steps that the

1:08

tester performed

1:10

he she opened the application didn't

1:13

enter book type

1:14

and then clicked search okay application

1:18

crashed

1:19

let's see the this attachment

1:22

let's see how how much information do we

1:24

have we can see clearly there's an

1:27

exception here apparently an argument

1:30

new exception

1:32

seems like book types not being passed

1:34

to the function

1:35

this is very useful let's continue we

1:40

can see we do have video links here

1:42

which is

1:42

really really useful so let's click here

1:45

see what what we get

1:47

you can see this is the video

1:48

reproduction of what the

1:50

the tester did while he was trying to

1:54

check this specific scenario you can see

1:57

there's the bug

1:58

he didn't just enter a book type so it's

2:01

pretty

2:03

easy to understand that okay let's just

2:06

close this for now

2:08

what else do we have here let's see

2:11

this is the test configuration windows 7

2:13

i88

2:14

the applications that were running right

2:16

in that moment

2:18

we can see this action lock

2:21

which will tell me um what specific

2:25

actions were performed

2:26

into the application okay so you can

2:29

even see

2:30

from what directory the application was

2:32

was run and most importantly

2:34

for each step which steps were performed

2:37

so for example for click search

2:40

okay here the the user first click at

2:42

the main window title bar then click at

2:44

search

2:46

okay then well um well then just click

2:49

the close button

2:51

because this is not really recording the

2:53

actual the actual order

2:54

uh windows dialog that uh that was

2:57

opened

2:58

so let's just close this we do have some

3:01

more

3:02

system information that we can actually

3:03

see here in system info

3:05

we can know that the no the name and the

3:08

domain of the

3:09

the machine the version windows version

3:12

you can see that the locale of windows

3:16

the available memory you know a lot of

3:18

information related to the computer

3:20

which

3:20

is also really useful we can also see

3:23

the test cases

3:25

that are associated with this specific

3:29

bug you can see this is the this case

3:31

that the tester was trying to

3:33

to to perform and here are all the links

3:36

related to to this back

3:39

okay so now that that we saw all that

3:41

information maybe we can just

3:42

fix this back so let's close this

3:46

and let's go to this employee

3:47

consultations bookstore

3:54

okay

3:58

so here we are

4:01

and now let's run the application see if

4:04

we can reproduce the bug

4:06

okay we're going to debug the

4:08

application

4:11

starting right now

4:20

okay there we are we will not enter a

4:24

book type and click search

4:31

so there's the bug you can see

4:36

value cannot be new okay

4:39

this this window in the right side which

4:41

is the new intelli trace

4:43

it would allow you to just jump back to

4:46

any specific point in the application

4:48

if er the applica the information that

4:51

you're receiving right now is not really

4:52

enough for you

4:54

so for example i can i can go back to

4:57

the deception

4:58

to this order section to click it search

5:02

you see you can go back as much as you

5:05

want

5:06

okay this is really not really

5:09

complicated

5:10

so it's pretty obvious that this book

5:12

type is not coming not really coming

5:15

okay so going back to the main

5:19

window.saml we can see that this text is

5:22

going blank

5:22

so it's pretty easy to fix let's just

5:25

stop this

5:29

fix this quickly so let's just say

5:34

you know we do have another another

5:37

function

5:38

which is this one get booked list that

5:40

will not uh

5:41

will not ask for any book type but will

5:43

just return

5:44

all the books that that's the one that

5:46

we want right here

5:48

so

5:51

let's just uh do this

5:56

okay you can see i just checked it out

5:59

the the source code and the right side

6:01

because i'm going to make change

6:04

let's say if

6:07

string dot is null or

6:10

empty

6:13

type text box that text

6:17

okay we will do something

6:23

else we will do what we were just doing

6:28

what we will do if there's

6:31

no text in the type text box let's just

6:34

return all books

6:35

which should fill the requirement okay

6:38

now let's run this again

6:43

click search okay wait a little bit

6:48

and there we go there's all the

6:51

information from all the books

6:53

so we just fixed this bug what we have

6:56

to do now is to

6:57

check in this change

7:01

of course always associating this

7:04

checking

7:04

with the appropriate work item in this

7:06

case it will be this bug

7:08

box 47 i will just resolve this this bug

7:12

and click check in

7:18

okay that's good let's close

7:22

close all these documents and now let's

7:24

take the role of the tester that wants

7:26

to verify

7:27

that the bug has actually been resolved

7:31

so let's open test lab manager

7:34

let's login as the as a tester

7:44

okay now let's go to the

7:48

track tab and let's say if we have any

7:52

new bug assignment

7:53

to us as a tester let's click run and

7:56

there you go we do have a resolved bug

7:59

which is bug 47 that is associated to

8:01

our test

8:02

so let's see if that is true let's go to

8:04

test

8:05

and let's try to run this again okay

8:08

let's

8:10

run

8:14

this time we don't really need to create

8:15

an action recording we just want to

8:17

to round the steps in the test see if it

8:21

passes okay let's

8:25

open bookstore

8:35

there we go do not okay open application

8:39

passes do not enter a book type passes

8:42

and now

8:42

let's click search wait a little bit

8:56

and there we go the information is right

8:58

there so we can say that

9:00

this last step just pass it and end the

9:03

test

9:06

let's close this

9:11

okay then now going back to this

9:15

this this main ui window

9:18

you can see the test is now marked as

9:20

passed the green bar is here

9:23

and we can also go to the tracking

9:25

tracking window

9:27

go to my box open this this box and mark

9:30

this as

9:32

closed safe and close and that's it

9:36

so i hope you like this like this i'll

9:38

see you again in the next video

9:40

see you again