UNIT OBJECTIVE. Understand what system testing entails Learn techniques for measuring system quality
|
|
- Aron Harvey
- 6 years ago
- Views:
Transcription
1 SYSTEM TEST
2 UNIT OBJECTIVE Understand what system testing entails Learn techniques for measuring system quality
3 SYSTEM TEST 1. Focus is on integrating components and sub-systems to create the system 2. Testing checks on component compatibility, interactions, correctly passing information, and timing Unlike Unit Test Like Unit Test, activities focus on following uses and data 1. Typical 2. Boundaries 3. Outliers 4. Failures 1. Components may come from many, independent parties 2. Testing becomes a group activity 3. Bespoke development may meet Off-The- Shelf or reused components 4. Testing may move to an independent team altogether
4 Will be a complete and utter waste if components are not thoroughly tested
5 INTEGRATING MULTIPLE PARTIES MAY INTRODUCE CONFLICT System Integration 1. Components may come from multiple, possibly independent, parties 2. Bespoke development may meet Off-The-Shelf or reused components 3. Testing becomes a group activity 4. Testing may move to an independent team altogether Implications Who controls integration readiness? What does lab entry mean? Are COTS components trusted? How to assign credit for test results and then who is responsible for repairs? How to maintain momentum when everyone isn t at the table? When partner priorities are not shared? What about open source?
6 UNLIKE COMPONENTS, SYSTEMS HAVE EMERGENT BEHAVIOR Some behavior is only clear when you put components together This has to be tested too, although it can be very hard to plan in advance! Usually this is identified after the fact, and test suites/cases are refactored.
7 TESTING FOCUS Emphasizes component 1. Compatibility 2. Interactions 3. Information passing 4. Timing Integration aims to find misunderstandings one component introduces when it interacts with other components Use Cases are a useful testing model Sequence diagrams form a strong basis for designing these tests Articulates the inputs required and the expected behaviors and outputs
8 ITERATIVE DEVELOPMENT LEADS TO ITERATIVE TESTING Two senses 1. Create tests incrementally 2. Run tests iteratively On check-in and branch merge, test all affected modules On check-in, test all modules Per a schedule, test all modules Regression Testing E.g. daily Each change, especially after a bug fix, should mean adding at least one new test case It is always best to test after each change as completely as you can, and completely before a release
9 REGRESSION TESTING Reasserting that changes to system haven t broken previously working parts Changes include Enhancements/extensions to modules Patches Configuration changes Options 1. Retest everything 2. Retest using only selected tests Tester specifies what test cases/suites get run 3. Retest using priority orders Tester defines priorities against test cases/suites. Tests are run in a greedy manner for some time period. Priorities may be set up against specific system or module versions.
10 OBVIOUS ISSUE WITH REGRESSION TESTING It becomes very expensive as test suites grow and code change velocities are high. It may be that regression test cycles keep getting disrupted by continual code changes Is a great way to put idle machine cycles to work especially if you own the machines (versus renting them) Also as a consequence of the introduction of new bugs, program maintenance requires far more system testing per statement written than any other programming. Theoretically, after each fix one must run the entire batch of test cases previously run against the system, to ensure that it has not been damaged in an obscure way. In practice, such regression testing must indeed approximate this theoretical idea, and it is very costly. - F. Brooks, The Mythical Man Month
11 WHO GUARDS THE GUARDS? Software Quality Assurance depends on good testing processes and test suite definitions How do you know if the test suite is good?
12 YOUR TESTING IS GOOD ENOUGH UNTIL A PROBLEM SHOWS THAT IT IS NOT GOOD ENOUGH It is hard to know when you should feel enough confidence to release the system Confidence comes, in part, on the sub-test of possible tests selected Picking the Subset high 1. Selection based on policy Every statement must executed once Every path must be exercised Crafted by specific end user use cases (scenario testing) 2. Selection based on testing team experience 3. Run everything each time Software Quality low many defects found few defects found few defects found few defects found high Test Quality low
13 MUTATION TESTING Introduce small changes to the code and see if testing catches it Statement Mutation changes to lines of code (adds, removes, changes) Value Mutation- changes parameter values are modified Decision Mutation- changes to control statements Why? Intent is to identify regions of code that are not tested. And catch dumb mistyping related bugs. The focus checks the effectiveness and accuracy of the testing program If testing catches the mutant, it is considered killed (M K ) If testing does not catch the mutant, it is considered an mutant equivalent (M E ) Different code, same accepted result Measuring mutations (Mutation Score) MS = M K M T M E Anything less than MS = 1 is generally bad test suites need refactoring to cover M E Mutation Testing is a White Box Testing activity Original Mutant c = a * b; c = a + b; If (a == 10) { If (a == 11) { If (a == b) { If (a!= b) {
14 PUTS AND TAKES ON MUTATION TESTING Advantages Disadvantages Can nicely cover the original source Finds ambiguities in the source code May detect detect all the faults in the testing regime Originally proposed in the early 2000 s Back in vogue because of the explosion in compute capacity Mutation testing is extremely costly and time consuming to pursue Requires generating many mutant programs Each mutation runs the original test suite(s), which may involve many test cases or run tests that take a long time or both Creates a potentially huge number of test suites to run. Requires additional tech to manage mutation generation and detection
15 Defect Density DEFECT DENSITY Using the past to estimate the future Judges code stability by comparing past number of bugs per code measure to present measured levels BugDensity release i = BugsFound(prerelease i)+bugsfound(postrelease i ) CodeMeasure(release i ) Release i is a candidate for release if the following holds: min(bugdensity release 1..i 1 ) BugDensity release i max(bugdensity release 1..i 1 ) Poor Software 9.5 Quality Expected Quality Poor Test Coverage/Quality 4 What this means: If density for the next release s additional code is within ranges of prior releases, it is a candidate for release 2 provided test or development practices haven t improved 0 Release 1 2
16 CODE MEASURES Approach 1: Count lines of Code Lines of code Count only executable lines. Count executable lines plus data definitions. Count executable lines, data definitions, and comments. Count executable lines, data definitions, comments Count lines as physical lines on an input screen. Count lines as terminated by logical delimiters. Count only shipped lines Count only new/changed lines Approach 2: Count function points Using a standard notion of a function/object/component, use a weighted function over Number of external interfaces Number of inputs Number of outputs Internal complexity Configuration complexity The weights may consider: Data communications Performance Transaction rate Reusability Installation ease Operational ease
17 MEASURING QUALITY: CAPTURE-RECAPTURE Applies estimating technique used in predicting wild-life populations (Humphrey, Introduction to Team Software Process, Addison Wesley, 2000) Example: Estimating Turtle Population (assuming turtles don t migrate) You catch and tag 5 turtles. Then, you release them. You later catch 10 turtles, and two have tags. Total # of turtles 5 turtles Total # of turtles = 10 turtles 2 turtles 10 turtles 5 turtles 2 turtles 25 Uses data collected by two or more independent collectors Collected via reviews or tests
18 CAPTURE-RECAPTURE Each collector finds some defects out of the total number of defects Some of these defects found will overlap Method 1. Count the number of defects found by each collector (n 1, n 2 ) 2. Count the number of intersecting defects found by each collector (m) When most findings overlap 3. Calculate defects found = (n 1 + n 2 ) m 4. Estimate total defects = (n 1 n 2 ) m 5. Estimate remaining defects remainder = (n 1 n 2 ) (n m 1 + n 2 ) m If multiple collectors, assign A to the highest collected number and set B to the rest of the collected defects. When multiple engineers find the same defect, count it just once. When there is little overlap Figures taken from
19 PERFORMANCE TESTING Measures the system s capacity to process a specific load over a specific time-span number of concurrent users specific number of concurrent transactions Involves creating and executing an operational profile that reflects the expected values of uses Ideally the system should degrade gracefully rather than collapse under load There are several types of performance tests 1. Load Aims to assess compliance with nonfunctional requirements 2. Stress Identifies system capacity limits 3. Spike Testing involving rapid swings in load 4. Endurance (or Soak) Continuous operation at a given load Under load, issues like protocol overhead or timing issues take center stage
20 Why do performance testing? Multiple Dimensions to Optimize The requirements demand demonstration that the system meets performance criteria Some performance related nonfunctional requirements exist It can compare two systems to find which performs better It can identify which parts of the system are the weak links It can identify workloads that cause the system to perform badly Typical optimizations focus on: 1. Throughput or Concurrency Getting the most data processed Greatest number of simultaneous transactions 2. Server response time 3. Service request round-trip time 4. Server utilization
QUALITY ASSURANCE. Michael Weintraub Fall, 2015
QUALITY ASSURANCE Michael Weintraub Fall, 2015 Unit Objective Understand what quality assurance means Understand QA models and processes Definitions According to NASA Software Assurance: The planned and
More informationSoftware Engineering and Scientific Computing
Software Engineering and Scientific Computing Barbara Paech, Hanna Remmel Institute of Computer Science Im Neuenheimer Feld 326 69120 Heidelberg, Germany http://se.ifi.uni-heidelberg.de paech@informatik.uni-heidelberg.de
More informationHigher-order Testing. Stuart Anderson. Stuart Anderson Higher-order Testing c 2011
Higher-order Testing Stuart Anderson Defining Higher Order Tests 1 The V-Model V-Model Stages Meyers version of the V-model has a number of stages that relate to distinct testing phases all of which are
More informationSoftware Testing CS 408
Software Testing CS 408 1/09/18 Course Webpage: http://www.cs.purdue.edu/homes/suresh/408-spring2018 1 The Course Understand testing in the context of an Agile software development methodology - Detail
More informationMeasuring VDI Fitness and User Experience Technical White Paper
Measuring VDI Fitness and User Experience Technical White Paper 3600 Mansell Road Suite 200 Alpharetta, GA 30022 866.914.9665 main 678.397.0339 fax info@liquidwarelabs.com www.liquidwarelabs.com Table
More informationLecture 15 Software Testing
Lecture 15 Software Testing Includes slides from the companion website for Sommerville, Software Engineering, 10/e. Pearson Higher Education, 2016. All rights reserved. Used with permission. Topics covered
More informationTopics in Software Testing
Dependable Software Systems Topics in Software Testing Material drawn from [Beizer, Sommerville] Software Testing Software testing is a critical element of software quality assurance and represents the
More informationChapter 10. Testing and Quality Assurance
Chapter 10 Testing and Quality Assurance Different styles of doing code review Human Reviewer Code Inspection with continuous integration infrastructure Pinger s testing set up Testing Related topics 1.
More informationSoftware Testing. Massimo Felici IF
Software Testing Massimo Felici IF-3.46 0131 650 5899 mfelici@staffmail.ed.ac.uk What is Software Testing? Software Testing is the design and implementation of a special kind of software system: one that
More informationQuestion 1: What is a code walk-through, and how is it performed?
Question 1: What is a code walk-through, and how is it performed? Response: Code walk-throughs have traditionally been viewed as informal evaluations of code, but more attention is being given to this
More informationTerminology. There are many different types of errors and different ways how we can deal with them.
Testing Terminology Reliability: The measure of success with which the observed behavior of a system confirms to some specification of its behavior. Failure: Any deviation of the observed behavior from
More informationOverview. State-of-the-Art. Relative cost of error correction. CS 619 Introduction to OO Design and Development. Testing.
Overview CS 619 Introduction to OO Design and Development ing! Preliminaries! All sorts of test techniques! Comparison of test techniques! Software reliability Fall 2012! Main issues: There are a great
More informationSoftware Testing Strategies. Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman. For non-profit educational use only
Chapter 22 Software Testing Strategies Slide Set to accompany Software Engineering: A Practitioner s Approach, 8/e by Roger S. Pressman and Bruce R. Maxim Slides copyright 1996, 2001, 2005, 2009, 2014
More informationVerification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1
Verification and Validation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1 Verification vs validation Verification: "Are we building the product right?. The software should
More informationImplementation and Integration
Implementation and Implementations and integration are two different phases performed in sequence Problems with this approach To test a module independently, Development and SQA members need Stubs for
More informationSample Exam Syllabus
ISTQB Foundation Level 2011 Syllabus Version 2.9 Release Date: December 16th, 2017. Version.2.9 Page 1 of 46 Dec 16th, 2017 Copyright 2017 (hereinafter called ISTQB ). All rights reserved. The authors
More informationIntroduction to Software Engineering
Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,
More informationEECS 481 Software Engineering Exam #1. You have 1 hour and 20 minutes to work on the exam.
EECS 481 Software Engineering Exam #1 Write your name and UM uniqname on the exam. There are ten (10) pages in this exam (including this one) and seven (7) questions, each with multiple parts. Some questions
More informationFeasibility of Testing to Code. Feasibility of Testing to Code. Feasibility of Testing to Code. Feasibility of Testing to Code (contd)
Feasibility of Testing to Code (contd) Feasibility of Testing to Code (contd) An incorrect code fragment for determining if three integers are equal, together with two test cases Flowchart has over 10
More informationIn this Lecture you will Learn: Testing in Software Development Process. What is Software Testing. Static Testing vs.
In this Lecture you will Learn: Testing in Software Development Process Examine the verification and validation activities in software development process stage by stage Introduce some basic concepts of
More informationSample Question Paper. Software Testing (ETIT 414)
Sample Question Paper Software Testing (ETIT 414) Q 1 i) What is functional testing? This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type
More informationTypes of Software Testing: Different Testing Types with Details
Types of Software Testing: Different Testing Types with Details What are the different Types of Software Testing? We, as testers are aware of the various types of Software Testing such as Functional Testing,
More informationCONFERENCE PROCEEDINGS QUALITY CONFERENCE. Conference Paper Excerpt from the 28TH ANNUAL SOFTWARE. October 18th 19th, 2010
PACIFIC NW 28TH ANNUAL SOFTWARE QUALITY CONFERENCE October 18th 19th, 2010 Conference Paper Excerpt from the CONFERENCE PROCEEDINGS Permission to copy, without fee, all or part of this material, except
More informationSoftware Testing. An Overview
Software Testing An Overview Software Testing Defined Software testing is the process of verifying & validating that a program or application: Meets technical specifications Meets business requirements
More informationSoftware Quality Assurance. David Janzen
Software Quality Assurance David Janzen What is quality? Crosby: Conformance to requirements Issues: who establishes requirements? implicit requirements Juran: Fitness for intended use Issues: Who defines
More informationComputational Systems COMP1209
Computational Systems COMP1209 Testing Yvonne Howard ymh@ecs.soton.ac.uk A Problem A café wants to build an automated system to provide breakfasts. The robot waiter greets people before taking their order
More informationAdopting Agile Practices
Adopting Agile Practices Ian Charlton Managing Consultant ReleasePoint Software Testing Solutions ANZTB SIGIST (Perth) 30 November 2010 Tonight s Agenda What is Agile? Why is Agile Important to Testers?
More informationChapter 11, Testing, Part 2: Integration and System Testing
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11, Testing, Part 2: Integration and System Testing Overview Integration testing Big bang Bottom up Top down Sandwich System testing
More informationChapter 11, Testing, Part 2: Integration and System Testing
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11, Testing, Part 2: Integration and System Testing Overview Integration testing Big bang Bottom up Top down Sandwich System testing
More informationChap 2. Introduction to Software Testing
Chap 2. Introduction to Software Testing 2.1 Software Testing Concepts and Processes 2.2 Test Management 1 2.1 Software Testing Concepts and Processes 1. Introduction 2. Testing Dimensions 3. Test Concepts
More informationVerification and Validation
Chapter 5 Verification and Validation Chapter Revision History Revision 0 Revision 1 Revision 2 Revision 3 Revision 4 original 94/03/23 by Fred Popowich modified 94/11/09 by Fred Popowich reorganization
More informationUnderstanding the Open Source Development Model. » The Linux Foundation. November 2011
» The Linux Foundation Understanding the Open Source Development Model November 2011 By Ibrahim Haddad (PhD) and Brian Warner, The Linux Foundation A White Paper By The Linux Foundation This paper presents
More informationCourse Wrap-Up. Software Testing and Verification. Stephen M. Thebaut, Ph.D. Prepared by. University of Florida
Course Wrap-Up Software Testing and Verification Prepared by Stephen M. Thebaut, Ph.D. University of Florida A few loose ends Final Exam + solution notes will be posted (under Practice Exams ) ASAP probably
More informationLecture 19 Engineering Design Resolution: Generating and Evaluating Architectures
Lecture 19 Engineering Design Resolution: Generating and Evaluating Architectures Software Engineering ITCS 3155 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at
More informationVerification and Validation. Verification and validation
Verification and Validation Verification and validation Verification and Validation (V&V) is a whole life-cycle process. V&V has two objectives: Discovery of defects, Assessment of whether or not the system
More informationCertified Tester Foundation Level(CTFL)
Certified Tester Foundation Level(CTFL) ISTQB : International Software Testing Qualifications Board Heading: The International Software Testing Qualifications Board (ISTQB) is an internationally recognized
More informationLeveraging Program Equivalence for Adaptive Program Repair: Models and First Results. Westley Weimer, UVA Zachary P. Fry, UVA Stephanie Forrest, UNM
Leveraging Program Equivalence for Adaptive Program Repair: Models and First Results Westley Weimer, UVA Zachary P. Fry, UVA Stephanie Forrest, UNM Automated Program Repair Given a program, a notion of
More informationBridge Course On Software Testing
G. PULLAIAH COLLEGE OF ENGINEERING AND TECHNOLOGY Accredited by NAAC with A Grade of UGC, Approved by AICTE, New Delhi Permanently Affiliated to JNTUA, Ananthapuramu (Recognized by UGC under 2(f) and 12(B)
More informationObject-Oriented Software Engineering Conquering Complex and Changing Systems. Chapter 9, Testing
Object-Oriented Software Engineering Conquering Complex and Changing Systems Chapter 9, Testing Preliminaries Written exam on for Bachelors of Informatik, and for other students who are not in the Informatik
More informationIntegration Testing Qualidade de Software 2
Integration Testing Integration Testing Software systems are built with components that must interoperate Primary purpose: To reveal component interoperability faults so that testing at system scope may
More informationAnswers NOT TO BE PRINTED
Advanced Software Engineering, COMP3C05, 2002 Answer Question 1 and two further questions. Marks for each part of each question are indicated in square brackets Calculators are NOT permitted 1. Your 3C05
More informationQUIZ #5 - Solutions (5pts each)
CS 435 Spring 2014 SOFTWARE ENGINEERING Department of Computer Science Name QUIZ #5 - Solutions (5pts each) 1. The best reason for using Independent software test teams is that a. software developers do
More informationAnalysis of the Test Driven Development by Example
Computer Science and Applications 1 (2013) 5-13 Aleksandar Bulajic and Radoslav Stojic The Faculty of Information Technology, Metropolitan University, Belgrade, 11000, Serbia Received: June 18, 2013 /
More informationModeling of RAS and Relays in Power Flow Contingency Analysis. Jamie Weber
Modeling of RAS and Relays in Power Flow Contingency Analysis Jamie Weber weber@powerworld.com 217 384 6330 ext. 13 2001 South First Street Champaign, Illinois 61820 +1 (217) 384.6330 support@powerworld.com
More informationChapter 11, Testing. Using UML, Patterns, and Java. Object-Oriented Software Engineering
Chapter 11, Testing Using UML, Patterns, and Java Object-Oriented Software Engineering Outline Terminology Types of errors Dealing with errors Quality assurance vs Testing Component Testing! Unit testing!
More informationChapter 8 Software Testing. Chapter 8 Software testing
Chapter 8 Software Testing 1 Topics covered Introduction to testing Stages for testing software system are: Development testing Release testing User testing Test-driven development as interleave approach.
More informationIntegration Testing. Conrad Hughes School of Informatics. Slides thanks to Stuart Anderson
Integration Testing Conrad Hughes School of Informatics Slides thanks to Stuart Anderson 19 February 2010 Software Testing: Lecture 10 1 Unit Test vs Integration Testing 1 The ideal in unit testing is
More informationBaseline Testing Services. Whitepaper Vx.x
Whitepaper Vx.x 2018-04 Table of Contents 1 Introduction... 3 2 What is Baseline Testing?... 3 3 Customer Challenge... 3 4 Project Details... 3 4.1 First Steps... 3 4.2 Project Management... 3 4.3 Software
More informationTurning a Marathon Runner into a Sprinter: Adopting Agile Testing Strategies and Practices at Microsoft
Turning a Marathon Runner into a Sprinter: Adopting Agile Testing Strategies and Practices at Microsoft Jean Hartmann Test Architect jeanhar@microsoft.com Overview Embracing Change Quality-related themes
More informationPart I: Preliminaries 24
Contents Preface......................................... 15 Acknowledgements................................... 22 Part I: Preliminaries 24 1. Basics of Software Testing 25 1.1. Humans, errors, and testing.............................
More informationThe Importance of Test
Software Testing Mistake in coding is called error, Error found by tester is called defect, Defect accepted by development team is called bug, Product does not meet the requirements then it Is failure.
More informationPart 5. Verification and Validation
Software Engineering Part 5. Verification and Validation - Verification and Validation - Software Testing Ver. 1.7 This lecture note is based on materials from Ian Sommerville 2006. Anyone can use this
More informationShree.Datta Polytechnic College,Dattanagar, Shirol. Class Test- I
Shree. Datta S.S.S.K. Charitable Trust s Shree.Datta Polytechnic College,Dattanagar, Shirol Class Test- I Course Code:CO6E Subject:-SOFTWARE TESTING Marks:-25 Semester:-VI Subject code:-12258 Date:- Institute
More informationMONIKA HEINER.
LESSON 1 testing, intro 1 / 25 SOFTWARE TESTING - STATE OF THE ART, METHODS, AND LIMITATIONS MONIKA HEINER monika.heiner@b-tu.de http://www.informatik.tu-cottbus.de PRELIMINARIES testing, intro 2 / 25
More informationObject-Oriented Software Engineering Practical Software Development using UML and Java
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Lecture 3 Errors and failure Inputs Error revealing inputs
More informationIntegration Testing. Unit Test vs Integration Testing 1. Unit Testing vs Integration Testing 2. Unit testing: isolation, stub/mock objects
Unit Test vs Testing 1 Testing Conrad Hughes School of Informatics Slides thanks to Stuart Anderson The ideal in unit testing is to isolate a single code unit and test it against its behavioural specification.
More informationIntegration and Testing. Uses slides from Lethbridge & Laganiere, 2001
Integration and Testing Uses slides from Lethbridge & Laganiere, 2001 Testing phases: V model Requirements Acceptance Testing Specifications System Testing Design Integration Testing Detailed Design Unit
More informationTesting. Outline. What is this? Terminology. Erroneous State ( Error ) Algorithmic Fault
Outline 1 Terminology Types of errors Dealing with errors Quality assurance vs Component Unit testing Integration testing Strategy Design Patterns & testing unction testing Structure Performance testing
More informationAgile Testing in the Real World Moving Beyond Theory to Achieve Practicality [NEED PICTURE HERE]
Moving Beyond Theory to Achieve Practicality [NEED PICTURE HERE] There are lots of books, articles, and webinars about how great Agile is However, those often describe purist approaches that adhere to
More informationTest s in i g n III Week 16
Testing III Week 16 Agenda (Lecture) White box testing Condition coverage Loop coverage Path coverage Agenda (Lab) Implementation Review of SRS/SDD documents Submit a weekly project progress report at
More informationChapter 9. Software Testing
Chapter 9. Software Testing Table of Contents Objectives... 1 Introduction to software testing... 1 The testers... 2 The developers... 2 An independent testing team... 2 The customer... 2 Principles of
More informationTest Oracles. Test Oracle
Encontro Brasileiro de Testes de Software April 23, 2010 Douglas Hoffman, BACS, MBA, MSEE, ASQ-CSQE, ASQ-CMQ/OE, ASQ Fellow Software Quality Methods, LLC. (SQM) www.softwarequalitymethods.com doug.hoffman@acm.org
More informationWelfare Navigation Using Genetic Algorithm
Welfare Navigation Using Genetic Algorithm David Erukhimovich and Yoel Zeldes Hebrew University of Jerusalem AI course final project Abstract Using standard navigation algorithms and applications (such
More informationCMSC 435: Software Engineering Section 0201
CMSC 435: Software Engineering Section 0201 Atif M. Memon (atif@cs.umd.edu) 4115 A.V.Williams building Phone: 301-405-3071 Office hours Tu.Th. (11:00am-1:00pm) Don t wait, don t hesitate, do communicate!!
More informationHelix Test Case Management Best Practices
The following information provides best practices for test case management activities in Helix ALM. These best practices are guidelines. Your testing process and business rules should dictate whether or
More informationVerification and Validation. Assuring that a software system meets a user s needs. Verification vs Validation. The V & V Process
Verification and Validation Assuring that a software system meets a user s needs Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 19,20 Slide 1
More informationManuel Oriol, CHCRC-C, Software Testing ABB
Manuel Oriol, CHCRC-C, 08.11.2017 Software Testing Slide 1 About me 1998 2004 2005 2008 2011 Slide 2 Introduction Why do we test? Did you have to deal with testing in the past? Slide 3 Ariane 5 http://www.youtube.com/watch?v=kyurqduyepi
More informationFacts About Testing. Cost/benefit. Reveal faults. Bottom-up. Testing takes more than 50% of the total cost of software development
Reveal faults Goals of testing Correctness Reliability Usability Robustness Performance Top-down/Bottom-up Bottom-up Lowest level modules tested first Don t depend on any other modules Driver Auxiliary
More information1 Visible deviation from the specification or expected behavior for end-user is called: a) an error b) a fault c) a failure d) a defect e) a mistake
Sample ISTQB examination 1 Visible deviation from the specification or expected behavior for end-user is called: a) an error b) a fault c) a failure d) a defect e) a mistake 2 Regression testing should
More informationBasic Training in Software Testing (2 Days)
www.peaklearningllc.com Basic Training in Software Testing (2 Days) This is a practical hands-on seminar to cover the critical path of testing. Your instructor will be an experienced practitioner in the
More informationQuality Assurance: Test Development & Execution. Ian S. King Test Development Lead Windows CE Base OS Team Microsoft Corporation
Quality Assurance: Test Development & Execution Ian S. King Test Development Lead Windows CE Base OS Team Microsoft Corporation Introduction: Ian King Manager of Test Development for Windows CE Base OS
More informationTHE AUTOMATED TEST FRAMEWORK
2017 THE AUTOMATED TEST FRAMEWORK Test More. Test Consistently. Test Faster. Secure Results. Delivered. xceleratesolutions.com TABLE OF CONTENTS CONCEPT...3 BENEFITS...4 TRANSFORMING FROM TRADITIONAL TO
More informationSoftware Engineering (CSC 4350/6350) Rao Casturi
Software Engineering (CSC 4350/6350) Rao Casturi Testing Software Engineering -CSC4350/6350 - Rao Casturi 2 Testing What is testing? Process of finding the divergence between the expected behavior of the
More informationQuality Assured SoC Design Using Crossfire. A Fractal whitepaper
Quality Assured SoC Design Using Crossfire A Fractal whitepaper Introduction There is no industry where the need for early bug-detection is more paramount than in SoC design. Consequences like design-re-spins
More informationProgramming Embedded Systems
Programming Embedded Systems Lecture 8 Overview of software testing Wednesday Feb 8, 2012 Philipp Rümmer Uppsala University Philipp.Ruemmer@it.uu.se 1/53 Lecture outline Testing in general Unit testing
More informationQuality Assurance = Testing? SOFTWARE QUALITY ASSURANCE. Meaning of Quality. How would you define software quality? Common Measures.
Quality Assurance = Testing? SOFTWARE QUALITY ASSURANCE William W. McMillan Meaning of Quality Error-free How define an error? Client is happy (we get paid!). User is happy (we are loved!). Stable (we
More informationSoftware Design Models, Tools & Processes. Lecture 6: Transition Phase Cecilia Mascolo
Software Design Models, Tools & Processes Lecture 6: Transition Phase Cecilia Mascolo UML Component diagram Component documentation Your own classes should be documented the same way library classes are.
More informationSoftware Reuse and Component-Based Software Engineering
Software Reuse and Component-Based Software Engineering Minsoo Ryu Hanyang University msryu@hanyang.ac.kr Contents Software Reuse Components CBSE (Component-Based Software Engineering) Domain Engineering
More informationHierarchical Clustering 4/5/17
Hierarchical Clustering 4/5/17 Hypothesis Space Continuous inputs Output is a binary tree with data points as leaves. Useful for explaining the training data. Not useful for making new predictions. Direction
More informationXP: Planning, coding and testing. Planning. Release planning. Release Planning. User stories. Release planning Step 1.
XP: Planning, coding and testing Annika Silvervarg Planning XP planning addresses two key questions in software development: predicting what will be accomplished by the due date determining what to do
More informationAssuring Certainty through Effective Regression Testing. Vishvesh Arumugam
Assuring Certainty through Effective Regression Testing Vishvesh Arumugam Agenda Introduction The Problem Magnitude Management Regression Test Efficiency Solution and Approach Test Suite Maintenance Determining
More information15. Regression testing
Outline 15. Regression testing Tom Verheyen, Jelle Slowack, Bart Smets, Glenn Van Loon Introduction - What, why, when, how - Regression faults - Test automation - Test suite maintenance - Reducing a test
More informationWhy testing and analysis. Software Testing. A framework for software testing. Outline. Software Qualities. Dependability Properties
Why testing and analysis Software Testing Adapted from FSE 98 Tutorial by Michal Young and Mauro Pezze Software is never correct no matter what developing testing technique is used All software must be
More informationMySQL Development Cycle
Abstract This document explains the MySQL Server development cycle. The purpose of the document is to facilitate community involvement, for example by providing feedback on pre-releases and making contributions
More informationLecture 20: SW Testing Presented by: Mohammad El-Ramly, PhD
Cairo University Faculty of Computers and Information CS251 Software Engineering Lecture 20: SW Testing Presented by: Mohammad El-Ramly, PhD http://www.acadox.com/join/75udwt Outline Definition of Software
More informationTesting Mission Critical Applications MCP UNITE 2012
Testing Mission Critical Applications MCP 4011 UNITE 2012 Who is MGS, Inc. Software Engineering, Product Development and Professional Services firm founded in 1986 We solve business problems with: Products,
More informationChapter 9 Quality and Change Management
MACIASZEK, L.A. (2007): Requirements Analysis and System Design, 3 rd ed. Addison Wesley, Harlow England ISBN 978-0-321-44036-5 Chapter 9 Quality and Change Management Pearson Education Limited 2007 Topics
More informationSoftware Testing Interview Question and Answer
Software Testing Interview Question and Answer What is Software Testing? A process of analyzing a software item to detect the differences between existing and required conditions (i.e., defects) and to
More informationChapter 11, Testing, Part 2: Integration and System Testing
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11, Testing, Part 2: Integration and System Testing Overview Integration testing Big bang Bottom up Top down Sandwich System testing
More informationPearson Education 2007 Chapter 9 (RASD 3/e)
MACIASZEK, L.A. (2007): Requirements Analysis and System Design, 3 rd ed. Addison Wesley, Harlow England ISBN 978-0-321-44036-5 Chapter 9 Quality and Change Management Pearson Education Limited 2007 Topics
More informationINTRODUCTION TO SOFTWARE ENGINEERING
INTRODUCTION TO SOFTWARE ENGINEERING Introduction to Software Testing d_sinnig@cs.concordia.ca Department for Computer Science and Software Engineering What is software testing? Software testing consists
More informationAppendix to The Health of Software Engineering Research
Appendix to The Health of Software Engineering Research David Lo School of Information Systems Singapore Management University Singapore davidlo@smu.edu.sg Nachiappan Nagappan and Thomas Zimmermann Research
More informationSoftware Testing. Testing: Our Experiences
Software Testing Testing: Our Experiences Test Case Software to be tested Output 1 Test Case Generation When to Stop? Test Case Software to be tested Verification Output No Enough? Test Coverage Yes A
More informationCS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS 1. Explain iterative waterfall and spiral model for software life cycle and various activities
More informationThe Bizarre Truth! Automating the Automation. Complicated & Confusing taxonomy of Model Based Testing approach A CONFORMIQ WHITEPAPER
The Bizarre Truth! Complicated & Confusing taxonomy of Model Based Testing approach A CONFORMIQ WHITEPAPER By Kimmo Nupponen 1 TABLE OF CONTENTS 1. The context Introduction 2. The approach Know the difference
More informationFour Essential Steps for Removing Risk and Downtime from Your POWER9 Migration
Four Essential Steps for Removing Risk and Downtime from Your POWER9 Migration Syncsort Four Essential Steps for Removing Risk and Downtime from Your POWER9 Migration With the introduction of IBM s POWER9
More informationCS 378: Computer Game Technology
CS 378: Computer Game Technology Dynamic Path Planning, Flocking Spring 2012 University of Texas at Austin CS 378 Game Technology Don Fussell Dynamic Path Planning! What happens when the environment changes
More informationARCHIVE ESSENTIALS
EMAIL ARCHIVE ESSENTIALS KEY CONSIDERATIONS WHEN MOVING TO OFFICE 365 DISCUSSION PAPER PREFACE The last few years have seen significant changes in the way that organisations conduct business. There has
More informationUp and Running Software The Development Process
Up and Running Software The Development Process Success Determination, Adaptative Processes, and a Baseline Approach About This Document: Thank you for requesting more information about Up and Running
More informationAbout Dean Leffingwell
Lean Practices for Foreword by Don Nonfunctional (System Qualities) Agile Style Reinertsen Development Series By and Ryan Shriver Agile 2010 Orlando, FL Lean Practices for Foreword by Don Reinertsen Development
More information