Dr. Manar Elkady's Lecture Notes: Software Testing Types, Levels, and Plans, Summaries of Software Engineering

Download Dr. Manar Elkady's Lecture Notes: Software Testing Types, Levels, and Plans and more Summaries Software Engineering in PDF only on Docsity!

Software Testing

Lecture (3)

Dr. Manar Elkady

[email protected]

These material are retrieved from previous courses offering by Dr. Soha Makady and Prof. Amr Kamel

Outline

• Types of Testing
• Testing Levels
• The V model
• Test Plans

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5

Static Analysis with Eclipse

• Compiler Warnings and Errors
  • Possibly uninitialized Variable
  • Undocumented empty block
  • Assignment has no effect
• Checkstyle
  • Check for code guideline violations
  • http://checkstyle.sourceforge.net
• FindBugs
  • Check for code anomalies
  • http://findbugs.sourceforge.net
• Metrics
  • Check for structural anomalies
  • http://metrics.sourceforge.net

Testing Levels Based on Software Activity (c) Copyright Soha Makady 2016 7

Testing Levels Based on Software Activity (c) Copyright Soha Makady 2016 8

Testing Levels Based on Software Activity (c) Copyright Soha Makady 2016 10

Testing Levels Based on Software Activity (c) Copyright Soha Makady 2016 11

Introduction to Software Testing, Edition 2 (Ch 2) © Ammann & Offutt 13 Traditional Testing Levels Class A method mA1() method mA2() Class B method mB1() method mB2() main Class P Acceptance testing : Is the software acceptable to the user? Integration testing : Test how modules interact with each other System testing :Test the overall functionality of the system Module testing (developer testing) : Test each class, file, module, component Unit testing (developer testing) : Test each unit (method) individually This view obscures underlying similarities

The V-Model

Test Plans

1. Overall test objectives.

16

Test Plan

• Introduction
• Risks and contingencies

Test Plans

• 2. Scope of the tests. 17 Test Plan
• Introduction
• Items to be tested (e.g., procedures, classes, modules, libraries).
• Features to be tested (e.g., functional requirements, performance requirements).
• Features not to be tested (with reasons for exclusion).
• Risks and contingencies

Test Plans

• 4. How to test.
• What strategies, methods, hardware, software tools, and test techniques will be applied? E.g., what percentage of test coverage is expected?
• What test deliverables and documents should be produced? These include::
• Test design specifications
• Test cases
• Test logs
• Test summary reports 19 Test Plan
• Introduction
• Items to be tested.
• Features to be tested
• Features not to be tested.
• Approach
• Test deliverables
• Responsibilities
• Staffing and training needs
• Risks and contingencies

Test Plans

• 5. When to test. 20 Test Plan
• Introduction
• Items to be tested.
• Features to be tested
• Features not to test
• Approach
• Test Deliverables
• Responsibilities
• Staffing and training needs
• Schedule
• Risks and contingencies