Importance of testing Difference between Errors and Faults The purpose of test data Importance of: – Testing – Test Plans.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Test process essentials Riitta Viitamäki,
Lecture 8: Testing, Verification and Validation
Verification and Validation
©G. Millbery 2003Data, Information, Knowledge and Processing Slide 1 Testing  Every system must be reliable and the data it produces trusted  This is.
P5, M1, D1.
1 Software Engineering Lecture 11 Software Testing.
Software Failure: Reasons Incorrect, missing, impossible requirements * Requirement validation. Incorrect specification * Specification verification. Faulty.
Requirements and Design
Black-box Testing Lakeisha Dubose November 30, 2006 CSCI 362.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Testing an individual module
Lecture 9 Testing Topics TestingReadings: Spring, 2008 CSCE 492 Software Engineering.
OHT 9.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 9.3 Software Testing Strategies.
Testing Test Plans and Regression Testing. Programs need testing! Writing a program involves more than knowing the syntax and semantics of a language.
Copyright © 2015 Pearson Education, Inc. Processing Integrity and Availability Controls Chapter
1 Functional Testing Motivation Example Basic Methods Timing: 30 minutes.
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
System/Software Testing
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
1 Shawlands Academy Higher Computing Software Development Unit.
Chapter 8: Systems analysis and design
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Software Engineering Chapter 23 Software Testing Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
1 Debugging and Testing Overview Defensive Programming The goal is to prevent failures Debugging The goal is to find cause of failures and fix it Testing.
Chapter 8 – Software Testing Lecture 1 1Chapter 8 Software testing The bearing of a child takes nine months, no matter how many women are assigned. Many.
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
Installation and Maintenance of Health IT Systems
Systems Development Lifecycle Testing and Documentation.
Testing E001 Access to Computing: Programming. 2 Introduction This presentation is designed to show you the importance of testing, and how it is used.
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.
SE: CHAPTER 7 Writing The Program
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
Systems Life Cycle. Know the elements of the system that are created Understand the need for thorough testing Be able to describe the different tests.
Code Complete Steve McConnell. 20. The Software-Quality Landscape.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
The Software Development Process
Chapter 8 Lecture 1 Software Testing. Program testing Testing is intended to show that a program does what it is intended to do and to discover program.
Project roles and responsibilities
Test Case Designing UNIT - 2. Topics Test Requirement Analysis (example) Test Case Designing (sample discussion) Test Data Preparation (example) Test.
Software Quality Assurance and Testing Fazal Rehman Shamil.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
 Software reliability is the probability that software will work properly in a specified environment and for a given amount of time. Using the following.
Testing i. explain the importance of system testing and installation planning;
Testing 1. Aims To understand the purpose of testing To understand the different test strategies To explore the four types of test data Have a understanding.
In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing:
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Highcliffe ICT Department
Testing Tutorial 7.
Processing Integrity and Availability Controls
Testing and Test-Driven Development CSC 4700 Software Engineering
G063 - Testing.
Informatics 43 – April 28, 2016.
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
Regression Testing.
Chapter 1: Boundary Value Testing
AICT5 – eProject Project Planning for ICT
Presentation transcript:

Importance of testing Difference between Errors and Faults The purpose of test data Importance of: – Testing – Test Plans

Whenever a system has been implemented it needs to be thoroughly tested to ensure it works. The amount of testing that takes place depends on the system: – A system which monitors nuclear reactions in a power station needs to be more thoroughly tested compared to a simple stock take system, for example. In any case, all new systems should be tested using a particular procedure.

A testing procedure is created which forms a test plan. Through testing you can establish: – That the new system meets the end-user’s requirements. – That the new system processes data and outputs correct results. Testing can also help boost the confidence of the end- user’s. If they know the system has worked under testing they will be more confident in using it!

It is important to understand the difference between an error and a fault.

If your system can minimise human error and doesn’t contain bugs then you could consider it to be a reliable system. Testing ensures that a system is reliable. If testing doesn’t take place then you can’t claim a system is reliable.

When a new system is released it often contains bugs that weren’t discovered in testing. The software developers often release a series of patches or updates to address these problems.

The data that is selected for testing is really important. There are three types of test data which should be used for each particular thing you are testing: – Normal data – Extreme data – Erroneous (or abnormal) data

This is data which is: – Correct – Which should not generate any errors – Data which is likely to be used everyday

This is data which is: – Correct – Tests the boundaries of a range For example, data inputted into a field might need to be within a range of Two tests should be carried out – Test the input of 1 and test the input of 100.

This is data which is: – Incorrect – Outside of boundary tolerances – Making use of incorrect data types – Making use of invalid characters ([? # + \] etc)

Test plans need to be created before any testing takes place. These should be well thought out so that all aspects of the system are tested. Test plans should ensure that tests cover: – The requirements – Pathways – Validation Routines – A comparison of the actual performance against the design specification

Test #Description of testType of testData usedExpected Result

The test plan needs to be detailed enough to allow someone else to look at it and understand what tests took place. Any test which returns an unexpected result will need to be analysed and retested after modifications have taken place.

Describe the importance of a test plan. Explain when a test plan needs to be changed? Explain the purpose of test data. Explain the difference between normal, extreme and erroneous test data.