TechClimbs Blog

<h2>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijAkcDDJe7cAwoeUp1MrdIVvOZeoF3APMTmoFzKOzZ0jx4gfxItcU-k0A32orrnT3E0q0E__PjJq7rf7qEnN8ctA5DPjAL3hc7JMRtJk2HnCnTBbBO0LHnf2jjwhMxknlTQvjrBCBPyKo/s1600/seven+principles+of+testing.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="458" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijAkcDDJe7cAwoeUp1MrdIVvOZeoF3APMTmoFzKOzZ0jx4gfxItcU-k0A32orrnT3E0q0E__PjJq7rf7qEnN8ctA5DPjAL3hc7JMRtJk2HnCnTBbBO0LHnf2jjwhMxknlTQvjrBCBPyKo/s640/seven+principles+of+testing.png" width="640" /></a></h2>
<h2>
 </h2>
<h2>
 Testing shows presence of defects: </h2>
<ul>
<li>Testing can show the defects are present, but cannot prove that there are no defects </li>
<li>As we find more defects, the probability of undiscovered defects remaining in a system reduces ( decreasing nature). </li>
<li>However Testing cannot prove that there are no defects present </li>
</ul>
<br />
<h2>
Exhaustive testing is impossible </h2>
<br />
<ul>
<li>We have learned that we cannot test everything (i.e. all combinations of inputs and per-conditions).  </li>
<li>That is we must prioritize our testing effort using a Risk Based Approach. </li>
<li>Test designing techniques can be helpful to prioritize the tests </li>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgq_4r0sV2Bc4WaCaUnOouPlYLttl5B7ssUSN01S7kXIpsd1qRBozX8eYzJaCUvTq7_MAukGkN5gCSPbM5jboWOwN_69-zAilYYFRlg-CQbeyC8F3nO1HJapcfHDADwhcMcD2_Hv1sfBoo/s1600/Exhaustive_testing.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgq_4r0sV2Bc4WaCaUnOouPlYLttl5B7ssUSN01S7kXIpsd1qRBozX8eYzJaCUvTq7_MAukGkN5gCSPbM5jboWOwN_69-zAilYYFRlg-CQbeyC8F3nO1HJapcfHDADwhcMcD2_Hv1sfBoo/s320/Exhaustive_testing.jpg" width="319" /></a></div>
<br />
<h2>
Early testing </h2>
<br />
<ul>
<li>In the software development life cycle testing activities should start as early as possible </li>
<li>Testing activities should be focused on defined objectives – outlined in the Test Strategy </li>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEii40CUjbi0t30Ry6tkalgKXAts_eRZOFpHxhCULVF2r2WuwMmrKnMU7pte1hgBwRYej66IlxcoPehA0At20GBrvNzOo_4XD-ZZWkdn_7lstpfcqAP_6dkn2FzYSJ9stuBT7gO-ynFE1UU/s1600/eary+testing.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="221" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEii40CUjbi0t30Ry6tkalgKXAts_eRZOFpHxhCULVF2r2WuwMmrKnMU7pte1hgBwRYej66IlxcoPehA0At20GBrvNzOo_4XD-ZZWkdn_7lstpfcqAP_6dkn2FzYSJ9stuBT7gO-ynFE1UU/s320/eary+testing.png" width="320" /></a></div>
<br />
<h2>
Defect clustering </h2>
<br />
<ul>
<li>A small number of modules contains most of the defects discovered  during pre-release testing or shows the most operational failures. </li>
<li>Defects are not evenly distributed in a system, they are ‘clustered’ </li>
<li>In other words, most defects found during testing are usually  confined to a small number of modules  ( 80%  of  uncovered errors   focused in  20%  modules of the whole application) “Pareto law” </li>
</ul>
<br />
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>

<ins class="adsbygoogle"
     style="display:block"
     data-ad-client="ca-pub-6650736793190222"
     data-ad-slot="8262835391"
     data-ad-format="auto"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
<h2>
Pesticide paradox </h2>
<br />
<ul>
<li>Testing identifies bugs, and programmers respond to fix them. as  bugs are eliminated by the programmers, the software improves </li>
<li>If the same kinds of tests are repeated again and again, eventually  the same set of test cases will no longer be able to find any new bugs.  </li>
<li>Therefore we must learn, create and use new tests based  on new techniques to catch new bugs   ( i.e. It is not a matter of  repetition. It is a matter of learning and improving) </li>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEio1FB-jD20USWHx4Af2NDas4rp9Fc-QtB_qTJq3lbAH7DE79J0HILoWN3grOB_tTlunY8lESe1DxLejw3kyI5jVPNsgJBtHRxPgY5lYCuRR5mGzYrDQYCApdLtfb5XbcUUIWxKS-TroxI/s1600/pestise+paradox.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEio1FB-jD20USWHx4Af2NDas4rp9Fc-QtB_qTJq3lbAH7DE79J0HILoWN3grOB_tTlunY8lESe1DxLejw3kyI5jVPNsgJBtHRxPgY5lYCuRR5mGzYrDQYCApdLtfb5XbcUUIWxKS-TroxI/s320/pestise+paradox.png" width="320" /></a></div>
<br />
<h2>
 <div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijAkcDDJe7cAwoeUp1MrdIVvOZeoF3APMTmoFzKOzZ0jx4gfxItcU-k0A32orrnT3E0q0E__PjJq7rf7qEnN8ctA5DPjAL3hc7JMRtJk2HnCnTBbBO0LHnf2jjwhMxknlTQvjrBCBPyKo/s1600/seven+principles+of+testing.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><br />
</a></div>
</h2>
<h2>
  Testing is context depending </h2>
<br />
<ul>
<li>Testing  is basically context dependent. </li>
<li>Testing is done differently in  different contexts, different kinds of sites are tested differently.  For example, safety – critical software is tested differently from an  e-commerce site. </li>
</ul>
<br />
<br />
<h2>
Absence – of – errors fallacy </h2>
<br />
<ul>
<li>If the system built is unusable and does not fulfill the user’s  needs and expectations then finding and fixing defects does not help.</li>
</ul>
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>

<ins class="adsbygoogle"
     style="display:block"
     data-ad-client="ca-pub-6650736793190222"
     data-ad-slot="8262835391"
     data-ad-format="auto"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>

Seven Key Principles of Testing

0 ISTQB CTFL, Manual Testing, QA Process, Software Testing

Testing shows presence of defects: Testing can show the defects are present, but cannot prove that there are no defects As we find more defects, the probability of undiscovered defects remaining…

Seven Key Principles of Testing

Popular Posts

Archives

Categories