Agile Testing Manifesto
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
3
We believe that...By that we mean...
4
1our main work product is information relevant to people who matterWe give feedback about the product as early as possible in a lean way, asking questions and providing information during pair programming to prevent bugs.We report truthfully, concisely, allowing stakeholders to make informed decisions.We rapidly uncover and report significant risks to the project.
5
2
we as testers explore the differences between perception, desire and reality
We understand that things can be different. Sometimes those differences are important. We uncover what those differences are and where they may lead to problems. We discover new information by the skilled application of exploratory testing.
6
3testing is a collaborative endeavourTesting is not delegated to testers only, but should also be done by everyone else in the team. The expertise of both testers and developers enables a broader testing coverage. We closely collaborate with developers and work side-by-side every day.
7
4learning about the domain is crucial to doing a good jobNo one has all the answers up front. Project requirements evolve over time. Rather than follow a rote plan, we learn as we test and we use what we learn to guide what we test next. We aim to understand eBay systems and share our knowledge with our peers.
8
5ignorance about the domain is not a reason not to testWe don't wait for a complete set of documentation and instructions before we start testing, but we apply good testing practices at any given time.
9
6the space between automation and manual testing is a continuumHumans excel at qualitative analysis - we notice things. Machines do quantitative analysis very well - rapidly making boolean choices. Our approach combines the two, ensuring that machines are employed for what they do best (automation, repetition and tooling), while the rest is left to humans.
10
7
developing tools for the benefit of all teams supports overall productivity
We can be more effective if shared tools are in place to optimize repetitive tasks and avoid solving the same problem multiple times. Those tools can either be sourced from outside or built in-house.
11
8metrics are a way to start a conversation and not to end itSometimes metrics are selected simply because they are easily available and not because their construct validity has been established. Misapplied metrics can cause a lot of harm. We use metrics to help us achieve results, hence we value inquiry metrics over evaluation metrics. http://www.developsense.com/blog/2009/01/meaningful-metrics/
12
9we are not the gatekeepers of qualityWe provide information to allow others to make informed decisions, including "ship" / "no ship" decisions. We highlight risks. It is up to our stakeholders to decide what to do based on that information.
13
10our approach is applicable eBay wideWe believe that an agile, embedded approach fosters close working relationships between testers and other roles. It helps deliver more value more quickly and reduces unnecessary overhead.
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
Loading...
 
 
 
Sheet1