Suche senden
Hochladen
Ch23
•
Als PPT, PDF herunterladen
•
2 gefällt mir
•
662 views
P
phanleson
Folgen
Technologie
Business
Melden
Teilen
Melden
Teilen
1 von 55
Jetzt herunterladen
Empfohlen
Software testing
Software testing
Mahfuz1061
Integration test
Integration test
sadegh salehi
Software testing
Software testing
Eng Ibrahem
Learn software testing with tech partnerz 2
Learn software testing with tech partnerz 2
Techpartnerz
Unit 6 final
Unit 6 final
sietkcse
Testing Concepts and Manual Testing
Testing Concepts and Manual Testing
Sachin-QA
Testing Concepts and Manual Testing
Testing Concepts and Manual Testing
Fayis-QA
Testing Concepts and Manual Testing
Testing Concepts and Manual Testing
ANKUR-BA
Empfohlen
Software testing
Software testing
Mahfuz1061
Integration test
Integration test
sadegh salehi
Software testing
Software testing
Eng Ibrahem
Learn software testing with tech partnerz 2
Learn software testing with tech partnerz 2
Techpartnerz
Unit 6 final
Unit 6 final
sietkcse
Testing Concepts and Manual Testing
Testing Concepts and Manual Testing
Sachin-QA
Testing Concepts and Manual Testing
Testing Concepts and Manual Testing
Fayis-QA
Testing Concepts and Manual Testing
Testing Concepts and Manual Testing
ANKUR-BA
Software testing
Software testing
Ahmed Moawad
Testing terms & definitions
Testing terms & definitions
Sachin MK
Software testing definition
Software testing definition
Hiro Mia
T0 numtq0nje=
T0 numtq0nje=
International Journal of Science and Research (IJSR)
Some important definitions in softaware testing
Some important definitions in softaware testing
Shwetketu Rastogi
Software Teting
Software Teting
Ruchika Sinha
software engineering
software engineering
Subhanshu Mittal
System Integration Testing
System Integration Testing
Josh Case
Requirements Based Testing
Requirements Based Testing
SSA KPI
Integration testing
Integration testing
Techversant
Structured system analysis and design
Structured system analysis and design
Jayant Dalvi
Unit Testing vs Integration Testing
Unit Testing vs Integration Testing
Rock Interview
6. Testing Guidelines
6. Testing Guidelines
Mohammad Nasir Uddin
System testing ppt
System testing ppt
L ESHWAR
System testing
System testing
Abdullah-Al- Mahmud
Software testing
Software testing
Nitish Upreti
Software testing
Software testing
Bhagyashree pathak
Software-Testing.pdf
Software-Testing.pdf
Salim533277
Software engineering testing and types
Software engineering testing and types
Dr. Anthony Vincent. B
Ian Sommerville, Software Engineering, 9th EditionCh 8
Ian Sommerville, Software Engineering, 9th EditionCh 8
Mohammed Romi
Ch. 20 software testing
Ch. 20 software testing
Sougata Dafader
Software Verification & Validation
Software Verification & Validation
university of education,Lahore
Weitere ähnliche Inhalte
Was ist angesagt?
Software testing
Software testing
Ahmed Moawad
Testing terms & definitions
Testing terms & definitions
Sachin MK
Software testing definition
Software testing definition
Hiro Mia
T0 numtq0nje=
T0 numtq0nje=
International Journal of Science and Research (IJSR)
Some important definitions in softaware testing
Some important definitions in softaware testing
Shwetketu Rastogi
Software Teting
Software Teting
Ruchika Sinha
software engineering
software engineering
Subhanshu Mittal
System Integration Testing
System Integration Testing
Josh Case
Requirements Based Testing
Requirements Based Testing
SSA KPI
Integration testing
Integration testing
Techversant
Structured system analysis and design
Structured system analysis and design
Jayant Dalvi
Unit Testing vs Integration Testing
Unit Testing vs Integration Testing
Rock Interview
6. Testing Guidelines
6. Testing Guidelines
Mohammad Nasir Uddin
System testing ppt
System testing ppt
L ESHWAR
System testing
System testing
Abdullah-Al- Mahmud
Software testing
Software testing
Nitish Upreti
Software testing
Software testing
Bhagyashree pathak
Was ist angesagt?
(17)
Software testing
Software testing
Testing terms & definitions
Testing terms & definitions
Software testing definition
Software testing definition
T0 numtq0nje=
T0 numtq0nje=
Some important definitions in softaware testing
Some important definitions in softaware testing
Software Teting
Software Teting
software engineering
software engineering
System Integration Testing
System Integration Testing
Requirements Based Testing
Requirements Based Testing
Integration testing
Integration testing
Structured system analysis and design
Structured system analysis and design
Unit Testing vs Integration Testing
Unit Testing vs Integration Testing
6. Testing Guidelines
6. Testing Guidelines
System testing ppt
System testing ppt
System testing
System testing
Software testing
Software testing
Software testing
Software testing
Ähnlich wie Ch23
Software-Testing.pdf
Software-Testing.pdf
Salim533277
Software engineering testing and types
Software engineering testing and types
Dr. Anthony Vincent. B
Ian Sommerville, Software Engineering, 9th EditionCh 8
Ian Sommerville, Software Engineering, 9th EditionCh 8
Mohammed Romi
Ch. 20 software testing
Ch. 20 software testing
Sougata Dafader
Software Verification & Validation
Software Verification & Validation
university of education,Lahore
Dr.Jonathan Software verification validation.ppt
Dr.Jonathan Software verification validation.ppt
Phial
Verifcation and Validation
Verifcation and Validation
SaggitariusArrow
Software Verification & Validation
Software Verification & Validation
university of education,Lahore
Different Types Of Testing
Different Types Of Testing
Siddharth Belbase
SE2018_Lec 19_ Software Testing
SE2018_Lec 19_ Software Testing
Amr E. Mohamed
Ch8
Ch8
Mohammed Romi
Ch8
Ch8
Keith Jasper Mier
System imolementation(Modern Systems Analysis and Design)
System imolementation(Modern Systems Analysis and Design)
United International University
Object oriented sad 6
Object oriented sad 6
Bisrat Girma
Software Testing
Software Testing
SKumar11384
Ch8-Software Engineering 9
Ch8-Software Engineering 9
Ian Sommerville
Software Processes
Software Processes
university of education,Lahore
UVM_Full_Print_n.pptx
UVM_Full_Print_n.pptx
nikitha992646
Ch8.Testing.pptx
Ch8.Testing.pptx
AsimAli449052
Ch8 - Testing
Ch8 - Testing
Harsh Verdhan Raj
Ähnlich wie Ch23
(20)
Software-Testing.pdf
Software-Testing.pdf
Software engineering testing and types
Software engineering testing and types
Ian Sommerville, Software Engineering, 9th EditionCh 8
Ian Sommerville, Software Engineering, 9th EditionCh 8
Ch. 20 software testing
Ch. 20 software testing
Software Verification & Validation
Software Verification & Validation
Dr.Jonathan Software verification validation.ppt
Dr.Jonathan Software verification validation.ppt
Verifcation and Validation
Verifcation and Validation
Software Verification & Validation
Software Verification & Validation
Different Types Of Testing
Different Types Of Testing
SE2018_Lec 19_ Software Testing
SE2018_Lec 19_ Software Testing
Ch8
Ch8
Ch8
Ch8
System imolementation(Modern Systems Analysis and Design)
System imolementation(Modern Systems Analysis and Design)
Object oriented sad 6
Object oriented sad 6
Software Testing
Software Testing
Ch8-Software Engineering 9
Ch8-Software Engineering 9
Software Processes
Software Processes
UVM_Full_Print_n.pptx
UVM_Full_Print_n.pptx
Ch8.Testing.pptx
Ch8.Testing.pptx
Ch8 - Testing
Ch8 - Testing
Mehr von phanleson
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
phanleson
Firewall - Network Defense in Depth Firewalls
Firewall - Network Defense in Depth Firewalls
phanleson
Mobile Security - Wireless hacking
Mobile Security - Wireless hacking
phanleson
Authentication in wireless - Security in Wireless Protocols
Authentication in wireless - Security in Wireless Protocols
phanleson
E-Commerce Security - Application attacks - Server Attacks
E-Commerce Security - Application attacks - Server Attacks
phanleson
Hacking web applications
Hacking web applications
phanleson
HBase In Action - Chapter 04: HBase table design
HBase In Action - Chapter 04: HBase table design
phanleson
HBase In Action - Chapter 10 - Operations
HBase In Action - Chapter 10 - Operations
phanleson
Hbase in action - Chapter 09: Deploying HBase
Hbase in action - Chapter 09: Deploying HBase
phanleson
Learning spark ch11 - Machine Learning with MLlib
Learning spark ch11 - Machine Learning with MLlib
phanleson
Learning spark ch10 - Spark Streaming
Learning spark ch10 - Spark Streaming
phanleson
Learning spark ch09 - Spark SQL
Learning spark ch09 - Spark SQL
phanleson
Learning spark ch07 - Running on a Cluster
Learning spark ch07 - Running on a Cluster
phanleson
Learning spark ch06 - Advanced Spark Programming
Learning spark ch06 - Advanced Spark Programming
phanleson
Learning spark ch05 - Loading and Saving Your Data
Learning spark ch05 - Loading and Saving Your Data
phanleson
Learning spark ch04 - Working with Key/Value Pairs
Learning spark ch04 - Working with Key/Value Pairs
phanleson
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
phanleson
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
phanleson
Lecture 1 - Getting to know XML
Lecture 1 - Getting to know XML
phanleson
Lecture 4 - Adding XTHML for the Web
Lecture 4 - Adding XTHML for the Web
phanleson
Mehr von phanleson
(20)
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
Firewall - Network Defense in Depth Firewalls
Firewall - Network Defense in Depth Firewalls
Mobile Security - Wireless hacking
Mobile Security - Wireless hacking
Authentication in wireless - Security in Wireless Protocols
Authentication in wireless - Security in Wireless Protocols
E-Commerce Security - Application attacks - Server Attacks
E-Commerce Security - Application attacks - Server Attacks
Hacking web applications
Hacking web applications
HBase In Action - Chapter 04: HBase table design
HBase In Action - Chapter 04: HBase table design
HBase In Action - Chapter 10 - Operations
HBase In Action - Chapter 10 - Operations
Hbase in action - Chapter 09: Deploying HBase
Hbase in action - Chapter 09: Deploying HBase
Learning spark ch11 - Machine Learning with MLlib
Learning spark ch11 - Machine Learning with MLlib
Learning spark ch10 - Spark Streaming
Learning spark ch10 - Spark Streaming
Learning spark ch09 - Spark SQL
Learning spark ch09 - Spark SQL
Learning spark ch07 - Running on a Cluster
Learning spark ch07 - Running on a Cluster
Learning spark ch06 - Advanced Spark Programming
Learning spark ch06 - Advanced Spark Programming
Learning spark ch05 - Loading and Saving Your Data
Learning spark ch05 - Loading and Saving Your Data
Learning spark ch04 - Working with Key/Value Pairs
Learning spark ch04 - Working with Key/Value Pairs
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
Lecture 1 - Getting to know XML
Lecture 1 - Getting to know XML
Lecture 4 - Adding XTHML for the Web
Lecture 4 - Adding XTHML for the Web
Kürzlich hochgeladen
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.
Curtis Poe
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
LoriGlavin3
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdf
Alex Barbosa Coqueiro
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brand
gvaughan
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdf
LoriGlavin3
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
LoriGlavin3
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
Lorenzo Miniero
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc
"Debugging python applications inside k8s environment", Andrii Soldatenko
"Debugging python applications inside k8s environment", Andrii Soldatenko
Fwdays
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
BookNet Canada
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
LoriGlavin3
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
LoriGlavin3
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
mohitsingh558521
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024
Lonnie McRorey
DSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine Tuning
Lars Bell
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan
Fwdays
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
LoriGlavin3
Training state-of-the-art general text embedding
Training state-of-the-art general text embedding
Zilliz
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
Commit University
unit 4 immunoblotting technique complete.pptx
unit 4 immunoblotting technique complete.pptx
BkGupta21
Kürzlich hochgeladen
(20)
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdf
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brand
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
TrustArc Webinar - How to Build Consumer Trust Through Data Privacy
"Debugging python applications inside k8s environment", Andrii Soldatenko
"Debugging python applications inside k8s environment", Andrii Soldatenko
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024
DSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine Tuning
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
Training state-of-the-art general text embedding
Training state-of-the-art general text embedding
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
unit 4 immunoblotting technique complete.pptx
unit 4 immunoblotting technique complete.pptx
Ch23
1.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing
2.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 2 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
3.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 3 Topics covered System testing Component testing Test case design Test automation
4.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 4 The testing process Component testing • Testing of individual program components; • Usually the responsibility of the component developer (except sometimes for 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.
5.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 5 Testing phases ComtestiSystesSoftwInd
6.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 6 Defect testing The goal of defect testing is to discover defects in programs A successful defect test is a test which causes a program to behave in an anomalous way Tests show the presence not the absence of defects
7.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 7 Testing process goals Validation testing • To demonstrate to the developer and the system customer that the software meets its requirements; • A successful test shows that the system operates as intended. Defect testing • To discover faults or defects in the software where its behaviour is incorrect or not in conformance with its specification; • A successful test is a test that makes the system perform incorrectly and so exposes a defect in the system.
8.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 8 The software testing process Design tecasesPrepare testdataRun programwithtaCoe restoTestcasesTestdataTestresuTesrepts
9.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 9 Only exhaustive testing can show a program is free from defects. However, exhaustive testing is impossible, Testing policies define the approach to be used in selecting system tests: • All functions accessed through menus should be tested; • Combinations of functions accessed through the same menu should be tested; • Where user input is required, all functions must be tested with correct and incorrect input. Testing policies
10.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 10 System testing Involves integrating components to create a system or sub-system. May involve testing an increment to be delivered to the customer. Two phases: • Integration testing - the test team have access to the system source code. The system is tested as components are integrated. • Release testing - the test team test the complete system to be delivered as a black-box.
11.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 11 Integration testing Involves building a system from its components and testing it for problems that arise from component interactions. Top-down integration • Develop the skeleton of the system and populate it with components. Bottom-up integration • Integrate infrastructure components then add functional components. To simplify error localisation, systems should be incrementally integrated.
12.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 12 Incremental integration testing TTT TT ABCD T2T1 T3T4 ABC T1T2T3AB Test seqTest sTest
13.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 13 Testing approaches Architectural validation • Top-down integration testing is better at discovering errors in the system architecture. System demonstration • Top-down integration testing allows a limited demonstration at an early stage in the development. Test implementation • Often easier with bottom-up integration testing. Test observation • Problems with both approaches. Extra code may be required to observe tests.
14.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 14 Release testing The process of testing a release of a system that will be distributed to customers. Primary goal is to increase the supplier’s confidence that the system meets its requirements. Release testing is usually black-box or functional testing • Based on the system specification only; • Testers do not have knowledge of the system implementation.
15.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 15 Black-box testing IeInput tta OeOutputesults System Inpanobehvio Outhiceveatheesedef
16.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 16 Testing guidelines Testing guidelines are hints for the testing team to help them choose tests that will reveal defects in the system • Choose inputs that force the system to generate all error messages; • Design inputs that cause buffers to overflow; • Repeat the same input or input series several times; • Force invalid outputs to be generated; • Force computation results to be too large or too small.
17.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 17 Testing scenario A student in Scotland is studying American History and has been asked to write a paper on ‘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 the search facility to discover if she can access original documents from that time. She discovers sources in various US university libraries and downloads copies of some of these. However, for one document, she needs to have confirmation from her university that she is a genuine student and that use is for non-commercial purposes. The student then uses the facility in LIBSYS that can request such permission and registers her request. 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 receive an e-mail message when the printed document is available for collection.
18.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 18 System tests
19.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 19 Use cases Use cases can be a basis for deriving the tests for a system. They help identify operations to be tested and help design the required test cases. From an associated sequence diagram, the inputs and outputs to be created for the tests can be identified.
20.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 20 Collect weather data sequence chart :Commrequestt)acknowreport ()sum reply (rt)acknowsend (t) :Weathe:Weat
21.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 21 Performance testing Part of release testing may involve testing the emergent properties of a system, such as performance and reliability. Performance tests usually involve planning a series of tests where the load is steadily increased until the system performance becomes unacceptable.
22.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 22 Stress testing Exercises the system beyond its maximum design load. Stressing the system often causes defects to come to light. Stressing the system test failure behaviour.. Systems should not fail catastrophically. Stress testing checks for unacceptable loss of service or data. Stress testing is particularly relevant to distributed systems that can exhibit severe degradation as a network becomes overloaded.
23.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 23 Component testing Component or unit testing is the process of testing individual components in isolation. It is a defect testing process. Components may be: • Individual functions or methods within an object; • Object classes with several attributes and methods; • Composite components with defined interfaces used to access their functionality.
24.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 24 Object class testing Complete test coverage of a class involves • Testing all operations associated with an object; • Setting and interrogating all object attributes; • Exercising the object in all possible states. Inheritance makes it more difficult to design object class tests as the information to be tested is not localised.
25.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 25 Weather station object interface idenrepotWeatcaliteststartupshu Weath
26.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 26 Weather station testing Need to define test cases for reportWeather, calibrate, test, startup and shutdown. Using a state model, identify sequences of state transitions to be tested and the event sequences to cause these transitions For example: • Waiting -> Calibrating -> Testing -> Transmitting -> Waiting
27.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 27 Objectives are to detect faults due to interface errors or invalid assumptions about interfaces. Particularly important for object-oriented development as objects are defined by their interfaces. Interface testing
28.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 28 Interface testing BC Testcase A
29.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 29 Interface types Parameter interfaces • Data passed from one procedure to another. Shared memory interfaces • Block of memory is shared between procedures or functions. Procedural interfaces • Sub-system encapsulates a set of procedures to be called by other sub-systems. Message passing interfaces • Sub-systems request services from other sub-system.s
30.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 30 Interface errors Interface misuse • A calling component calls another component and makes an error in its use of its interface e.g. parameters in the wrong order. Interface misunderstanding • A calling component embeds assumptions about the behaviour of the called component which are incorrect. Timing errors • The called and the calling component operate at different speeds and out-of-date information is accessed.
31.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 31 Interface testing guidelines Design tests so that parameters to a called procedure are at the extreme ends of their ranges. Always test pointer parameters with null pointers. Design tests which cause the component to fail. Use stress testing in message passing systems. In shared memory systems, vary the order in which components are activated.
32.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 32 Test case design Involves designing the test cases (inputs and outputs) used to test the system. The goal of test case design is to create a set of tests that are effective in validation and defect testing. Design approaches: • Requirements-based testing; • Partition testing; • Structural testing.
33.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 33 Requirements based testing A general principle of requirements engineering is that requirements should be testable. Requirements-based testing is a validation testing technique where you consider each requirement and derive a set of tests for that requirement.
34.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 34 LIBSYS requirements
35.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 35 LIBSYS tests • Initiate user search for searches for items that are known to be present and known not to be present, where the set of databases includes 1 database. • Initiate user searches for items that are known to be present and known not to be present, where the set of databases includes 2 databases • Initiate user searches for items that are known to be present and known not to be present where the set of databases includes more than 2 databases. • Select one database from the set of databases and initiate user searches for items that are known to be present and known not to be present. • Select more than one database from the set of databases and initiate searches for items that are known to be present and known not to be present.
36.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 36 Partition testing Input data and output results often fall into different classes where all members of a class are related. Each of these classes is an equivalence partition or domain where the program behaves in an equivalent way for each class member. Test cases should be chosen from each partition.
37.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 37 Equivalence partitioning System Outpu Invalid inValid i
38.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 38 Equivalence partitions Between 10000Less th0000Moe t999910000500001000999 Input values Between 40Less tMoe th03471110 Numbinputalues
39.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 39 Search routine specification procedure Search (Key : ELEM ; T: SEQ of ELEM; Found : in out BOOLEAN; L: in out ELEM_INDEX) ; Pre-condition -- the sequence has at least one element T’FIRST <= T’LAST Post-condition -- the element is found and is referenced by L ( Found and T (L) = Key) or -- the element is not in the array ( not Found and not (exists i, T’FIRST >= i <= T’LAST, T (i) = Key ))
40.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 40 Inputs which conform to the pre-conditions. Inputs where a pre-condition does not hold. Inputs where the key element is a member of the array. Inputs where the key element is not a member of the array. Search routine - input partitions
41.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 41 Testing guidelines (sequences) Test software with sequences which have only a single value. Use sequences of different sizes in different tests. Derive tests so that the first, middle and last elements of the sequence are accessed. Test with sequences of zero length.
42.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 42 Search routine - input partitions
43.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 43 Sometime called white-box testing. Derivation of test cases according to program structure. Knowledge of the program is used to identify additional test cases. Objective is to exercise all program statements (not all path combinations). Structural testing
44.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 44 Structural testing ComcodeTesou Test dtaDerivesTests
45.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 45 Pre-conditions satisfied, key element in array. Pre-conditions satisfied, key element not in array. Pre-conditions unsatisfied, key element in array. Pre-conditions unsatisfied, key element not in array. Input array has a single value. Input array has an even number of values. Input array has an odd number of values. Binary search - equiv. partitions
46.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 46 Binary search equiv. partitions MidElemEleEquivalen
47.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 47 Binary search - test cases
48.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 48 Path testing The objective of path testing is to ensure that the set of test cases is such that each path through the program is executed at least once. The starting point for path testing is a program flow graph that shows nodes representing program decisions and arcs representing the flow of control. Statements with conditions are therefore nodes in the flow graph.
49.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 49 Binary search flow graph elemArrelemArelem 1234567891410 111213 bottom > twhile bobottom > t elemArra[mid] = k
50.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 50 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 14 1, 2, 3, 4, 5, 14 1, 2, 3, 4, 5, 6, 7, 11, 12, 5, … 1, 2, 3, 4, 6, 7, 2, 11, 13, 5, … Test cases should be derived so that all of these paths are executed A dynamic program analyser may be used to check that paths have been executed Independent paths
51.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 51 Test automation Testing is an expensive process phase. Testing workbenches provide a range of tools to reduce the time required and total testing costs. Systems such as Junit support the automatic execution of tests. Most testing workbenches are open systems because testing needs are organisation-specific. They are sometimes difficult to integrate with closed design and analysis workbenches.
52.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 52 A testing workbench DynamianalyserProgrambeing tTest resultTestpredicFilecomExecutionreport Simulator SourcecodeTestmanagerTest dataOracleTest datageneratorSpetion ReportgeneatorTestesurepot
53.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 53 Testing workbench adaptation Scripts may be developed for user interface simulators and patterns for test data generators. Test outputs may have to be prepared manually for comparison. Special-purpose file comparators may be developed.
54.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 54 Key points Testing can show the presence of faults in a system; it cannot prove there are no remaining faults. Component developers are responsible for component testing; system testing is the responsibility of a separate team. Integration testing is testing increments of the system; release testing involves testing a system to be released to a customer. Use experience and guidelines to design test cases in defect testing.
55.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 23 Slide 55 Key points Interface testing is designed to discover defects in the interfaces of composite components. Equivalence partitioning is a way of discovering test cases - all cases in a partition should behave in the same way. Structural analysis relies on analysing a program and deriving tests from this analysis. Test automation reduces testing costs by supporting the test process with a range of software tools.
Jetzt herunterladen