SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Testing Smart Report Template

hiroko avatar
hiroko
14 diapositives · 300 Views · Oct 21, 2014

Testing Smart Report Template. By: Kashif Masud. Topics. Smart Report Template overview Testing techniques used and why Number of test cases generated Effort (in hours) of execution Number of defects found Analysis of defects Follow-up actions. What is Smart Report?.

#testing smart report template #testing smart report template ppt #powerpoint #presentation
Testing Smart Report Template - slide 1
01 / 14Testing Smart Report Template
1 / 17

Télécharger la présentation

Testing Smart Report Template
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. TestingSmart Report Template By: Kashif Masud

  2. Topics • Smart Report Template overview • Testing techniques used and why • Number of test cases generated • Effort (in hours) of execution • Number of defects found • Analysis of defects • Follow-up actions

  3. What is Smart Report? The Smart Report Template is an interactive application used to perform trades by Specialists in the New York Stock Exchange in order to maintain a fair, balanced and orderly trading market. The Smart Report Template facilitates the Specialist’s decision-making by performing calculations, displaying market data, processing input and verifying data based on business rules. It makes the trading process more efficient and reduces the risk for errors.

  4. What does Smart Report Template look like? How do we test such an application?

  5. Let’s use heuristic analysis The Smart Report Template is an interactive application used to perform trades by Specialists in the New York Stock Exchange in order to maintain a fair, balanced and orderly trading market. The Smart Report Template facilitates the Specialist’s decision-making by performing calculations, displaying market data, processing input and verifying data based on business rules. It makes the trading process more efficient and reduces the risk for errors. What does all this imply?

  6. Interactive  Interaction between application and user Application provides data User provides some input Application performs calculations Application performs actions Perform Calculations  Boundary testing; DFT Display Market Data  GUI testing / List-based testing Process Input  Partition testing; Boundary testing Verify Data  GUI testing; DFT  Control Flow Testing

  7. Control Flow Graph for Smart Report List-based testing Partition-based testing We want to: 1. Test each state 2. Test each transition Let’s zoom in on this area 3. Test each path

  8. How do we test all these fields? Answer: = Input Fields  Partition-based testing, Boundary testing • Verify that values selected from set of valid/invalid values correctly handled • Verify field capacities by inputting extreme field values = Calculated Fields  Boundary testing, Data flow testing • Verify field capacities by pushing calculated field values to extremes • Verify fields correctly calculated based on data dependencies; use data-dependency graphs (DDG)

  9. Example: DDG for ‘Book Buyer Row’ field

  10. Control Flow Graph for Smart Report We want to: 1. Test each state 2. Test each transition 3. Test each path List-based testing; DFT GUI testing List-based testing; Partition testing Partition-based testing

  11. Test Case Distribution 6 5 Effort: 16 hours of execution 3 62 (Defects = 4) 27 (Defects = 2) Total # TCs = 168 (Defects = 2) 50 8 Total # Defects = 8 5 2

  12. Defect Analysis – What, Where and When? Most defects are in calculation area

  13. Possible Reasons for Defects: • Lack of business knowledge • Misunderstanding of requirements • Coding standards not being followed • Oversight Follow-up Actions: • Perform detailed causal analysis • Provide analysis results to management • Create plan-of-action based on management feedback

  14. Thank You!