Integration and system test

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Software Testing. Quality is Hard to Pin Down Concise, clear definition is elusive Not easily quantifiable Many things to many people You'll know it when.
Test Yaodong Bi.
Test Automation Success: Choosing the Right People & Process
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
System Construction and Implementation Objectives:
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
Copyright © 2003 by The McGraw-Hill Companies, Inc. All rights reserved. Business and Administrative Communication SIXTH EDITION.
Integration testing Satish Mishra
6/19/2007SE _6_19_TSPImp_SVT_Lecture.ppt1 Implementation Phase Inputs: Development strategy & plan Completed, inspected & baselined SRS & SDS.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Illinois Institute of Technology
Heuristic Evaluation IS 485, Professor Matt Thatcher.
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
Software Testing & Strategies
Software System Integration
Software Development, Programming, Testing & Implementation.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
INFO 637Lecture #81 Software Engineering Process II Integration and System Testing INFO 637 Glenn Booker.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Chapter 8: Systems analysis and design
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.
Software Testing Life Cycle
Software Systems Verification and Validation Laboratory Assignment 3 Integration, System, Regression, Acceptance Testing Assignment date: Lab 3 Delivery.
RUP Implementation and Testing
Output and User Interface Design
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Understand Application Lifecycle Management
INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Slide 1 Construction (Testing) Chapter 15 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by Solomon.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
Sylnovie Merchant, Ph.D. MIS 161 Spring 2005 MIS 161 Systems Development Life Cycle II Lecture 5: Testing User Documentation.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Chapter 3 Whole Composition Summary of Key Points Writing processes can include eight activities: planning, gathering, writing, evaluating, getting feedback,
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 2: Testing in Software Life Cycle MNN1063 System Testing and Evaluation.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
Focus on design principles and on a process for doing design = To produce a precise, complete, high- quality foundation for product implementation.
What is a level of test?  Defined by a given Environment  Environment is a collection of people, hard ware, software, interfaces, data etc.
Requirements Engineering Requirements Validation and Management Lecture-24.
Bina Nusantara 19 C H A P T E R SYSTEM CONSTRUCTION AND IMPLEMENTATION.
Stat Today: More Chapter 3. Full Factorial Designs at 2 Levels Notation/terminology: 2 k experiment, where –k is the number of factors –each factor.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Tool Support for Testing Classify different types of test tools according to their purpose Explain the benefits of using test tools.
Principles of Information Systems Eighth Edition
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Inspections and Testing
Peer Reviews 11/21/2018.
Lecture 09:Software Testing
Software System Integration
Software life cycle models
Integration Testing CS 4311
Systems Construction and Implementation
Chapter 13: Construction
System Construction and Implementation
Systems Construction and Implementation
Chapter 11: Integration- and System Testing
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

Integration and system test Chapter 9

CONTENTS Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Testing Principles In TSPi, the purpose of testing is to assess the product and not to fix it. You should have found and fixed almost all the defects before the testing phase. The quality of a product is determined when it is developed. When you put a poor-quality product into test, you generally get a poor-quality product out of test. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

TSPi Testing Strategy Build the System Integration Test System Test Using the developed and unit-tested parts, build the system Integration Test Integration-test the system to verify that it is properly built, that all the parts are present, and that they function together System Test System-test the product to validate that it does what the system requirements call for; Regression Test In subsequent cycles, regression tests are also needed to ensure that the development work for this cycle has not unintentionally changed the functionality or performance produced in prior cycles. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Build & Integration Strategy The purpose of the build process is to ensure that all needed parts are present, to assemble a working system, and to provide this system to integration and system test. Integration testing should merely check that all the components are present and that all their calls and other interactions work. You should not test the components’ functions. You should not test the components’ functions. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Build & Integration Strategy Big-Bang Strategy Put all the parts together and see whether they work. Advantage: it requires the least amount of test development; Disadvantage: it is rarely successful, particularly with poor-quality systems. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Build & Integration Strategy The One-at-a-time Strategy Put all the parts together and see whether they work. Advantage: With each addition, you look for problems with the newly added parts Disadvantage: This strategy requires more test development work. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Build & Integration Strategy The Cluster Strategy This strategy is to add parts in clusters. You identify a class of related components and integrate them. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Build & Integration Strategy The Flat-system Strategy This strategy is to integrate all the highest level parts first and then delve down into successive system layers in parallel. You identify a class of related components and integrate them. Advantage: You can detect system-wide issues early; Disadvantage: it usually requires large numbers of stubs or special scaffolding to provide dummy returns for all the functions that are not yet available. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

The Function-first Strategy System Test Strategy The Function-first Strategy Firstly, test each of the system’s intended functions Check operation under stress conditions, evaluate usability Finally, measure performance. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

The Functional Area Strategy System Test Strategy The Functional Area Strategy Cover all aspects of each functional area before moving to the next functional area. You might start by testing Numerical calculations for normal and adverse operation; Usability Performance Quality Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Combining the Preceding-two Strategy System Test Strategy Combining the Preceding-two Strategy Test lower level functions for normal, abnormal and stress behavior; Move to the next higher level and test functional aggregates to ensure that they work together. Check them under various normal and stress conditions; Continue testing at progressively higher levels until you have covered the full system. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Reversing the Preceding Strategy System Test Strategy Reversing the Preceding Strategy Test the highest level functions and work down, doing normal and stress tests Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Test Planning The completed testing plan should have… A list of all the testing steps to be performed The supporting materials required for each test The results that the tests are to produce An estimate of the defect-free run time, the defects to be found, and total time for each test An estimate of the work required to develop each item in the test plan. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Tracking and Measuring Testing The test log (LOGTEST FORM) contains a summary of the tests run and the results obtained With the test log data, you can readily determine which tests were run and which found the most defects You can also determine the test run time and the defects found per testing hour Data from this log can help you select the most efficient strategy for regression-testing modified programs Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Documentation In the TSPi test phase, part of the team drafts and reviews the user documentation while the rest of the team conducts the tests. A well-designed manual should be organized around the reader’s needs and not the product’s structure. Generally The first section should address what the user needs to know first: how to get started Next, you might explain what the user can do with the product Finally, make it easy for people to find what they want to know. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Documentation Writing Style Write short sentences; Use simple words and phrases; Use lots of lists and bulleted items. Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Documentation Document Review Document Organization Document Terminology Document Content Accuracy Readability Understandability Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

The Test Process http://casper.cii.saxion.nl/se/SEscripts/test.html Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Test Scripts Test script includes: Develop build, integration test, and system test procedures Determine size, time, and materials needed for each test Build the product Conduct integration testing Conduct system testing From Glenn Booker INFO 637

Test Scripts Outputs include Produce user documentation, review and fix it Outputs include An integrated and tested product for this cycle Completed LOGD and LOGTEST forms for all tests Completed user documentation Time, size, and defect data in TSP system

Have a nice day!