<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-2482299832526920103</id><updated>2026-08-10T18:02:41.793-07:00</updated><category term="Testing principles"/><category term="introduction"/><category term="quality assurance"/><category term="software testing"/><title type='text'>Software Testing</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://softwaretestblogs.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2482299832526920103/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://softwaretestblogs.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Anuradha Kelum</name><uri>http://www.blogger.com/profile/03525821884044533603</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>2</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-2482299832526920103.post-7306244132858257270</id><published>2016-01-05T09:53:00.000-08:00</published><updated>2016-01-05T09:53:04.816-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Testing principles"/><title type='text'>Testing Principles</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOUzttNsp5cIxwanYkqTUh2OJ500feTkHtHkWB5l7x6C7ct7mFBB4s5Zbkz0rdLCzISXxQclqdk1nZoJGMWbQBE2U_rHAYPLcvdbtOWuFxilNwG7bz25QfDKdGW3d5v1gzswnb-8JDmgY/s1600/100-percent-guarantee-label_1012-118.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;320&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOUzttNsp5cIxwanYkqTUh2OJ500feTkHtHkWB5l7x6C7ct7mFBB4s5Zbkz0rdLCzISXxQclqdk1nZoJGMWbQBE2U_rHAYPLcvdbtOWuFxilNwG7bz25QfDKdGW3d5v1gzswnb-8JDmgY/s320/100-percent-guarantee-label_1012-118.jpg&quot; width=&quot;320&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
&lt;br /&gt;&lt;/h4&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
1. Testing is context dependent&lt;/h4&gt;
We need to do the testing differently for different context. As a example we do test standalone application and webpage in different manner.&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
2. Exhaustive testing is impossible&lt;/h4&gt;
Testing everything is impossible for most software product (all combination of inputs). Instead of testing everything we can prioritise test cases/ areas base on the risk attach with it.&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
3. Early testing&lt;/h4&gt;
We should start our testing activities early as possible in the SDLC, need to define objectives and goals and should be focus on to achieving defined objectives.&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
4. Defect clustering&lt;/h4&gt;
A small number of unit/module/component contains most of the defects reported before the release and found most operational failures after release.&lt;br /&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
5. Pesticide paradox&lt;/h4&gt;
&lt;div&gt;
If we run the same test case again and again, that test case will not find new bugs. To avoid this we need to update/ review/revise test cases regularly. And need to write new test cases to cover different areas where we found most bugs.&lt;/div&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
6. testing show presence of defect &amp;nbsp;&lt;/h4&gt;
&lt;div&gt;
We can show that defects are present using testing but we can&#39;t prove that there aren&#39;t defects. Testing reduces the risk of defect leakage but if there are no defect reported won&#39;t guarantee the correctness of the software.&amp;nbsp;&lt;/div&gt;
&lt;h4 style=&quot;text-align: left;&quot;&gt;
7. Absence of errors fallacy &amp;nbsp;&lt;/h4&gt;
&lt;div&gt;
Finding defect and fixing them will not help if the system/software is unstable and doesn&#39;t fulfill the customer/user expectations and requirements.&amp;nbsp;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://softwaretestblogs.blogspot.com/feeds/7306244132858257270/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://softwaretestblogs.blogspot.com/2016/01/testing-principles.html#comment-form' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2482299832526920103/posts/default/7306244132858257270'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2482299832526920103/posts/default/7306244132858257270'/><link rel='alternate' type='text/html' href='http://softwaretestblogs.blogspot.com/2016/01/testing-principles.html' title='Testing Principles'/><author><name>Anuradha Kelum</name><uri>http://www.blogger.com/profile/03525821884044533603</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOUzttNsp5cIxwanYkqTUh2OJ500feTkHtHkWB5l7x6C7ct7mFBB4s5Zbkz0rdLCzISXxQclqdk1nZoJGMWbQBE2U_rHAYPLcvdbtOWuFxilNwG7bz25QfDKdGW3d5v1gzswnb-8JDmgY/s72-c/100-percent-guarantee-label_1012-118.jpg" height="72" width="72"/><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2482299832526920103.post-4552077155102825864</id><published>2016-01-04T09:13:00.001-08:00</published><updated>2016-01-04T09:13:08.056-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="introduction"/><category scheme="http://www.blogger.com/atom/ns#" term="quality assurance"/><category scheme="http://www.blogger.com/atom/ns#" term="software testing"/><title type='text'>Introduction to software tesing</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div style=&quot;text-align: left;&quot;&gt;
&lt;/div&gt;
&lt;h2 style=&quot;text-align: left;&quot;&gt;
&lt;span style=&quot;font-family: &#39;Helvetica Neue&#39;, Arial, Helvetica, sans-serif;&quot;&gt;&lt;span style=&quot;color: #444444;&quot;&gt;Introduction&lt;/span&gt;&lt;/span&gt;&lt;/h2&gt;
&lt;h3 style=&quot;text-align: left;&quot;&gt;
&lt;span style=&quot;font-family: &#39;Helvetica Neue&#39;, Arial, Helvetica, sans-serif;&quot;&gt;&lt;span style=&quot;color: #444444;&quot;&gt;Why we need Testing&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;div style=&quot;text-align: justify;&quot;&gt;
&lt;span style=&quot;color: #444444; font-family: Helvetica Neue, Arial, Helvetica, sans-serif;&quot;&gt;&lt;span style=&quot;background-color: white; font-size: 16px; line-height: 21px; text-align: start;&quot;&gt;We all make mistakes. Some of those mistakes are unimportant. But some of them are very expensive and dangerous. So that we need to check everything we deliver as software because people make mistakes. We can make&amp;nbsp;&lt;/span&gt;&lt;span class=&quot;correction  alternate&quot; id=&quot;GingerWidget-correction-0&quot; style=&quot;background-color: white; border-image-outset: initial; border-image-repeat: initial; border-image-slice: initial; border-image-source: initial; border-image-width: initial; border: 0px; font-size: 16px; font-stretch: inherit; line-height: 21px; margin: 0px; padding: 0px; text-align: start; vertical-align: baseline;&quot;&gt;the same mistake&lt;/span&gt;&lt;span style=&quot;background-color: white; font-size: 16px; line-height: 21px; text-align: start;&quot;&gt;&amp;nbsp;if we try to find our own mistakes due to bad assumption and blind spot. So we should get someone else to check our work because another person is more likely to find mistakes. In this blog we try to explain you how&amp;nbsp;&lt;/span&gt;&lt;span class=&quot;correction  alternate&quot; id=&quot;GingerWidget-correction-1&quot; style=&quot;background-color: white; border-image-outset: initial; border-image-repeat: initial; border-image-slice: initial; border-image-source: initial; border-image-width: initial; border: 0px; font-size: 16px; font-stretch: inherit; line-height: 21px; margin: 0px; padding: 0px; text-align: start; vertical-align: baseline;&quot;&gt;doing&lt;/span&gt;&lt;span style=&quot;background-color: white; font-size: 16px; line-height: 21px; text-align: start;&quot;&gt;&amp;nbsp;the software testing.&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: justify;&quot;&gt;
&lt;span style=&quot;color: #444444; font-family: Helvetica Neue, Arial, Helvetica, sans-serif;&quot;&gt;&lt;span style=&quot;background-color: white; font-size: 16px; line-height: 21px; text-align: start;&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjonD403Qi57lw1TpiM0vIhlfq4bb4D6R2QS4hWuHD7KsieD3oPaC1-DLR-mKpWqzil8y-UcJf4vCiF1Qif2yuoOdKtPCkqxi9Sfp7HejoPDxp9w0MtZCasBZBUcA8cL8ABj-q4Sq1JO1k/s1600/scientists-in-lab_23-2147508017.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;640&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjonD403Qi57lw1TpiM0vIhlfq4bb4D6R2QS4hWuHD7KsieD3oPaC1-DLR-mKpWqzil8y-UcJf4vCiF1Qif2yuoOdKtPCkqxi9Sfp7HejoPDxp9w0MtZCasBZBUcA8cL8ABj-q4Sq1JO1k/s640/scientists-in-lab_23-2147508017.jpg&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: justify;&quot;&gt;
&lt;span style=&quot;color: #444444; font-family: Helvetica Neue, Arial, Helvetica, sans-serif;&quot;&gt;&lt;span style=&quot;background-color: white; font-size: 16px; line-height: 21px; text-align: start;&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://softwaretestblogs.blogspot.com/feeds/4552077155102825864/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://softwaretestblogs.blogspot.com/2016/01/introduction-to-software-tesing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2482299832526920103/posts/default/4552077155102825864'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2482299832526920103/posts/default/4552077155102825864'/><link rel='alternate' type='text/html' href='http://softwaretestblogs.blogspot.com/2016/01/introduction-to-software-tesing.html' title='Introduction to software tesing'/><author><name>Anuradha Kelum</name><uri>http://www.blogger.com/profile/03525821884044533603</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjonD403Qi57lw1TpiM0vIhlfq4bb4D6R2QS4hWuHD7KsieD3oPaC1-DLR-mKpWqzil8y-UcJf4vCiF1Qif2yuoOdKtPCkqxi9Sfp7HejoPDxp9w0MtZCasBZBUcA8cL8ABj-q4Sq1JO1k/s72-c/scientists-in-lab_23-2147508017.jpg" height="72" width="72"/><thr:total>0</thr:total></entry></feed>