Test. V-model Wikipedia:

Slides:



Advertisements
Similar presentations
การทดสอบโปรแกรม กระบวนการในการทดสอบ
Advertisements

Testing and Quality Assurance
Annoucements  Next labs 9 and 10 are paired for everyone. So don’t miss the lab.  There is a review session for the quiz on Monday, November 4, at 8:00.
Software Architecture Prof.Dr.ir. F. Gielen
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 32 Slide 1 Aspect-oriented Software Development.
CMSC 345, Version 11/07 SD Vick from S. Mitchell Software Testing.
November 2005J. B. Wordsworth: J5DAMQVT1 Design and Method Quality, Verification, and Testing.
1 CODE TESTING Principles and Alternatives. 2 Testing - Basics goal - find errors –focus is the source code (executable system) –test team wants to achieve.
Illinois Institute of Technology
1 SWE Introduction to Software Engineering Lecture 5.
CS 425/625 Software Engineering Software Testing
Testing an individual module
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 32 Slide 1 Aspect-oriented Software Development 2.
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
BY: GARIMA GUPTA MCA FINAL YEAR WHAT IS SOFTWARE TESTING ? SOFTWARE TESTING IS THE PROCESS OF EXECUTING PROGRAMS OR SYSTEM WITH THE INTENT.
Categories of Testing.
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.
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
Let us start from the V-Model Verification Phases Requirements analysis System Design Architecture Design Module Design Coding Validation phases Unit.
Software Systems Verification and Validation Laboratory Assignment 3 Integration, System, Regression, Acceptance Testing Assignment date: Lab 3 Delivery.
CMSC 345 Fall 2000 Unit Testing. The testing process.
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
Testing : A Roadmap Mary Jean Harrold Georgia Institute of Technology Presented by : Navpreet Bawa.
Testing Especially Unit Testing. V-model Wikipedia:
Contract based programming Using pre- and post-conditions, and object invariants Contract based programming1.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Chapter SIX Implementation, Testing and Pragmatics Making it a reality.
Unit Testing 101 Black Box v. White Box. Definition of V&V Verification - is the product correct Validation - is it the correct product.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
(1) Unit Testing and Test Planning CS2110: SW Development Methods These slides design for use in lab. They supplement more complete slides used in lecture.
Software Testing Process By: M. Muzaffar Hameed.
Software Development Problem Analysis and Specification Design Implementation (Coding) Testing, Execution and Debugging Maintenance.
SOFTWARE TESTING. INTRODUCTION Testing forms the first step in determining the errors in a program. It is the major quality control measure used during.
CSC 480 Software Engineering Testing - I. Plan project Integrate & test system Analyze requirements Design Maintain Test units Implement Software Engineering.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Software Testing 1Software testing. V model Software testing2.
Software Testing. System/Software Testing Error detection and removal determine level of reliability well-planned procedure - Test Cases done by independent.
Agenda for today: The Unified Software Development Process: Test (Note) Test The purpose of testing Artifacts Test in the sw Life Cycle Workers Test procedure.
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
 Software Testing Software Testing  Characteristics of Testable Software Characteristics of Testable Software  A Testing Life Cycle A Testing Life.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
SOFTWARE TESTING. SOFTWARE Software is not the collection of programs but also all associated documentation and configuration data which is need to make.
Testing Integral part of the software development process.
Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik.
Topics  Direct Predicate Characterization as an evaluation method.  Implementation and Testing of the Approach.  Conclusions and Future Work.
Database Testing Gourav Mehta (Associate QA Engineer)
CPMGT 300 Week 3 Learning Team Planning Process Groups and Developing the Scope Check this A+ tutorial guideline at
Software Testing.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Domain Testing Functional testing which tests the application by giving inputs and evaluating its appropriate outputs. system does not accept invalid and.
G&W Chapter 22: Test Cases Software Specification Lecture 29
SOFTWARE TESTING OVERVIEW
Different Types of Testing
Chapter 8 – Software Testing
Quality Management Perfectqaservices.
Lecture 09:Software Testing
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Software Engineering Lecture #14.
Chapter 10 – Software Testing
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
CSE 1020:Software Development
Software Development Chapter 1.
PSS0 Configuration Management,
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Implementation Plan system integration required for each iteration
Presentation transcript:

Test

V-model Wikipedia:

Verification & Validation Verification Phases – Requirements analysis – System Design – Architecture Design – Module Design Validation Phases – Unit Testing – Integration Testing – System Testing – User Acceptance Testing

Types (or Stages) of Testing (Validation) Developer Testing – Normal testing by the developer / programmer – to see it do work Independent and Stakeholder Testing – Independent Testing denotes the test design and implementation that it is most appropriate for someone independent from the team of developers to do. Unit Tests – Systematic automatic test of a unit (testing from a black box view) Integration Test – integration testing is performed to ensure that the components in combination do work (e.g. that classes across packages do work) System Test – System testing is done when the software is functioning as a whole. Do the whole system works Acceptance Test – The users do the testing and accepting as a final test action prior to deploying the software. Check that all use-cases and all non-functional requirements work

Unit testing White box testing – where you check all programming lines have been executed with an accepted result Black box testing – where you check all methods have been executed and all parameter boundaries have been checked – of cause again with an accepted result

Black-box (UPedu) input argument – Normal values from each equivalence class. – Values on the boundary of each equivalence class. – Values outside the equivalence classes. – Illegal values. output argument – Normal values from each equivalence class. – Values on the boundary for each equivalence class. – Values outside the equivalence classes. – Illegal values.

Set up test-cases Follow / Fill out schema Test case # Description of test case Expected value Passed succesfully 1...

Example - Book Constrains: The title must be not null and not empty. The Author must be not null and not empty. The isbn must be not null and the length must be greater than 9 copyId must be in the range 1-15

Test case # Description of test caseExpected value Passed successfully 1Default constructorObject created 2setTitle – parameter nullIllegalArgumentException 3setTitle – parameter emptyIllegalArgumentException 4setTitle – parameter not empty XgetTitle() == X 5setAuthor – parameter nullIllegalArgumentException 6setAuthor – parameter emptyIllegalArgumentException 7setAuthor – parameter not empty XgetAuthor() == X 8setIsbn – parameter nullIllegalArgumentException 9setIsbn – parameter emptyIllegalArgumentException 10 setIsbn – parameter not empty value “ ” IllegalArgumentException 11 setIsbn – parameter not empty value “ ” getIsbn() == “ ” 12setIsbn – parameter not empty value “isbn: ” getIsbn() == “isbn: ”

Test case # Description of test caseExpected value Passed successfully 13setCopyId – parameter value 0IllegalArgumentException 14setCopyId – parameter value 1getCopyId() == 1 15setCopyId – parameter value 4getCopyId() == 4 16setCopyId – parameter value 15getCopyId() == 15 17setCopyId – parameter value 16IllegalArgumentException 18setCopyId – parameter value -1IllegalArgumentException 19Constructor(“title”,”author”,” ”,4) getTitle() == “title” getAuthor() == “author” getIsbn() == “ ” getCopyId() == 4 20Constructor(null,”author”,” ”,4)IllegalArgumentException 21Constructor(”title”,””,” ”,4)IllegalArgumentException 22Constructor(”title”,”author”,”wrong”,4)IllegalArgumentException 23Constructor(“title”,”author”,” ”,0)IllegalArgumentException 24 Tostring Constructor(“title”,”author”,” ”,4) toString() == “title=title author=author isbn= copyId=4”