Sangeetha Vairavel

275 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
275
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sangeetha Vairavel

  1. 1. Testing Concepts
  2. 2. Agenda Intro Testing Methods Testing Steps Testing Types Testing ModelsMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 2
  3. 3. Intro to testing What? Why? How? When? Who?Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 3
  4. 4. Testing Methods White Box Testing Black Box Testing Grey Box TestingMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 4
  5. 5. White Box Testing White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 5
  6. 6. Black Box Testing Black box testing treats the System/software as a "black box"—without any knowledge of internal implementation.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 6
  7. 7. Grey Box Testing Grey Box testing is a partial combination of both white box and black box testing.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 7
  8. 8. Steps in Testing(STLC) Requirment Analysis Test Planning Test Execution Test Reporting Test Result Analysis Defects Retesting Test ClosureMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 8
  9. 9. Testing Types Unit Testing Integration Testing Regression Testing Acceptance Testing Ad Hoc Testing Security TestingMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 9
  10. 10. Unit Testing •In Software Testing:  Done after completing a new Module. Test the new Module alone •In TBA: Done after completing new provision change. Test the new provision work as expectedMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 10
  11. 11. Integration Testing •In Software Testing:  Done after joining new Module to the product. Test the connectivity of new module with old modules •In TBA: Done in master test (C) database. Test all the provisions connected with the new changes.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 11
  12. 12. Regression Testing •In Software Testing: Test to make sure old features have not been affected by the addition of new module. •In TBA: Done after the provisions are moved to staging. Test the new changes works as in Staging (Z)Database.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 12
  13. 13. Acceptance Testing Final testing before delivering to client. Classified as:  Alpha Testing  Beta Testing •In Software Testing: Alpha - Product used inside the company Beta – Launching a Beta Version •In TBA: Alpha - Prod Verification Beta - ??????Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 13
  14. 14. Ad Hoc Testing Not a formal Testing. Wont have a test plan. •In S/W testing: Testing of a module which is added at the end of delivery. •In TBA: Testing done when a defect is solved.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 14
  15. 15. Security Testing Done by the admin team. To control hacking. •In S/W testing: Confidential product will be tested. •In TBA: Most important testing as TBA contain personal datas.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 15
  16. 16. Testing Models Waterfall Model Spiral Model V-Shaped ModelMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 16
  17. 17. Waterfall Model The waterfall model is a sequential process. Progress is seen as flowing.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 17
  18. 18. Spiral Model Testing will be done in each phase Implementation Verification Design RequirmentMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 18
  19. 19. V-Shape Model Plan for testing done side by side during analysis process.Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 19
  20. 20. RecapMarket/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 20
  21. 21. Questions?!?!?Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 21
  22. 22. Market/Division/Tier 3 (Optional) | Practice Group/Tier 4 (Optional)Proprietary & Confidential (Optional) | Date (Optional) 22

×