1 |
On 4 October 2013 05:11, "Paweł Hajdan, Jr." <phajdan.jr@g.o> wrote: |
2 |
|
3 |
> Even then, no amount of testing guarantees lack of problems. |
4 |
|
5 |
|
6 |
Indeed, but which is a better assurance, "5 testers tested this combination |
7 |
and nothing bad happened", or "5000 people tested this combination and |
8 |
nothing bad happened". |
9 |
|
10 |
Now, if you were to see "no people have successfully built combination X", |
11 |
that in itself is interesting, even if you don't have actual failure |
12 |
reports of that combination. |
13 |
|
14 |
Also, if "5 testers tested this combination and nothing bad happened" is |
15 |
combined with "however, we have 200 similar installation failures reported |
16 |
for this combination", you've got some context for research you need to do |
17 |
to understand why those failures exist ( even if none of them managed to |
18 |
file a bug report ). |
19 |
|
20 |
Essentially, I'm saying we need to lower the thresholds to providing |
21 |
reliable feedback about what is happening with packages in the field, ie: |
22 |
Diego's smoke boxes are very very useful, but thats *one* person. Imagine |
23 |
if we can get 500+ people running similar smoke operations with a |
24 |
manageable feedback system. |
25 |
|
26 |
That would give us fare more assurance than the arch testers are likely to |
27 |
be able to provide. |
28 |
|
29 |
|
30 |
-- |
31 |
Kent |