---Presenter: Christian PapicSubject: How to Test the Happy PathDuration: 00:05:08## Related ResourcesFailed QA Ticket PolicyUnderstanding Azure Dev Ops Ticket/User Story StatusesInitial Setup of QA and Staging Sites - Ben How to handle QA failed tickets?Dealing With ImpedimentsCode Complete Tasks/ QA Walkthrough---00:00:05.980 --> 00:00:09.592
So now I will show you, yeah,
the way to do it from Azure.00:00:10.330 --> 00:00:14.050
So let's say you know user snap
is not set up on a project and00:00:14.050 --> 00:00:16.034
will just use DF 02. We use the00:00:16.034 --> 00:00:20.052
same site, OK? So you go
here. Same thing you go00:00:20.052 --> 00:00:21.024
into the backlog.00:00:22.170 --> 00:00:26.112
Also, all project backlog you
click new work item.00:00:27.250 --> 00:00:30.552
And you can select what type of
ticket is like. Again, for QA00:00:30.552 --> 00:00:33.854
it's almost always going to be a
bug ticket, you know. So you00:00:33.854 --> 00:00:37.156
gonna go ahead bug first thing
to do when creating it. This is00:00:37.156 --> 00:00:40.458
going to be the title you always
put in brackets. What project it00:00:40.458 --> 00:00:41.982
is. So we'll just say core.00:00:43.050 --> 00:00:46.975
And we'll say Azure Test00:00:46.975 --> 00:00:49.920
ticket ticket. OK.00:00:50.550 --> 00:00:53.250
Then you're going to add it
to the top. And unlike user00:00:53.250 --> 00:00:55.500
snap, where it actually comes
in at the very bottom.00:00:56.810 --> 00:00:59.670
It comes in at the top here,
and I'm pretty sure you can00:00:59.670 --> 00:01:02.090
toggle different. You add to
bottom if you wanted. I don't00:01:02.090 --> 00:01:04.950
know why you'd want to add it
to bottom. You have to scroll,00:01:04.950 --> 00:01:07.370
but there you go, so there's
your ticket and it comes00:01:07.370 --> 00:01:09.790
through with no details at
first, so you would have to00:01:09.790 --> 00:01:12.210
click into the ticket and
similar to the way we modified00:01:12.210 --> 00:01:15.070
the user snap ticket, we would
go in if you wanted to modify00:01:15.070 --> 00:01:17.710
the title for whatever reason.
All you gotta do is click in00:01:17.710 --> 00:01:20.350
and edit unassigned. Same thing
will go, will sign it to Maine.00:01:21.600 --> 00:01:23.466
Add the tag same exact way.00:01:24.520 --> 00:01:27.700
4. Iteration, same thing.00:01:29.670 --> 00:01:33.375
This is very serious that if
your state is new, you put your00:01:33.375 --> 00:01:36.510
project manager said it right
here and you would link your00:01:36.510 --> 00:01:38.505
parents. Take it if you had one.00:01:39.270 --> 00:01:43.534
So you would just have to do
the repro steps in the testing00:01:43.534 --> 00:01:46.814
steps manually. So for
example, let me pull this to00:01:46.814 --> 00:01:50.094
the other window in the
meantime, so same thing. Let's00:01:50.094 --> 00:01:53.702
say I found an issue on the
site. People have different00:01:53.702 --> 00:01:56.654
versions of like screenshot
software. I use the snipping00:01:56.654 --> 00:02:00.262
tool because it's free. It's
free and easy, but anybody you00:02:00.262 --> 00:02:03.214
can basically take a
screenshot however you want on00:02:03.214 --> 00:02:07.150
the page. Sorry I don't know
where it just went. There we00:02:07.150 --> 00:02:09.446
go, so I would click new snip.00:02:10.750 --> 00:02:13.680
So go ahead and drag
the box over the area00:02:13.680 --> 00:02:14.852
I want to screenshot.00:02:16.750 --> 00:02:20.566
And it also does have marking
features not quite as well as00:02:20.566 --> 00:02:24.700
user snap, but you can see him
up here. So say there's a00:02:24.700 --> 00:02:27.880
problem with the name. Go
ahead and circle it circle00:02:27.880 --> 00:02:31.378
there. That's terrible circle,
but you get the idea. Yeah, so00:02:31.378 --> 00:02:32.968
I would copy my screenshot.00:02:34.780 --> 00:02:35.680
Close this.00:02:37.690 --> 00:02:40.570
Let me bring over the other
window with Azure.00:02:45.950 --> 00:02:50.268
Instead. Usually I log
everything in the repro steps,00:02:50.268 --> 00:02:53.909
repro steps in testing steps
overlap for the most part. So00:02:53.909 --> 00:02:57.881
usually what I would do to
create a ticket just like in00:02:57.881 --> 00:03:01.875
user snap, sorry. You take the
URL of the site.00:03:05.010 --> 00:03:07.660
That's usually the first thing
your Gonna Post in the00:03:07.660 --> 00:03:09.780
repressive people know what
environment you're testing in.00:03:11.290 --> 00:03:14.400
Next you would post the
credentials you used to test.00:03:14.400 --> 00:03:17.821
Some things are guest you know
specific or not logged in00:03:17.821 --> 00:03:20.931
specific versus logged in
specific, so I would just says00:03:20.931 --> 00:03:21.864
the admin credentials.00:03:22.970 --> 00:03:23.640
Used00:03:26.110 --> 00:03:30.169
that's when I would go ahead.
You can either put your00:03:30.169 --> 00:03:33.859
description first or the
screenshot. Usually I put the I00:03:33.859 --> 00:03:37.180
put my description for some QA
test bug screenshot.00:03:38.000 --> 00:03:41.378
OK, go in you simply paste.00:03:42.070 --> 00:03:44.473
Oh sorry, I forgot to copy
the URL last.00:03:46.190 --> 00:03:49.118
So just for demo sake, let me go
ahead. Take another screenshot.00:03:52.320 --> 00:03:52.930
Boom00:03:54.530 --> 00:03:55.900
copy screenshot.00:04:02.520 --> 00:04:03.400
Go ahead.00:04:04.660 --> 00:04:06.750
Simply Post that right there.00:04:09.490 --> 00:04:13.247
Yeah, that's pretty much it.
Like I said, if you want to tag00:04:13.247 --> 00:04:16.426
out your PMC, usually you do
that in the discussion portion00:04:16.426 --> 00:04:17.871
you like. Click high priority.00:04:18.740 --> 00:04:20.078
Please take a look you know.00:04:24.310 --> 00:04:27.046
I'm actually not going to save
this because it's going to send00:04:27.046 --> 00:04:30.010
him an email every time you tag
a PM, but essentially you would00:04:30.010 --> 00:04:32.746
set it up the same. Yeah, that's
that's another thing to note.00:04:32.746 --> 00:04:35.254
Every time you tag somebody's
name, it's going to send an00:04:35.254 --> 00:04:37.534
email to their clarity email
address so they get notified00:04:37.534 --> 00:04:40.631
right away. So yeah, that is
pretty much the Gist of it. You00:04:40.631 --> 00:04:43.046
would save and close. Let me get
rid of Clint just so I can show00:04:43.046 --> 00:04:45.260
you. Where it saves.00:04:49.560 --> 00:04:51.765
And boom, Erika still
right there at the top.00:04:53.220 --> 00:04:55.556
Let me click in and just
remove this.00:04:58.540 --> 00:04:59.460
We don't have that.00:05:02.570 --> 00:05:02.960
Hey.00:05:05.460 --> 00:05:07.920
Yeah, and that is the way you're
gonna do it, the Azure.