Testing Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university 1Worshop in SE ProjectSpring 2013.

Slides:



Advertisements
Similar presentations
Test Yaodong Bi.
Advertisements

CMSC 345, Version 11/07 SD Vick from S. Mitchell Software Testing.
Software Engineering, COMP201 Slide 1 Software Testing Lecture 28 & 29.
Software testing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
1 Software Testing and Quality Assurance Lecture 30 - Introduction to Software Testing.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Defect testing l Testing programs to establish the presence of system defects.
Software Engineering Software Testing.
CS 425/625 Software Engineering Software Testing
BASIS PATH TESTING ● By Tom McCabe ● McCabe, T., "A Software Complexity Measure," IEEE Trans. Software Engineering, vol. SE-2, December 1976, pp
- Testing programs to establish the presence of system defects -
1 Software Testing and Quality Assurance Lecture 5 - Software Testing Techniques.
Unit Testing CS 414 – Software Engineering I Don Bagert Rose-Hulman Institute of Technology January 16, 2003.
Program unit A Program unit B Program unit T Function 1 Function 2 Function Component 1 Whole System (e.g. regression testing) Component 3....
1 Software Testing Techniques CIS 375 Bruce R. Maxim UM-Dearborn.
Chapter 13 & 14 Software Testing Strategies and Techniques
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Software Testing Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
TESTING.
Different Levels of Testing
Introduction Telerik Software Academy Software Quality Assurance.
CMSC 345 Fall 2000 Unit Testing. The testing process.
Testing phases. Test data Inputs which have been devised to test the system Test cases Inputs to test the system and the predicted outputs from these.
Software Engineering Chapter 23 Software Testing Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Chapter 20 Software Testing.
CSC 480 Software Engineering Lecture 14 Oct 16, 2002.
Overview of Software Testing 07/12/2013 WISTPC 2013 Peter Clarke.
1 Software testing. 2 Testing Objectives Testing is a process of executing a program with the intent of finding an error. A good test case is in that.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Software Testing The process of operating a system or component under specified conditions, observing and recording the results, and making an evaluation.
Testing Workflow In the Unified Process and Agile/Scrum processes.
1 Software Defect Testing Testing programs to establish the presence of system defects.
Software Testing Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
Software Construction Lecture 18 Software Testing.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 Program Testing (Lecture 14) Prof. R. Mall Dept. of CSE, IIT, Kharagpur.
CSC 480 Software Engineering Lecture 15 Oct 21, 2002.
Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 1 Requirements  Elicitation  Analysis  Specification.
Creator: ACSession No: 7 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringSeptember 2005 Software Measurement – Estimation and Productivity CSE300.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Defect testing l Testing programs to establish the presence of system defects.
Software Engineering 2004 Jyrki Nummenmaa 1 BACKGROUND There is no way to generally test programs exhaustively (that is, going through all execution.
CPSC 873 John D. McGregor Session 9 Testing Vocabulary.
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.
White Box Testing Arun Lakhotia University of Southwestern Louisiana P.O. Box Lafayette, LA 70504, USA
Software Construction Lecture 19 Software Testing-2.
CS451 Lecture 10: Software Testing Yugi Lee STB #555 (816)
CPSC 871 John D. McGregor Module 8 Session 1 Testing.
SOFTWARE TESTING. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves any activity.
OOAD UNIT V B RAVINDER REDDY PROFESSOR DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING.
VI SEM CSE UNIT IV SOFTWARE ENGINEERING PROJECT MANAGEMENT TESTING STRATEGIES By Mr. Vaibhav V. Bhujade DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING DMIETR,
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
CSC 395 – Software Engineering Lecture 27: White-Box Testing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Testing Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university 1Worshop in SE ProjectSpring 2013.
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
Defect testing Testing programs to establish the presence of system defects.
White Box Testing. Agenda White-box vs Black-box Program Flow Controls White-box Test Methods Exercises Complexity Q&A.
Testing Integral part of the software development process.
CPSC 372 John D. McGregor Module 8 Session 1 Testing.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XVIII. Software Testing.
White-Box Testing Pfleeger, S. Software Engineering Theory and Practice 2nd Edition. Prentice Hall, Ghezzi, C. et al., Fundamentals of Software Engineering.
Software Engineering (CSI 321)
IS301 – Software Engineering V:
WHITEBOX TESTING APPROACH
Software Engineering Lecture #39
Software Engineering Lecture #35
Whitebox Testing.
Presentation transcript:

Testing Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university 1Worshop in SE ProjectSpring 2013

Software Engineering, 2005Design Patterns – Creational patterns 2 Classification Tests are boolean: Pass or fail! 1.White-box testing: 1.Unit testing 1.Follow computation paths (code coverage) 2.Test scenarios derived from use cases (data coverage) 3.Test non-functional requirements (data coverage) 2.Integration testing 1.Test integration scenarios derived from functional and non- functional requirements 2.Black-box testing 1.Test scenarios derived from use cases (data coverage) 2.Test non-functional requirements (data coverage) 3.Regression testing

Software Engineering, 2005Design Patterns – Creational patterns 3 Unit testing – Follow computation paths 1.White-box testing: 1.Unit testing 1.Follow computation paths (code coverage) 2.Test scenarios derived from use cases (data coverage) 3.Test non-functional requirements (data coverage) Code coverage: Statement, line coverage Branch coverage  Code complexity – e.g., cyclomatic complexity  Related to data coverage

Software Engineering, 2005Design Patterns – Creational patterns 4 Unit testing – Use-case scenarios 1.White-box testing: 1.Unit testing 1.Follow computation paths (code coverage) 2.Test scenarios derived from use cases (data coverage) 3.Test non-functional requirements (data coverage) Use-case coverage: Build scenarios for use-case alternatives  Use sequence diagrams for scenario specification  What is the relevance of use-case diagrams? Data coverage  How to test “big, complex” data, like a big graph?

Software Engineering, 2005Design Patterns – Creational patterns 5 Unit testing – Non-functional requirements 1.White-box testing: 1.Unit testing 1.Follow computation paths (code coverage) 2.Test scenarios derived from use cases (data coverage) 3.Test non-functional requirements (data coverage) How to create Data? How to test success/failure Beware of side-effects

Software Engineering, 2005Design Patterns – Creational patterns 6 Integration testing 1.White-box testing: 1.Unit testing 2.Integration testing 1.Test integration scenarios derived from functional and non- functional requirements 1.Use sequence diagrams to emphasize inter-module interaction

Software Engineering, 2005Design Patterns – Creational patterns 7 Black-box: Test Use case scenarios How different from white-box testing? 1.Black-box testing  Positive tests  Negative tests  Use customer advice for testing data 1.Test scenarios derived from use cases (data coverage) 2.Test non-functional requirements (data coverage)

Software Engineering, 2005Design Patterns – Creational patterns 8 Recommended blog and lecture: How to write non-testable code:  untestable-code.html untestable-code.html How to Write Clean, Testable Code 