Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SQA Training 2


Published on

Training session 2, about the basic concepts of Software Quality Assurance, which I have conducted for 3rd year and final year students of CSIT department at NED University.

Published in: Technology, Education
  • Be the first to comment

SQA Training 2

  1. 1. Software Quality Assurance<br />(Session 2 @ CSIT Department, NED University)<br />Trainer: Faiza Yousuf<br />
  2. 2. Today’s Focus<br />Test Cases<br />Field Validation<br />Login Page Test Cases<br />GUI Testing and Components<br />Examples of BAD UI Design <br />Exercise<br />CV Writing <br />Tuesday, May 31, 2011<br />2<br />
  3. 3. Test Case<br />A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not.<br />Tuesday, May 31, 2011<br />3<br />
  4. 4. Test Case Format<br />Test Case Title (Refers to the Functionality of the product being tested)Test Case version( Required when multiple changes takes place in the product and the Test Case as well)<br />Step No (Sequence used for no of test steps in the Test Case)<br />Test Step (Actual step to be followed or executed)<br />Expected Result ( Result which is expected as a normal behavior) <br />Actual Result ( Result which we actually get after we execute the test step)<br />Tuesday, May 31, 2011<br />4<br />
  5. 5. Test Case Format (Cont.)<br />Defect id ( If the Expected and Actual result do not match then we need to log a defect either in a Defect logging tool or by maintaining an Excel sheet of defect incurred. The corresponding id generated for the defect logged should be mentioned in this column so that we can get the exact track of which defect is logged against the said Test Case.) <br />Test Step result ( Whether the step is Passed or Failed is to be mentioned here) <br />Tuesday, May 31, 2011<br />5<br />
  6. 6. Field Validations<br />Check whether the field is mandatory or not.<br />Check for the uniqueness of the field.<br />Check whether the field is auto generated or not.<br />Check its length and input type.<br />Check that the field label is correct, concise and understandable with no spelling/grammatical errors.<br />Check the error/alert messages on fields.<br />Smart validation should be applied to the fields e.g. “Date” and “Email” fields.<br />User guidance should be given for maximum fields.<br />Tuesday, May 31, 2011<br />6<br />
  7. 7. Test Cases for a login page<br />Tuesday, May 31, 2011<br />7<br />
  8. 8. GUI Testing<br />In software engineering, graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its written specifications.<br />Tuesday, May 31, 2011<br />8<br />
  9. 9. Major GUI Components<br />Text boxes<br />Radio Buttons<br />Check boxes<br />Push Buttons<br />Drop downs / Pull down menus<br />Combo Box<br />List Boxes<br />Tuesday, May 31, 2011<br />9<br />
  10. 10. USER:<br />PW.<br />LOGIN<br />RESET<br />Tuesday, May 31, 2011<br />10<br />
  11. 11. Examples of BAD UI Design<br />Tuesday, May 31, 2011<br />11<br />
  12. 12. Examples of BAD UI Design (Cont.)<br />Tuesday, May 31, 2011<br />12<br />
  13. 13. Examples of BAD UI Design (Cont.)<br />Tuesday, May 31, 2011<br />13<br />
  14. 14. Can anyone test this for me?<br />Tuesday, May 31, 2011<br />14<br />
  15. 15. Let’s Hop to C.V. Writing Stuff!<br />Tuesday, May 31, 2011<br />15<br />
  16. 16. Questions?<br />Tuesday, May 31, 2011<br />16<br />
  17. 17. Thanks for participating!<br />Tuesday, May 31, 2011<br />17<br />You can reach me at or find me at LinkedIn.<br />