Prepare for your exams
Get points
Guidelines and tips
Sell on Docsity
Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips

Sell on Docsity

Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents

20 Points

For each uploaded document

Answer questions

5 Points

For each given answer (max 1 per day)

All the ways to get free points

Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

System Testing-Software Engineering-Lecture Slides, Slides of Software Engineering

Software engineering is about the development and application of processes and tools for managing the complexities inherent in creating high quality software systems. It introduces the fundamental software engineering concepts and terminology. This lecture includes: System, Testing, Validation, Defect, Component, Generating, Characteristics, Automation, Case, Design, Program, Errors, Verification

Typology: Slides

2011/2012

Uploaded on 08/09/2012

parthivi 🇮🇳

4.1

(8)

85 documents

1 / 58

This page cannot be seen from the preview

Don't miss anything!

Objectives

To discuss the distinctions between validation testing

and defect testing

To describe the principles of system and component

testing

To describe strategies for generating system test

cases

To understand the essential characteristics of tool

used for test automation

docsity.com

Partial preview of the text

Download System Testing-Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity!

Objectives 

To discuss the distinctions between validation testingand defect testing

To describe the principles of system and componenttesting

To describe strategies for generating system testcases

To understand the essential characteristics of toolused for test automation

Topics covered 

System testing

Component testing

Test case design

Test automation

Program testing goals 

To demonstrate to the developer and the customer that thesoftware meets its requirements.^ 

For custom software, this means that there should be at least one test forevery requirement in the requirements document. For generic softwareproducts, it means that there should be tests for all of the systemfeatures, plus combinations of these features, that will be incorporated inthe product release. 

To discover situations in which the behavior of the software isincorrect, undesirable or does not conform to its specification.^ 

Defect testing is concerned with rooting out undesirable system behaviorsuch as system crashes, unwanted interactions with other systems,incorrect computations and data corruption. 5

Validation and defect testing 

The first goal leads to validation testing^ 

You expect the system to perform correctly using agiven set of test cases that reflect the system’s expecteduse.

The second goal leads to defect testing^ 

The test cases are designed to expose defects. The testcases in defect testing can be deliberately obscure andneed not reflect how the system is normally used.

6 Chapter 8 Software testing

The software testing process

Who Tests the Software?

developer

independent tester

Understands the systembut, will test "gently"and, is driven by "delivery" Must learn about the system,but, will attempt to break itand, is driven by quality

The testing process 

Component testing^ 

Testing of individual program components;  Usually the responsibility of the component developer (except sometimesfor critical systems);  Tests are derived from the developer’s experience. 

System testing^ 

Testing of groups of components integrated to create a system or sub-system;  The responsibility of an independent testing team;  Tests are based on a system specification.

Testing policies 

Only exhaustive testing can show a program is free fromdefects. However, exhaustive testing is impossible,

Testing policies define the approach to be used in selectingsystem tests:^ 

All functions accessed through menus should be tested;  Combinations of functions accessed through the same menu should betested;  Where user input is required, all functions must be tested with correctand incorrect input.

Integration testing 

Involves building a system from its components andtesting it for problems that arise from componentinteractions.

Top-down integration^ 

Develop the skeleton of the system and populate it withcomponents.

Bottom-up integration^ 

Integrate infrastructure components then add functionalcomponents.

To simplify error localisation, systems should beincrementally integrated.

Incremental integration testing

Release testing 

The process of testing a release of a system thatwill be distributed to customers.

Primary goal is to increase the supplier’s confidencethat the system meets its requirements.

Release testing is usually black-box or functionaltesting^ 

Based on the system specification only;



Testers do not have knowledge of the systemimplementation.

Black-box testing

Testing scenario

A student in Scotland is studying American History and has been asked to write a paperon Ô

Frontier mentality in the American West from 1840 to 1880Õ.To do this, she needs to

find sources from a range of libraries. She logs on to the LIBSYS system and uses thesearch facility to discover if she can acce ss original documents from that time. Shediscovers sources in various US university libraries and down loads copies of some ofthese. However, for one document, she needs to have confirmation from her universitythat she is a genuine student and that use is for non-commercial purposes. The s tudentthen uses the facility in LIBSYS that can request such permission and registers herrequest. If granted, the document will be downloaded to the registered libraryÕ

s server

and printed for her. She receives a message from LIBSYS telling her that she will receivean e-mail message when th e printed document is available for collection.

System tests

Test the login mechanism using correct and incorrect logins to checkthat valid users are accepted and invalid users are rejected.

Test the search facility using different queries against known sources tocheck that the search mechanism is actually finding documents.

Test the system presentation facility to check that information aboutdocuments is displayed properly.

Test the mechanism to request permission for downloading.

Test the e-mail response indicating that the downloaded document isavailable.