![Write test case Exercise
There is a simple program with the following items:
0 Input Box A
0 Input Box B
0 Add button
0 Result Text Box [=A+B]
0 Identify all the test cases for the program. [Example:
press the Add button without entering anything in
Input Box A and B]](https://image.slidesharecdn.com/qaoverview-160730191517/85/QA-overview-24-320.jpg)
QA overview
- 2. Quality assurance, Quality control Quality Management Quality Assurance Quality Control
- 6. Validation and Verification 0 Validation - Are we doing the right thing? 0 Verification - Are we doing the thing right?
- 7. Bug Severity and bug priority Low Severity High Priority Low Severity Low Priority High Severity Low Priority High Severity High Priority
- 8. We have an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. 0 A fault while calculating yearly report. 0 A fault while calculating weekly report. 0 A spelling mistake on the weekly report. 0 A spelling mistake on the yearly report.
- 9. Bug Severity and bug priority Low Severity High Priority Low Severity Low Priority High Severity Low Priority High Severity High Priority A fault while calculating yearly report. A fault while calculating weekly report. A spelling mistake on the weekly report. A spelling mistake on the yearly report.
- 11. Testing Principles 0 Testing shows presence of defects 0 Exhaustive testing is impossible 0 Early testing 0 Defect clustering 0 Pesticide paradox 0 Testing is context dependent 0 Absence-of-errors fallacy
- 13. Testing levels 0 Unit testing 0 Component testing 0 Integration testing (System, Component Integration) 0 System testing 0 Acceptance testing 0 User acceptance test 0 Compliance acceptance testing (Contract) 0 Alpha testing 0 Beta testing
- 14. Testing process activities 0 Test planning and control 0 Test analysis and design 0 Test implementation and execution 0 Evaluating exit criteria and reporting 0 Test closure activities
- 15. Software development models 0 The waterfall model 0 V model 0 Iterative development model
- 17. V Model
- 19. Testing types (the targets of testing) 0 Testing of software structure/architecture (structural testing) 0 Testing related to changes (confirmation and regression testing) 0 Testing of function (functional testing) 0 Testing of software product characteristics (non- functional testing)
- 20. Non-functional testing 0 Compatibility testing 0 Load, performance testing 0 Volume testing 0 Scalability testing 0 Localization and Internationalization testing 0 Security testing 0 Usability testing 0 Recovery testing
- 21. Testing process activities 0 Test planning and control 0 Test analysis and design 0 Test implementation and execution 0 Evaluating exit criteria and reporting 0 Test closure activities
- 22. Test cases classification 0 Functional 0 Positive 0 Negative 0 Non functional
- 23. Test case template Test Case details Title ID Description Owner Automated Priority Requirement Tested Procedure (Details) PassFail Criteria (Details)
- 24. Write test case Exercise There is a simple program with the following items: 0 Input Box A 0 Input Box B 0 Add button 0 Result Text Box [=A+B] 0 Identify all the test cases for the program. [Example: press the Add button without entering anything in Input Box A and B]
- 25. Bug tracking 0 Direct contact with the developer 0 Emails 0 Shared excel sheet 0 Bug tracking system
- 26. Bug life Cycle
- 27. Bug template ID Steps to produce the bug expected result result Severity status date comment Assignee Reporter Catastrophic . Severe . Moderate . Minor . Cosmetic . Enhancement .
- 28. Exercise 1 - Find more than 20 defects (layout inconsistencies, spelling errors, and the like) in the image below:
- 29. Tips to make your software testing run smoothly 0 Learn to analyze your test results thoroughly. 0 Learn to maximize the test coverage 0 break your application into smaller functional modules. 0 write test cases for the intended functionality 0 Think positive 0 Write your test cases in requirement analysis 0 Make your test cases available to developers 0 group your test cases for regression testing 0 Performance testing is the critical part of many applications 0 Programmers should not test their own code 0 Go beyond requirement testing.
- 30. Things that tester must know 0 Defect may appear in any place 0 Defects may have common cause 0 Learning is very important 0 Don’t assume ask 0 You may be wrong 0 Log every thing
- 35. Example
- 37. Example Assume the following rules apply to loans: The minimum loan amount is $5,000. The maximum loan amount is $1,000,000. The minimum property value is $25,000. The maximum property value is $5,000,000
- 38. Decision Tables Conditions Rule 1 . . . . . . . Actions . . .
- 39. Example 0 If you are a new customer opening a credit card account, you will get a 15% discount on all your purchases today. 0 If you are an existing customer and you hold a loyalty card, you get a 10% discount 0 If you have a coupon, you can get 20% off today (but it can't be used with the 'new customer' discount).
- 40. Solution
- 41. State-Based Testing and State Transition Diagrams 0 Example : Access bank account using ATM
- 42. Use Case Testing 0 Example : Access bank account using ATM
- 43. Choosing a test technique 0 The internal factors : 0 Models used 0 Tester knowledge I experience 0 Likely defects 0 Test objective 0 Life cycle model 0 The external factors : 0 Risk 0 Customer I contractual requirements 0 Type of system 0 Regulatory 0 Time and budget
- 44. Q & A