MSc Software Testing MSc Prófun hugbúnaðar
|
|
- David Edwards
- 5 years ago
- Views:
Transcription
1 MSc Software Testing MSc Prófun hugbúnaðar Fyrirlestrar 1 & 2 The SWEBOK Chapter on Software Testing IEEE 29/08/2007 Dr Andy Brooks 1
2 Repeat after Andy: software contains faults, software contains faults,... 29/08/2007 Dr Andy Brooks 2
3 Software testing consists of the dynamic verification of the behavior of a program on a finite set of test cases, suitably selected from the usually infinite executions domain, against the expected behavior. Static techniques (no execution) are beginning to mature. Exhaustive testing on even simple programs can take months or years. Selecting test techniques often relies on risk management and engineering expertise. Observed behavior can be checked against user expectations (validation), against a specification (verification), or against implicit requirements or reasonable expectations. 29/08/2007 Dr Andy Brooks 3
4 Testing is no longer seen as an activity which starts after the coding phase is complete, with the limited purpose of detecting failures. Planning for testing should begin when requirements are being specified. Testing should be done throughout development and maintenance. Corrective maintenance fixes faults after delivery. Even after extensive testing, software always contains faults. 29/08/2007 Dr Andy Brooks 4
5 Software Testing 1. Software Testing Fundamentals 2. Test Levels 3. Test Techniques 4. Test Related Measures Testing-Related Terminology Key Issues Relationships of Testing to Other Activities The Target of the Test Objectives of Testing Intuition and Experience Specificationbased Code-based Fault-based Evaluation of the Program Under Test Evaluation of the Tests Performed 5. Test Process Usage-based 29/08/2007 Dr Andy Brooks 5
6 1. Software Testing Fundamentals Faults vs. Failures A fault (defect) is the cause of a malfunction. A failure is an undesired effect observed during system operation. Testing can reveal failures, but it is the faults that can and must be removed... the cause of a failure cannot always be unequivocally identified. - requirements may have been poorly defined. 29/08/2007 Dr Andy Brooks 6
7 1. Software Testing Fundamentals 1.2 Key Issues Test selection criteria/test adequacy criteria What is a suitable set of test cases? Is a set of test cases adequate? Can the testing be stopped? Testing for defect identification A succesful test case is one which causes a failure. 29/08/2007 Dr Andy Brooks 7
8 1. Software Testing Fundamentals 1.2 Key Issues véfrétt The oracle problem A human or mechanical agent is needed to calculate the correct outcomes of tests. Can you rely on: i. the values of constants in books, ii. your pocket calculator, or iii hand calculations? 29/08/2007 Dr Andy Brooks 8
9 1. Software Testing Fundamentals 1.2 Key Issues Theoretical and practical limitations of testing Complete testing for real programs is not possible. Dijkstra: program testing can be used to show the presence of bugs, but never to show their absence The problem of infeasible paths There may be control flow paths that cannot be exercised by any input data. 29/08/2007 Dr Andy Brooks 9
10 1. Software Testing Fundamentals 1.2 Key Issues Testability How easy is it to test the software? Is technical documentation detailed, accurate, organised, and accessible? Is source code accessible? Is code modular and are coding standards used? Is software changed frequently? Frequent changes imply frequent disruptions to testing. Can tests be automated? Does the software suffer feature creep? Testing unncessary features is a waste of resources. 29/08/2007 Dr Andy Brooks 10
11 2. Test Levels 2.1 The target of the test the target of the test can vary: a single module, a group of such modules..., or a whole system. Three big test stages can be conceptually distinguished, namely Unit, Integration, and System. 29/08/2007 Dr Andy Brooks 11
12 2. Test Levels 2.1 The target of the test Unit testing Unit testing verifies the functioning in isolation of software pieces which are separately testable. Involves executing code. Testing can be performed by the developers themselves. 29/08/2007 Dr Andy Brooks 12
13 2. Test Levels 2.1 The target of the test Integration testing Integration testing is the process of verifying the interaction between software components. Traditional top-down or bottom-up strategies are used for traditional, hierarchically structured software. Modern integration testing involves identifying functional threads. The user enters a search term in the GUI dialogue box, which is transformed to an SQL query in the middle layer, and then the database in the bottom layer is queried... Mock objects may be needed if functionality is not currently implemented. program stubs 29/08/2007 Dr Andy Brooks 13
14 a b c l d e f g h i m j Procedures b and c could be stubbed in a top-down approach. Procedures e and g could be stubbed in a bottom-up approach. l, m, or n could be mock objects. n 29/08/2007 Dr Andy Brooks 14
15 2. Test Levels 2.1 The target of the test System testing System testing is concerned with the behavior of a whole system. Most faults should have already been identified during unit and integration testing. System testing often involves testing the non-functional requirements: Security Speed Accuracy Reliability System testing often also involves testing external interfaces to other software and hardware. 29/08/2007 Dr Andy Brooks 15
16 2. Test Levels 2.2 Objectives of Testing Acceptance/qualification testing Acceptance testing checks the system behavior against the customer s requirements, however these may have been expressed. Customers or developers may undertake typical tasks Installation testing Installation testing is much like system testing except the software has now been installed in the target environment Alpha and beta testing This testing involves trial usage in-house (alpha) or by external parties (beta). 29/08/2007 Dr Andy Brooks 16
17 2. Test Levels 2.2 Objectives of Testing Conformance/Functional/Correctness testing Does the observed behavior of the software conform to the specification? The program should read in four integers, either in a single line or on separate lines. The first integer represents a year (y), the second integer represents a month (m), the third integer represents a day (d), and the fourth integer represents a wind speed in mph (w). The program should output historical statements such as: On that Monday it was an F5 tornado. The program must calculate the tornado strengths according to the following table: Force description speed (in mph) F0 light F1 moderate F2 considerable F3 severe F4 devastating F5 incredible
18 Frequently Asked Questions about Calendars Version 2.8 Claus Tøndering 15 December What is the Julian calendar? The Julian calendar was introduced by Julius Caesar in 45 BC. It was in common use until the late 1500s, when countries started changing to the Gregorian calendar (section 2.2). However, some countries (for example, Greece and Russia) used it into the early 1900s, and the Orthodox church in Russia still uses it, as do some other Orthodox churches. 29/08/2007 Dr Andy Brooks 18
19 2. Test Levels 2.2 Objectives of Testing Reliability achievement and evaluation Statistical measures of reliability can be achieved by generating random test cases according to the operational profile. 1 failure every 5000 logical tasks. 1 failure every logical tasks. 1 failure every logical tasks.? Frequency of logical tasks in internet banking Login and password...33% Display account information...33% Pay bill...25% Transfer money between accounts...5% O.s.f. operational profile 29/08/2007 Dr Andy Brooks 19
20 2. Test Levels 2.2 Objectives of Testing Regression testing Regression testing is the selective retesting of a system or component to verify that modifications have not caused unintended effects... (Retesting using all the tests is very expensive in terms of time and resources, but it is the safest thing to do.) Performance testing Does the software meet performance requirements such as capacity and response time? 29/08/2007 Dr Andy Brooks 20
21 2. Test Levels 2.2 Objectives of Testing Stress testing The software is tested beyond the maximum design load. number of simultaneous users number of simultaneous applications very large file transfers osf Back-to-back testing The same set of tests is applied to two versions of the system and the results compared. 29/08/2007 Dr Andy Brooks 21
22 2. Test Levels 2.2 Objectives of Testing Recovery testing Recovery testing checks restart capability after a crash Configuration testing Configuration testing analyses the software under different memory, network, server, database, browser,... configurations. 29/08/2007 Dr Andy Brooks 22
23 2. Test Levels 2.2 Objectives of Testing Usability testing How easy is it for users to learn to use the software? How long do users take to recover from mistakes? ATMs have a walk-up-and-use useability requirement Test-driven development (TDD) Tests cases are written before the code is executed. Under TDD, sometimes, less attention is paid to producing software requirement specification documents. 29/08/2007 Dr Andy Brooks 23
24 3. Test Techniques 3.1 Intuition and experience Ad hoc testing í sérstöku augnamiði Tests are based on skill, intuition, and experience with similar programs. A widely practiced technique. things that are empty division by 0 overflow characters in a numeric field Exploratory testing Tests are dynamically designed, executed and modified. Not defined in advanced. 29/08/2007 Dr Andy Brooks 24
25 3. Test Techniques 3.2. Specification-based world s oldest woman is 125? Equivalence partition The input domain is divided into subsets of equivalent classes and an input is taken from each subset as being representative of the class. Age<0 ( -5 ), 0<=Age<=135 ( 45 ), Age >135 ( 142 ) Equivalence partitioning may also involve classes such as: is a number and is not a number number of inputs The size of the set of test cases (test suite) can grow very quickly. 29/08/2007 Dr Andy Brooks 25
26 3. Test Techniques 3.2. Specification-based world s oldest woman is 125? Boundary-value analysis Test cases are chosen near boundaries of the input domain since faults tend to be found near extreme values. Robustness testing is an extension of this technique and includes values outside the input domain. Age ( -1, 0, 1 ) ( 134, 135, 136) 29/08/2007 Dr Andy Brooks 26
27 3. Test Techniques 3.2. Specification-based Decision Table (Cause-Effect Graphing) Decision tables represent relationships between conditions (inputs) and actions (outputs). Test cases are derived by considering all possible combination of conditions and actions. If the customer is billed using a fixed rate method, a fixed monthly charge applies if electricity used is less than 100 kwh. If electricity usage is greater, then the customer is charged according to Schedule A. If the customer is billed using a variable rate method, Schedule A charging applies to the first 100 kwh of electricity consumption and Schedule B charging to additional consumption. example 29/08/2007 Dr Andy Brooks 27
28 Decision Table example conditions fixed rate account T T F F variable rate account F F T T < 100 kwh T F T F >= 100kwh F T F T actions fixed monthly charge x Schedule A charging x x x Schedule B charging x 4 rules 4 tests 29/08/2007 Dr Andy Brooks 28
29 3. Test Techniques 3.2. Specification-based Finite-state machine-based The program is modelled as a finite-state machine and tests derived to cover the states and transitions Testing from formal specifications Tests can be derived from specifications written in a formal language Random testing Tests are generated at random. The input domain is sampled at random. 29/08/2007 Dr Andy Brooks 29
30 3. Test Techniques 3.3. Code-based Control-flow based criteria If The strongest criteria is path testing: all entry-to-exit control flow paths in the flowgraph are excuted. Other criteria are statement testing, branch testing, condition/decision testing. Adequacy is measure by the coverage achieved by the set of tests cases (test suite) expressed as a percentage: e.g. 100% statement coverage 29/08/2007 Dr Andy Brooks 30
31 // Pay overtime at "time and a half" if (hours > STANDARD) pay = STANDARD*RATE+(hours-STANDARD)*(RATE*1.5); else pay = hours*rate; If A single test may involve executing the if-else statement, so the statement is covered. But a single test will mean the condition only takes one of its two possible values (TRUE,FALSE) and only one of the two possible branches are executed. The condition and branches are not fully covered. 29/08/2007 Dr Andy Brooks 31
32 3. Test Techniques 3.3. Code-based Data-flow based criteria double pay = 0.0; How are variables defined, used, and killed (undefined)? The strongest criteria, all definition-use paths, requires that for each variable, every control flow path segment from a definition of that variable to a use of that definition is executed. A weaker criteria is all-uses. double pay = 0.0; System.out.print ("Enter the number of hours worked: "); int hours = scan.nextint(); System.out.println (); // Pay overtime at "time and a half" if (hours > STANDARD) pay = STANDARD*RATE+(hours-STANDARD)*(RATE*1.5); else pay = hours*rate; NumberFormat fmt = NumberFormat.getCurrencyInstance(); System.out.println ("Gross earnings: " + fmt.format(pay)); 29/08/2007 Dr Andy Brooks 32
33 3. Test Techniques 3.4. Fault-based Error guessing Test cases are designed with the aim of identifying likely faults in a program given a history of faults in earlier projects, as well as the experience of the software engineer Mutation testing A mutant is a slightly modified version of a program ( negate decision or replace operator,...). The test suite is modified so that a test case kills the mutant. 29/08/2007 Dr Andy Brooks 33
34 3. Test Techniques 3.5. Usage-based Operational profile The test environment reproduces the operational environment of the software. Future reliability of the software can be estimated from the results. Test inputs are assigned a probability distribution according to their occurrence in actual operation. 29/08/2007 Dr Andy Brooks 34
35 3. Test Techniques 3.6. Nature of application Specialized testing fields: Object-oriented testing. Component-based testing. Web-based testing. GUI testing. Concurrent programs. Protocol conformance. Real-time systems. Safety-critical systems. 29/08/2007 Dr Andy Brooks 35
36 3. Test Techniques 3.7. Select and combine Functional and structural Specification (functional) and code-based (structural) techniques should not be seen as alternative but as complementary Deterministic and random Select and combine techniques. 29/08/2007 Dr Andy Brooks 36
MSc Software Testing and Maintenance MSc Prófun og viðhald hugbúnaðar
MSc Software Testing and Maintenance MSc Prófun og viðhald hugbúnaðar Fyrirlestrar 25 & 26 The SWEBOK Chapter on Software Testing IEEE http://www.swebok.org/ 19/10/2005 Dr Andy Brooks 1 Repeat after Andy:
More information9. Verification, Validation, Testing
9. Verification, Validation, Testing (a) Basic Notions (b) Dynamic testing. (c) Static analysis. (d) Modelling. (e) Environmental Simulation. (f) Test Strategies. (g) Tool support. (h) Independent Verification
More informationINTRODUCTION. It is the process used to identify the correctness, completeness and quality of developed computer software.
INTRODUCTION It is the process used to identify the correctness, completeness and quality of developed computer software. It is the process of executing a program/application under positive and negative
More informationIntroduction to Software Engineering
Introduction to Software Engineering (CS350) Lecture 16 Jongmoon Baik Software Testing Strategy 2 What is Software Testing? Testing is the process of exercising a program with the specific intent of finding
More informationTesting. CxOne Standard
Testing CxOne Standard CxStand_Testing.doc November 3, 2002 Advancing the Art and Science of Commercial Software Engineering Contents 1 INTRODUCTION... 1 1.1 OVERVIEW... 1 1.2 GOALS... 1 1.3 BACKGROUND...
More informationDHANALAKSHMI COLLEGE OF ENGINEERING, CHENNAI DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING IT6004 SOFTWARE ESTING UNIT I : INTRODUCTION
DHANALAKSHMI COLLEGE OF ENGINEERING, CHENNAI DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING IT6004 SOFTWARE ESTING UNIT I : INTRODUCTION PART A (2 Marks) 1) Define Software Engineering. Software Engineering
More informationTesting and Inspections (3C05/D22) Unit 11: Testing and Inspection. What is Testing?
Testing and Inspections (3C05/D22) Unit 11: Testing and Inspection Objectives To introduce software testing and to develop its role within the software development process. To introduce the use of formal
More informationBook Outline. Software Testing and Analysis: Process, Principles, and Techniques
Book Outline Software Testing and Analysis: Process, Principles, and Techniques Mauro PezzèandMichalYoung Working Outline as of March 2000 Software test and analysis are essential techniques for producing
More informationISTQB-Level1 ASTQB. American Software Testing Qualifications Board Level 1
ASTQB ISTQB-Level1 American Software Testing Qualifications Board Level 1 Download Full Version : https://killexams.com/pass4sure/exam-detail/istqb-level1 QUESTION: 46 Comparing TMMi and TPI, which is
More informationISTQB Certified Tester. Foundation Level. Sample Exam 1
ISTQB Certified Tester Foundation Level Version 2015 American Software Testing Qualifications Board Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged.
More informationLed by the Author Attended by a peer group Varying level of formality Knowledge gathering Defect finding
Technical Review Walkthrough Review Inspection Review Informal Review A Technical Review is a type of peer review, and is considered to be a formal review type, even though no Managers are expected to
More informationTesting Masters Technologies
1. How will you receive the project requirements? A. The finalized SRS will be placed in a project repository; we will access it from there 2. What will you do with SRS? A. SRS stands for software requirement
More informationIT6004/ Software Testing Unit-I
Question Bank: IT6004/ Software Testing Unit-I 1) Define Software Engineering. Software Engineering is a discipline that produces error free software with in a time and budget. 2) Define software Testing.
More informationTesting 2. Testing: Agenda. for Systems Validation. Testing for Systems Validation CONCEPT HEIDELBERG
CONCEPT HEIDELBERG GMP Compliance for January 16-17, 2003 at Istanbul, Turkey Testing for Systems Validation Dr.-Ing. Guenter Generlich guenter@generlich.de Testing 1 Testing: Agenda Techniques Principles
More informationT Software Testing and Quality Assurance Test Planning
T-76.5613 Software Testing and Quality Assurance 10.10.2007 Test Planning Juha Itkonen Outline Test planning, purpose and usage of a test plan Topics of test planning Exercise References: IEEE Std 829-1998,
More informationA Review Paper on Software Testing
A Review Paper on Software Testing Amit M. Kale 1, Vivek V. Bandal 2, Komal Chaudhari 3 1,2Bachelor Student, Dept. of Electrical Engineering 3Professor, Dept. of Computer Engineering ----------------------------------------------------------------------***---------------------------------------------------------------------
More informationIT Software Testing
IT6004 - Software Testing Unit-I Introduction 1.1 The Evolving Profession of Software Engineering the development process is well understood; projects are planned; life cycle models are defined and adhered
More informationTesting Close to and Post-Release: System, Acceptance, and Regression Testing
Testing Close to and Post-Release: System, Acceptance, and Regression Testing CSCE 747 - Lecture 23-04/05/2016 The V-Model of Development Requirements Elicitation System Specification Acceptance Test Plan
More informationBugs are costly... Kinds of Quality Assurance
Bugs are costly... 1. Types of bugs (What type of bugs have you had in the past?) a. Race conditions and deadlocks b. Library misuse c. Logical errors (off by one, null, buffer overflow) d. Usability e.
More informationSoftware Engineering
Software Engineering (CS550) Software Testing - I Jongmoon Baik Objectives To define and understand what software testing is To understand software testing strategies To describe software testing processes
More informationIT6004/ Software Testing
1) Define Software Engineering. Software Engineering is a discipline that produces error free software with in a time and budget. 2) Define software Testing. Testing can be described as a process used
More informationFunctional Testing. CSCE Lecture 4-01/21/2016
Functional Testing CSCE 747 - Lecture 4-01/21/2016 How do you come up with test cases? Test Plans Plan for how we will test the system. What is being tested (units of code, features). When it will be tested
More informationCost-Effective Verification and Validation of Modeling and Simulation
Cost-Effective Verification and Validation of Modeling and Simulation Dr. Dave Cook The AEgis Technologies Group, Inc. Purpose of This Talk Show what V&V is (and what it is not!) and how it applies to
More informationSE420 Software Quality Assurance
SE420 Software Quality Assurance Lecture 1 Introduction Part-2 January 16, 2017 Sam Siewert Course Learning Objectives Theory of Overall SQA Process Process Models (Waterfall, Spiral, XP) using Agile Strategy
More informationISTQB Sample Question Paper Dump #11
ISTQB Sample Question Paper Dump #11 1. Which of the following is true a. Testing is the same as quality assurance b. Testing is a part of quality assurance c. Testing is not a part of quality assurance
More informationSoftware processes, quality, and standards VTV, fast methods, automation
Software processes, quality, and standards VTV, fast methods, automation Jaak Tepandi, Jekaterina Tšukrejeva, Stanislav Vassiljev, Pille Haug Tallinn University of Technology Department of Software Science
More informationStandard Glossary of Terms used in Software Testing. Version 3.2. Terms Changed since 01-Feb-2018
Standard Glossary of Terms used in Software Testing Version 3.2 International Software Testing Qualifications Board Copyright Notice This document may be copied in its entirety, or extracts made, if the
More informationTesting throughout the software life cycle. Software Testing: INF3121 / INF4121
Testing throughout the software life cycle Software Testing: INF3121 / INF4121 Summary: Week 2 Software development models Sequential / Iterative-Incremental / Testing within a life cycle Test levels Component
More informationExam questions- examples
Exam questions- examples The following are examples of exam questions. At the exam there will be similar questions with similar level of difficulty. In the question pool there will be questions related
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Building Skills is a 3-day course that is a subset of our course. The course is designed to provide a fundamental knowledge base and practical skills for anyone interested in implementing or improving
More informationSoftware Quality Factors
Software Quality Factors The need for a comprehensive software quality requirements There are some characteristic common : All the software projects satisfactory fulfilled the basic requirements for correct
More informationIntroduction to Verification and Test of Embedded Systems SE767: Vérification & Test
Introduction to Verification and Test of Embedded Systems SE767: Vérification & Test Ulrich Kühne ulrich.kuhne@telecom-paristech.fr 26/11/2018 Objectives of this Course Understanding the role of test &
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Courses is a 2-day course that is a subset of our course. The course is designed to provide an overview of techniques and practices. This course starts with an overview of software quality engineering
More informationTest s in i g n I Week 14
Testing I Week 14 Agenda (Lecture) Concepts and principles of softwaretesting testing Verification and validation Non execution based testing Execution based testing Feasibility of testing to specification
More informationBACKGROUND OF TESTING 4. The fundamental principles of the testing are as follows.
BACKGROUND OF TESTING 4 CHAPTER-2 BACKGROUND OF TESTING Testing is a means of making sure that the product meets the needs of the customer. Software Testing is the process of exercising the software product
More informationSoftware Testing Life Cycle
Software Testing Life Cycle STLC (Software Testing Life Cycle) is an integral component of SDLC (Software Development Life Cycle). Testing has become a distinct phenomenon during and after the development
More informationManual Testing Step by Step Tutorial
Manual Testing Step by Step Tutorial 1) Software Development Life Cycle and SDLC Model i) Requirement Gathering ii) Analysis iii) Design iv) Coding / Development v) Testing vi) Deployment & Maintenance
More informationThis document describes the overall software development process of microcontroller software during all phases of the Company Name product life cycle.
Maturity Process Owner Check Release Description Valid Name / Department Name / Department Name / Department Detailed procedure for software development Title: Software Development Procedure Purpose: This
More informationSoftware Testing(TYIT) Software Testing. Who does Testing?
Software Testing(TYIT) Software Testing Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. In simple words,
More informationSkill Category 7. Quality Control Practices
Skill Category 7 Quality Control Practices Testing Concepts Developing Testing Methodologies Verification and Validation Methods Software Change Control Defect Management Process Management Processes CSQA
More informationINF 3121 Software Testing - Lecture 05. Test Management
INF 3121 Software Testing - Lecture 05 Test Management 1. Test organization (20 min) (25 min) (15 min) (10 min) (10 min) (10 min) INF3121 / 23.02.2016 / Raluca Florea 1 1. Test organization (20 min) LO:
More informationVALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur
VALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur 603203. DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Year & Semester : III & VI Section : CSE 1 Subject Code : IT6004 Subject Name : SOFTWARE
More informationIntroduction to Software Testing Chapter 1 Introduction Paul Ammann & Jeff Offutt
Introduction to Software Testing Chapter 1 Introduction Paul Ammann & Jeff Offutt www.introsoftwaretesting.com 1. Why do we test? A Talk in 3 Parts 2. What should we do during testing? 3. How do we get
More informationRequirements Engineering: Part I. Software Requirements & Project Management CITS3220
Requirements Engineering: Part I Software Requirements & Project Management CITS3220 The Problems of Requirements What goal(s) are we trying to satisfy? How do we identify the scope and properties of the
More informationTest Management: Part I. Software Testing: INF3121 / INF4121
Test Management: Part I Software Testing: INF3121 / INF4121 Summary: Week 6 Test organisation Independence Tasks of the test leader and testers Test planning and estimation Activities Entry and exit criteria
More informationISTQB CTFL BH0-010 Exam Practice Question Paper
ISTQ TFL H0-010 Exam Practice Question Paper For Software Testing rticlesvisit @ http://softwaretestinghelp.com Join the est Software Testing Training ourse @ http://softwaretestinghelp.org QUESTION 1:
More informationMeasuring and Assessing Software Quality
Measuring and Assessing Software Quality Issues, Challenges and Practical Approaches Kostas Kontogiannis Associate Professor, NTUA kkontog@softlab.ntua.gr The Software Life Cycle Maintenance Requirements
More informationIntroduction To Software Testing. Brian Nielsen. Center of Embedded Software Systems Aalborg University, Denmark CSS
Introduction To Software Testing Brian Nielsen bnielsen@cs.auc.dk Center of Embedded Software Systems Aalborg University, Denmark CSS 1010111011010101 1011010101110111 Software development cycle 1. Programmer
More informationVector Software. Understanding Verification and Validation of software under IEC :2010 W H I T E P A P E R
Vector Software W H I T E P A P E R Understanding Verification and Validation of software under IEC 61508-3:2010 Abstract This paper is intended to serve as a reference for developers of systems that will
More informationBrief Summary of Last Lecture. Model checking of timed automata: general approach
Brief Summary of Last Lecture Formal verification Types: deductive (theorem proving) and algorithmic (model checking) ields proof that a (formal) specification is fulfilled Formalization of specs e.g.
More informationCLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS
More informationSoftware Reliability and Testing: Know When To Say When. SSTC June 2007 Dale Brenneman McCabe Software
Software Reliability and Testing: Know When To Say When SSTC June 2007 Dale Brenneman McCabe Software 1 SW Components with Higher Reliability Risk, in terms of: Change Status (new or modified in this build/release)
More informationISTQB Advanced Technical Test Analyst Certificate in Software Testing
ISTQB Advanced Technical Test Analyst Certificate in Software Testing Sample Paper A - 1 Hour Examination This is not a complete exam paper Record your surname/last/family name and initials on the Answer
More informationAppendix C: MS Project Software Development Plan and Excel Budget.
1. Introduction. Appendix C: MS Project Software Development Plan and Excel Budget. Project: PickUp Game App The Project plan for this Application consist of 76 days; In this plan is defined how long each
More informationBlack box testing. What is Black Box testing? Error Guessing. What is Black Box testing?
What is Black Box testing? Black box testing Testing without having an insight into the details of underlying code input Unit output Testing based on specification What is Black Box testing? Ignores internal
More informationR214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM
A2LA R214 Specific Requirements: Information Technology Testing Laboratory Accreditation Document Revised: 3/5/18 Page 1 of 34 R214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION
More informationR.POONKODI, ASSISTANT PROFESSOR, COMPUTER SCIENCE AND ENGINEERING, SRI ESHWAR COLLEGE OF ENGINEERING, COIMBATORE.
R.POONKODI, ASSISTANT PROFESSOR, COMPUTER SCIENCE AND ENGINEERING, SRI ESHWAR COLLEGE OF ENGINEERING, COIMBATORE. UNIT I INTRODUCTION Testing as an Engineering Activity Testing as a Process Testing axioms
More informationRelease Notes. Standard Glossary of Terms used in. Software Testing. Version 3.2
Standard Glossary of Terms used in Release Notes Standard Glossary of Terms used in Version 3.2 Copyright Notice This document may be copied in its entirety or extracts made if the source is acknowledged.
More informationIntroduction to Software Testing
Introduction to Software Testing Introduction Chapter 1 introduces software testing by : describing the activities of a test engineer defining a number of key terms explaining the central notion of test
More informationBabu Madhav Institute Of Information Technology,UTU
UNIT: 1 Introduction Short Questions: 1. List the two types of software analyst? 2. What is the role of software test analyst? 3. Define Software Testing 4. Define verification. 5. Define validation. 6.
More informationISEB ISTQB Sample Paper
[2011] ISEB ISTQB Sample Paper [BH0-010 ISEB ISTQB FOUNDATION LEVEL] This sample is based on the latest syllabus of ISTQB Foundation Level prepared by For more sample papers visit /istqb.aspx Total Questions:
More informationISTQB CTFL BH QuestionsAnswers with Explanation
ISTQB CTFL BH0-10 - QuestionsAnswers with Explanation For Software Testing Articles Visit @ http://softwaretestinghelp.com Join the Best Software Testing Training Course @ http://softwaretestinghelp.org
More informationContractual Aspects of Testing Some Basic Guidelines CONTENTS
CONTENTS 1 Introduction... 1 1.1 Background... 1 1.2 Structure... 1 1.3 Some Conventions... 1 1.4 Feedback... 1 2 Test Schedule List of Contents... 2 3 Testing Deliverables... 3 4 Coverage Guidance...
More informationSE420 Software Quality Assurance
SE420 Software Quality Assurance Lecture 2 Software Specification Part-1 January 16, 2017 Sam Siewert SQA LO s (Learning Objectives) Theory and Principles 1. Coverage of Current SQA Theory and Practice
More informationSurviving the Top Ten Challenges of Software Testing
Surviving the Top Ten Challenges of Software Testing: A Closer Look at Understanding Software Testing Randy Rice, CQA, CSTE Rice Consulting Services, Inc. 405-692-7331 http://www.riceconsulting.com rcs@telepath.com
More informationIntegration and Testing
Integration and Testing 1 Today Software Quality Assurance Integration Test planning Types of testing Test metrics Test tools 2 Deliverables by Phase Possible Deliverables by Phase Concept Document Statement
More informationLECTURE 6 LEVELS OF SOFTWARE TESTING
LECTURE 6 LEVELS OF SOFTWARE TESTING UNIT TESTING Unit testing is a level of software testing where individual units/ components of software are tested. The purpose is to validate that each unit of the
More informationVector Software W H I T E P A P E R. Using VectorCAST for Software Verification and Validation of Railway Applications
Vector Software W H I T E P A P E R Using VectorCAST for Software Verification and Validation of Railway Applications Introduction This document is intended to serve as a reference for the usage of VectorCAST
More informationSample. NI TestStand TM I: Introduction Course Manual
NI TestStand TM I: Introduction Course Manual Course Software Version 4.0 July 2007 Edition Part Number 322317J-01 NI TestStand I: Introduction Course Manual Copyright 1999 2007 National Instruments Corporation.
More informationSHRI ANGALAMMAN COLLEGE OF ENGINEERING & TECHNOLOGY (An ISO 9001:2008 Certified Institution) SIRUGANOOR,TRICHY
SHRI ANGALAMMAN COLLEGE OF ENGINEERING & TECHNOLOGY (An ISO 9001:2008 Certified Institution) SIRUGANOOR,TRICHY-621105. DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS1301- SOFTWARE ENGINEERING UNIT I
More informationMTAT : Software Testing
MTAT.03.159: Software Testing Lecture 01: Introduction to Software Testing (Textbook Ch. 1-3) Spring 2016 Dietmar Pfahl email: dietmar.pfahl@ut.ee Structure of Lecture 1 Introduction and Motivation Course
More informationAn Intuitive Approach to Determine Test Adequacy in Safety-critical Software
An Intuitive Approach to Determine Test Adequacy in Safety-critical Software P. Arun Babu, C. Senthil Kumar, N. Murali, T. Jayakumar ACM SIGSOFT Software Engineering, Vol. 37, 2012 2013. 3. 27. Presented
More informationIntroduction to software testing and quality process
Introduction to software testing and quality process Automated testing and verification J.P. Galeotti - Alessandra Gorla Engineering processes Engineering disciplines pair construction activities activities
More informationComputerized global management of maintenance
Computerized global management of maintenance Linx 7.0 is a program that makes easy and automates the management of the Maintenance department, allows an exhaustive control of all the tasks (Preventive,
More informationISTQB CTFL BH0-010 Exam Practice Question Paper
ISTQB TFL BH0-010 Exam Practice Question Paper For Software Testing rticlesvisit @ http://softwaretestinghelp.com Join the Best Software Testing Training ourse @ http://softwaretestinghelp.org QUESTION
More informationInternational Journal of Advanced Research in Computer Science and Software Engineering
Volume 2, Issue 8, August 2012 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Improvement in
More information1. Can you explain the PDCA cycle and where testing fits in?
1. Can you explain the PDCA cycle and where testing fits in? Software testing is an important part of the software development process. In normal software development there are four important steps, also
More informationFundamentals of Dynamic Testing. Inaccuracy in Dynamic Testing
Fundamentals of Dynamic Testing Three questions: How shall we tell if a test has succeeded or failed? [More next week on this, as well as process issues] How shall we select test cases? How do we know
More informationImplement Effective Computer System Validation. Noelia Ortiz, MME, CSSGB, CQA
Implement Effective Computer System Validation Noelia Ortiz, MME, CSSGB, CQA Session Outline 1 2 3 4 5 Understanding Regulations and Guidelines Pertaining to Computer Systems Integrate SDLC and GAMP 5
More informationTesting. Testing is the most important component of software development that must be performed throughout the life cycle
Testing Testing is the most important component of software development that must be performed throughout the life cycle Testing must be carried out by developers continuously More methodical testing must
More informationSoftware Quality. A Definition of Quality. Definition of Software Quality. Definition of Implicit Requirements
Definition of Software Quality Software Quality The Ultimate Goal of Software Engineering Software must conformance to explicit and implicit requirements if it is to be considered to be of good quality.
More informationImportance of Software Testing with Study of Various Testing Techniques & Automation Tools
Importance of Software Testing with Study of Various Testing Techniques & Automation Tools Shikha Nandi B. Tech (CSE), Galgotias University, Greater Noida, Uttar Pradesh, India Abstract- Software testing
More informationSecond Generation Model-based Testing
CyPhyAssure Spring School Second Generation Model-based Testing Provably Strong Testing Methods for the Certification of Autonomous Systems Part I of III Motivation and Challenges Jan Peleska University
More informationIntroducing Structured Testing
Introducing Structured Testing Master s Thesis Lund 2008-06-16 Author: Hanna Färnstrand Supervisors: Henrik Andersson, Sogeti Lars Hall, Apptus Technologies Patrik Wåhlin, Apptus Technologies Examiner:
More informationWork Plan and IV&V Methodology
Work Plan and IV&V Methodology Technology initiatives and programs should engage with an IV&V process at the project planning phase in order to receive an unbiased, impartial view into the project planning,
More informationDisciplined Software Testing Practices
isciplined oftware Testing Practices r. Magdy Hanna Chairman International Institute for oftware Testing ponsored by: International Institute for oftware Testing International Institute for oftware Testing,
More informationKINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK
KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK Subject Code & Subject Name: IT1251 Software Engineering and Quality Assurance Year / Sem : II / IV UNIT I SOFTWARE PRODUCT
More informationSQA: The Monitoring & Measuring the strength of development process is called SQA (Software Quality Assurance).
Page 1 SOFTWARE TESTING CONCEPTS Requirement s Gathering (BRS) Software Quality: - Software should i. Meet Customer requirements ii. Meet Customer expectations QUALITY iii. Cost to Purchase (Economical)
More informationQuality Standards in Open Source Lifecycle
Quality Standards in Open Source Lifecycle Bogdan VINTILA Academy of Economic Studies, Bucharest, Romania vb@vintilabogdan.ro Abstract: Open source applications and components are very important for the
More informationTesting. And Software Product Management. Autumn 2017 CSM14104 Software Product Management 1
Testing And Software Product Management Autumn 2017 CSM14104 Software Product Management 1 Lecture Outline and learning objectives What is testing? Definition Limits of testing Test strategy Testing in
More informationExam questions- examples
Exam questions- examples The following are examples of exam questions. At the exam there will be similar questions with similar level of difficulty. In the question pool there will be questions related
More informationQUMU CLOUD PLATFORM CUSTOMER SUPPORT AGREEMENT
QUMU CLOUD PLATFORM CUSTOMER SUPPORT AGREEMENT I. DEFINITIONS "Approved Support Contacts" means CUSTOMER employees that are authorized to initiate Support Requests with QUMU Customer Support and that are
More informationKNOWLEDGE AREA: SOFTWARE QUALITY
KNOWLEDGE AREA: SOFTWARE QUALITY 1. Introduction Software Quality Assurance (SQA) and Verification and Validation (V&V) are the processes of the Knowledge Area on Software Quality. The scope of this Knowledge
More informationMANAGEMENT INFORMATION SYSTEMS COURSES Student Learning Outcomes 1
MANAGEMENT INFORMATION SYSTEMS COURSES Student Learning Outcomes 1 MIS 180: Principles of Information Systems 1. Explain the importance of determining information system requirements for all management
More informationIntroduction to Software Engineering
CHAPTER 1 Introduction to Software Engineering Structure 1.1 Introduction Objectives 1.2 Basics of Software Engineering 1.3 Principles of Software Engineering 1.4 Software Characteristics 1.5 Software
More informationISTQB CTFL BH0-010 Exam Practice Question Paper
ISTQ TFL H0-010 Exam Practice Question Paper For Software Testing rticlesvisit @ http://softwaretestinghelp.com Join the est Software Testing Training ourse @ http://softwaretestinghelp.org QUESTION 1:
More informationSoftware Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement
Tian: Software Quality Engineering Slide (Ch.7) 1 Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement Jeff Tian, tian@engr.smu.edu www.engr.smu.edu/ tian/sqebook Chapter
More informationJava & Testing. Slides adapted from Craig Zilles
Java & Testing Slides adapted from Craig Zilles 1 Things to have been doing join UIUC CS 126 on piazza.com get an iclicker registered at http://iclicker.com get a GitHub account install IntelliJ on to
More informationON THE USE OF BASE CHOICE STRATEGY FOR TESTING INDUSTRIAL CONTROL SOFTWARE
School of Innovation Design and Engineering Västerås, Sweden Thesis for the Degree of Bachelor of Science in Computer Science 15.0 credits ON THE USE OF BASE CHOICE STRATEGY FOR TESTING INDUSTRIAL CONTROL
More informationIntermediate Certificate in Software Testing Syllabus. Version 1.4
Intermediate Certificate in Software Testing Syllabus February 2010 Background This document is the syllabus for the intermediate paper which leads to the practitioner level of qualification, as administered
More information