1
00:00:07,101 --> 00:00:09,557
- Now let's learn what
tests critique the product

2
00:00:09,557 --> 00:00:12,621
for fast feedback and realistic use.

3
00:00:12,621 --> 00:00:15,037
Guiding coding with testing is great,

4
00:00:15,037 --> 00:00:16,621
but we can't think of everything.

5
00:00:16,621 --> 00:00:20,541
Some testing requires the
code to actually be there

6
00:00:20,541 --> 00:00:21,915
to be complete.

7
00:00:21,915 --> 00:00:24,677
So let's look at the right
side of the quadrants.

8
00:00:24,677 --> 00:00:28,381
This side is about finding defects.

9
00:00:28,381 --> 00:00:31,080
Quadrant three, that's
kind of one of the places

10
00:00:31,080 --> 00:00:35,021
where testers have spent
their entire lives in

11
00:00:35,021 --> 00:00:36,999
traditional projects.

12
00:00:36,999 --> 00:00:39,180
But in Agile as usable
chunks are delivered,

13
00:00:39,180 --> 00:00:40,897
you can evaluate it.

14
00:00:40,897 --> 00:00:44,431
Does it meet the needs of
the business, the customer,

15
00:00:44,431 --> 00:00:45,763
the end users?

16
00:00:45,763 --> 00:00:48,039
Are we testing for the right value?

17
00:00:48,039 --> 00:00:50,904
For example, if we look
at the pet salon owner,

18
00:00:50,904 --> 00:00:53,960
are we helping them
save time on scheduling?

19
00:00:53,960 --> 00:00:56,723
When we look at the tests
in quadrant three we wanna

20
00:00:56,723 --> 00:01:00,840
think about what activities
build confidence.

21
00:01:00,840 --> 00:01:03,120
Exploratory testing is
one of the things that we

22
00:01:03,120 --> 00:01:04,961
usually think about.

23
00:01:04,961 --> 00:01:07,739
They provide feedback into
other stories, and we'll talk

24
00:01:07,739 --> 00:01:11,560
much more of them on
lesson five in exploring.

25
00:01:11,560 --> 00:01:15,141
But maybe we have iteration
reviews, the demos.

26
00:01:15,141 --> 00:01:19,363
Perhaps we pair with our
customers or our product owners.

27
00:01:19,363 --> 00:01:22,297
There's lots of different
ways that we can do testing.

28
00:01:22,297 --> 00:01:26,200
Usability testing, user
acceptance testing.

29
00:01:26,200 --> 00:01:28,424
Can the user do their work?

30
00:01:28,424 --> 00:01:31,064
We wanna do it as early as possible.

31
00:01:31,064 --> 00:01:33,581
Can we bring our users in?

32
00:01:33,581 --> 00:01:37,405
We really wanna focus on
the value to the business.

33
00:01:37,405 --> 00:01:39,464
Think back to our pet salon.

34
00:01:39,464 --> 00:01:42,719
As a busy client, you're
scheduling your pet's grooming.

35
00:01:42,719 --> 00:01:46,003
As an employee, you're
organizing your schedule and

36
00:01:46,003 --> 00:01:47,805
accommodating clients.

37
00:01:47,805 --> 00:01:51,763
How do people in different
roles, in different jobs

38
00:01:51,763 --> 00:01:53,923
use their product?

39
00:01:53,923 --> 00:01:57,821
Quadrant three is a little
interesting because we really

40
00:01:57,821 --> 00:02:01,821
wanna think about feedback
into quadrants one and two.

41
00:02:01,821 --> 00:02:04,525
What are we learning because
quadrant three is about

42
00:02:04,525 --> 00:02:07,384
learning, it's about
evaluating our product.

43
00:02:07,384 --> 00:02:11,051
When we think as real
users we tend to start

44
00:02:11,981 --> 00:02:13,899
testing differently.

45
00:02:13,899 --> 00:02:16,125
We wanna look for missing functionality.

46
00:02:16,125 --> 00:02:18,981
We might even find a defect
or two along the way.

47
00:02:18,981 --> 00:02:21,245
We wanna make it fun as well.

48
00:02:21,245 --> 00:02:23,043
For example, our pet salon.

49
00:02:23,043 --> 00:02:25,341
What if one groomer is so popular?

50
00:02:25,341 --> 00:02:27,817
Can we help her manage her schedule?

51
00:02:27,817 --> 00:02:29,864
Can we help her best clients get access to

52
00:02:29,864 --> 00:02:31,781
their favorite groomer?

53
00:02:31,781 --> 00:02:33,763
What is the value to the customer?

54
00:02:33,763 --> 00:02:35,923
What information might be useful?

55
00:02:35,923 --> 00:02:39,485
We are learning about the
product, so what we do,

56
00:02:39,485 --> 00:02:43,652
how we conduct the tests will
depend on your own context.

57
00:02:44,701 --> 00:02:46,963
Let's talk about quadrant four now.

58
00:02:46,963 --> 00:02:49,261
This is about critiquing a product still,

59
00:02:49,261 --> 00:02:51,864
but from a technology perspective.

60
00:02:51,864 --> 00:02:55,364
This is often the most forgotten quadrant.

61
00:02:56,221 --> 00:02:58,141
Business stakeholders
often assume the team

62
00:02:58,141 --> 00:03:01,499
knows what we want, performance, security,

63
00:03:01,499 --> 00:03:03,224
other quality attributes.

64
00:03:03,224 --> 00:03:06,381
However, the tests in this
quadrant might be more

65
00:03:06,381 --> 00:03:09,064
important than the actual functionality,

66
00:03:09,064 --> 00:03:11,040
and is easily overlooked.

67
00:03:11,040 --> 00:03:14,980
The early Agile books and
articles focused on customer

68
00:03:14,980 --> 00:03:17,222
and programmer tests.

69
00:03:17,222 --> 00:03:21,581
And I had testers constantly
ask me, and I'm sure

70
00:03:21,581 --> 00:03:25,241
Lisa has too, well what
about all those other kinds

71
00:03:25,241 --> 00:03:26,803
of testing?

72
00:03:26,803 --> 00:03:30,541
This model has given us
a way to talk about them.

73
00:03:30,541 --> 00:03:32,605
Here's a sample of the
tests that we categorize

74
00:03:32,605 --> 00:03:34,243
in quadrant four.

75
00:03:34,243 --> 00:03:37,123
You can see there's a lot
of different kinds of tests.

76
00:03:37,123 --> 00:03:40,781
We often talk about ility
tests, things like reliability,

77
00:03:40,781 --> 00:03:44,483
interoperability, browser compatibility,

78
00:03:44,483 --> 00:03:47,501
but there's also tests
like the data migration or

79
00:03:47,501 --> 00:03:51,965
infrastructure testing that
team don't think about.

80
00:03:51,965 --> 00:03:54,925
These can be addressed
as quality constraints,

81
00:03:54,925 --> 00:03:58,061
and we'll talk about
those in the next section.

82
00:03:58,061 --> 00:04:00,041
Why do we have to do it?

83
00:04:00,041 --> 00:04:03,565
Well, a lot of times the
non-functional, and we prefer

84
00:04:03,565 --> 00:04:06,744
the term quality attributes,
have a higher priority

85
00:04:06,744 --> 00:04:08,643
than functionality.

86
00:04:08,643 --> 00:04:11,603
Example, an airline website.

87
00:04:11,603 --> 00:04:14,722
It goes down when it's
having a huge seat sale.

88
00:04:14,722 --> 00:04:18,301
The functionality really
doesn't make any difference

89
00:04:18,301 --> 00:04:22,740
if I can't get on and buy
that seat when I want to.

90
00:04:22,740 --> 00:04:26,177
If we look at our pet
salon, it has a light load,

91
00:04:26,177 --> 00:04:28,623
so load testing is probably not important,

92
00:04:28,623 --> 00:04:32,703
but maybe the privacy
of the customer data is.

93
00:04:32,703 --> 00:04:36,660
Does you team have all of
the skills that it needs?

94
00:04:36,660 --> 00:04:39,582
It sometimes takes specialized
skills for performance,

95
00:04:39,582 --> 00:04:43,721
security, maybe data
warehousing or accessibility.

96
00:04:43,721 --> 00:04:47,023
You wanna make sure that you
have the skills on your team,

97
00:04:47,023 --> 00:04:49,780
so if you bring in a specialist,
collaborate to transfer

98
00:04:49,780 --> 00:04:50,863
those skills.

99
00:04:52,084 --> 00:04:55,418
The fit and finish of your
product is what makes the

100
00:04:55,418 --> 00:04:58,900
difference often from
yours and the competitor's.

101
00:04:58,900 --> 00:05:02,463
You will need test environments,
infrastructure tools,

102
00:05:02,463 --> 00:05:06,004
maybe a production-like
environment for load testing.

103
00:05:06,004 --> 00:05:08,541
Really look at that whole product.

104
00:05:08,541 --> 00:05:10,884
When you're planning with the quadrants,

105
00:05:10,884 --> 00:05:13,384
use them to have visual clues.

106
00:05:14,404 --> 00:05:18,660
It helps you to plan for
the right infrastructure,

107
00:05:18,660 --> 00:05:22,020
for the right people,
maybe the right skills

108
00:05:22,020 --> 00:05:23,641
when you need them.

109
00:05:23,641 --> 00:05:26,644
Use the quadrants to guide
planning for conversation,

110
00:05:26,644 --> 00:05:28,660
for priorities, right?

111
00:05:28,660 --> 00:05:31,261
If you understand and you see
what testing you need to do,

112
00:05:31,261 --> 00:05:34,281
you learn how to make them
part of what you're planning.

113
00:05:34,281 --> 00:05:37,503
We encourage you to
make your own quadrants.

114
00:05:37,503 --> 00:05:40,197
Take it, put a poster up, talk
about what testing you have

115
00:05:40,197 --> 00:05:41,780
and make it visual.

116
00:05:42,761 --> 00:05:44,921
Remember, it's a thinking tool.

117
00:05:44,921 --> 00:05:48,340
There are other models that
might work better for you.

118
00:05:48,340 --> 00:05:52,177
If the quadrants don't work,
experiment with alternatives.

119
00:05:52,177 --> 00:05:55,021
On our website, agiletesting.ca,
we have download of

120
00:05:55,021 --> 00:05:58,804
chapter eight from our second
book, and it talks a lot

121
00:05:58,804 --> 00:06:00,780
about lots of different variations.

122
00:06:00,780 --> 00:06:03,447
One of those might work for you.