21. 21
/32
原則1:
テストは欠陥があることしか示せない
Testing can show that defects are present,
but cannot prove that there are no defects.
Testing reduces the probability of undiscovered
defects remaining in the software but, even if
no
defects are found, it is not a proof of
correctness.
22. 22
/32
原則1:
テストは欠陥があることしか示せない
Testing can show that defects are present,
but cannot prove that there are no defects.
テストにより、欠陥があることはわかるが、
欠陥がないことは示せない。
Testing reduces the probability of undiscovered
defects remaining in the software but, even if
no
defects are found, it is not a proof of
correctness.
テストにより、ソフトウェアに残る未摘出欠陥
の数を減らせるが、欠陥が摘出できない状態で
23. 23
/32
原則1:
テストは欠陥があることしか示せない
Testing can show that defects are present,
but cannot prove that there are no defects.
Testing reduces the probability of undiscovered
defects remaining in the software but, even if
no
defects are found, it is not a proof of
correctness.
24. 24
/32
原則1:
テストは欠陥があることしか示せない
Testing can show that defects are present,
but cannot prove that there are no defects.
Testing reduces the probability of undiscovered
defects remaining in the software but, even if no
defects are found, it is not a proof of correctness.
25. 25
/32
原則2:
全数テストは不可能
Testing everything (all combinations of inputs
and preconditions) is not feasible except for
trivial cases.
Instead of exhaustive testing, risk analysis and
priorities should be used to focus testing
efforts.
26. 26
/32
原則2:
全数テストは不可能
Testing everything (all combinations of inputs
and preconditions) is not feasible except for
trivial cases.
全てをテストすること(入力条件の全組み合わ
せ)は、ごく単純なソフトウェア以外では非現
実的である。
Instead of exhaustive testing, risk analysis and
priorities should be used to focus testing
efforts.
全数テストの代 わりに、リスクや優先順位に
よりテストの焦点を絞る。
27. 27
/32
原則2:
全数テストは不可能
Testing everything (all combinations of inputs
and
preconditions) is not feasible except for trivial
cases.
Instead of exhaustive testing, risk analysis and
priorities should be used to focus testing
efforts.
28. 28
/32
原則2:
全数テストは不可能
Testing everything (all combinations of inputs
and
preconditions) is not feasible except for trivial
cases.
Instead of exhaustive testing, risk analysis and
priorities should be used to focus testing efforts.
29. 29
/32
原則3:
初期テスト
To find defects early, testing activities shall be
started as early as possible in the software or
system development life cycle, and shall be
focused on defined objectives.
早く欠陥を見つけるために、テストはソフト
ウェア開発もしくはシステム開発のライフサ
イクルのなるべく早い時期に開始し、あらか
じめ定義した目的に集中すべきである。
個人ワーク
30. 30
/32
原則3:
初期テスト
To find defects early, testing activities shall be
started as early as possible in the software or
system development life cycle, and shall be
focused
on defined objectives.
個人ワーク
32. 32
/32
参考文献
• Your most unhappy customers are your greatest
source of learning.
(ビル・ゲイツの名言より)
• テストの7原則〜Seven Testing Principles
(ISTQB Foundation level syllabus
2011より)
Have a nice English life!Have a nice English life!