Differences

This shows you the differences between two versions of the page.

--- software_carpentary2 [2011/06/20 03:35]
medhamsh created
+++ software_carpentary2 [2011/06/20 03:57]
medhamsh
@@ Line 3: / Line 3: @@
 The more you invest in quality, the less time it takes to develop working software.\\
- Quality is not just testing\\
+Quality is not just testing\\
+Trying to improve the quality of software by doing more testing is like trying to lose weight by weighing yourself more often. (Steve McConnell)\\
-    Trying to improve the quality of software by doing more testing is like trying to lose weight by weighing yourself more often. (Steve McConnell)\\
 Quality is:
@@ Line 17: / Line 16: @@
     * Suppose you have a function that compares two 7-digit phone numbers, and returns True if the first is greater than the second
-          o 1072 possible inputs
+    * 1072 possible inputs
-          o At ten million tests per second, that's 155 days
+    * At ten million tests per second, that's 155 days
     * If they're 7-character alphabetic strings, it's 254 years
           o Then you move on to the second function...
-    * And how do you know that your tests are correct?
+             * And how do you know that your tests are correct?
     * All a test can do is show that there may be a bug
+===== Nomenclature =====
+A unit test exercises one component in isolation
+    * Developer-oriented: tests the program's internals
+An integration test exercises the whole system
+    * User-oriented: tests the software's overall behavior
+Regression testing is the practice of rerunning tests to check that the code still works
+    * I.e., make sure that today's changes haven't broken things that were working yesterday
+    * Programs that don't have regression tests are difficult (sometimes impossible) to maintain
+===== Test results specifications =====
+Any test can have one of three outcomes:
+    * Pass: the actual outcome matches the expected outcome
+    * Fail: the actual outcome is different from what was expected
+    * Error: something went wrong inside the test (i.e., the test contains a bug)
+          o Don't know anything about the system being tested
+A specification is something that tells you how to classify a test's result
+    * You can't test without some sort of specification
+===== Writing Tests =====
+How to write tests so that:
+   * It's easy to add or change tests
+  *  It's easy to see what's been tested, and what hasn't
+A test consists of a fixture, an action, and an expected result
+          o A fixture is something that a test is run on
+          o Can be as simple as a single value, or as complex as a networked database
+Every test should be independent
+          o I.e., the outcome of one test shouldn't depend on what happened in another test
+          o Otherwise, faults in early tests can distort the results of later ones
+So each test:
+          o Creates a fresh instance of the fixture
+          o Performs the operation
+          o Checks and records the result
+Find the exercises at http://software-carpentry.org/3_0/qa.html
+====== Reading Code ======
+Read the following code and test!
+<code>
+void main()
+{
+char str[40];
+int i,flag=0,len;
+clrscr();
+printf("\n Enter A string : ");
+gets(str);
+len=strlen(str);
+for(i=0;i<(len/2);i++)
+{
+if(str[i]!=str[len-1-i])
+{
+flag=1;
+break;
+}
+}
+if(flag==1)
+{
+printf(" \n The string is not palindrome");
+}
+if(flag==0)
+printf("\n String is palindrome");
+getch();
+}
+</code>

Swecha Wiki

User Tools

Site Tools

Differences

Page Tools