This document discusses various topics related to software testing and verification and validation (V&V). It begins with an overview of test plan creation and different types of testing such as unit, integration, system, and object-oriented testing. It then defines the key differences between verification and validation. The rest of the document provides more details on V&V techniques like static and dynamic verification, software inspections, and testing. It also covers testing fundamentals, principles, testability factors, and different testing techniques like black-box and white-box testing.
Software Product Measurement and Analysis in a Continuous Integration Environ...Gabriel Moreira
Presentation of a paper presented in the International Conference ITNG 2010, about a framework constructed for software internal quality measurement program with automatic metrics extraction, implemented at a Software Factory.
Software Testing and Quality Assurance Assignment 3Gurpreet singh
Short questions :
Que 1 : Define Software Testing.
Que 2 : What is risk identification ?
Que 3 : What is SCM ?
Que 4 : Define Debugging.
Que 5 : Explain Configuration audit.
Que 6 : Differentiate between white box testing & black box testing.
Que 7 : What do you mean by metrics ?
Que 8 : What do you mean by version control ?
Que 9 : Explain Object Oriented Software Engineering.
Que 10 : What are the advantages and disadvantages of manual testing tools ?
Long Questions:
Que 1 : What do you mean by baselines ? Explain their importance.
Que 2 : What do you mean by change control ? Explain the various steps in detail.
Que 3 : Explain various types of testing in detail.
Que 4 : Differentiate between automated testing and manual testing.
Que 5 : What is web engineering ? Explain in detail its model and features.
Software Product Measurement and Analysis in a Continuous Integration Environ...Gabriel Moreira
Presentation of a paper presented in the International Conference ITNG 2010, about a framework constructed for software internal quality measurement program with automatic metrics extraction, implemented at a Software Factory.
Software Testing and Quality Assurance Assignment 3Gurpreet singh
Short questions :
Que 1 : Define Software Testing.
Que 2 : What is risk identification ?
Que 3 : What is SCM ?
Que 4 : Define Debugging.
Que 5 : Explain Configuration audit.
Que 6 : Differentiate between white box testing & black box testing.
Que 7 : What do you mean by metrics ?
Que 8 : What do you mean by version control ?
Que 9 : Explain Object Oriented Software Engineering.
Que 10 : What are the advantages and disadvantages of manual testing tools ?
Long Questions:
Que 1 : What do you mean by baselines ? Explain their importance.
Que 2 : What do you mean by change control ? Explain the various steps in detail.
Que 3 : Explain various types of testing in detail.
Que 4 : Differentiate between automated testing and manual testing.
Que 5 : What is web engineering ? Explain in detail its model and features.
Software, Types of Software
Software Project, Application and Product
Software Business Process
SDLC
SDLC Models
Test Levels
Software Environment
Test Types
Test Design Techniques
Testing Process (STLC)
Informal Testing
Quality Standards
Software Business Domains
http://www.londrestaxi.es/ | T Cars Service is a Private Hire Chaffeuring Service, where we offer high quality of service from our 17 years worth of experience. Our office is open 24/7 and you can call us anytime to get instant quote for your desired journey.
Business Seminar: Social-Media-Integration auf UnternehmenswebsitesGoldbach Group AG
INHALTE:
Theoretisches und praktisches Wissen zu:
1 Wirkung und gegenseitige Abhängigkeiten, 2 kanalgerechte Ansprache und Inhaltsproduktion, 3 technische Integration, 4 visuelle Darstellung und Einschränkungen, 5 Messbarkeit der einzelnen Schritte und Kanäle
Topics:
Authentic Leadership
The leader's code
My own roadmap toward new Leadership
Marshall Goldsmith Library
Scott Williams
Charter for NEW Leadership
Unboss
Global trends
My mission
Leadership in turbulent times
Recommendations
Software, Types of Software
Software Project, Application and Product
Software Business Process
SDLC
SDLC Models
Test Levels
Software Environment
Test Types
Test Design Techniques
Testing Process (STLC)
Informal Testing
Quality Standards
Software Business Domains
http://www.londrestaxi.es/ | T Cars Service is a Private Hire Chaffeuring Service, where we offer high quality of service from our 17 years worth of experience. Our office is open 24/7 and you can call us anytime to get instant quote for your desired journey.
Business Seminar: Social-Media-Integration auf UnternehmenswebsitesGoldbach Group AG
INHALTE:
Theoretisches und praktisches Wissen zu:
1 Wirkung und gegenseitige Abhängigkeiten, 2 kanalgerechte Ansprache und Inhaltsproduktion, 3 technische Integration, 4 visuelle Darstellung und Einschränkungen, 5 Messbarkeit der einzelnen Schritte und Kanäle
Topics:
Authentic Leadership
The leader's code
My own roadmap toward new Leadership
Marshall Goldsmith Library
Scott Williams
Charter for NEW Leadership
Unboss
Global trends
My mission
Leadership in turbulent times
Recommendations
This is the most important topic of OOAD named as Object Oriented Testing. It is used to prepare a good software which has no bug in it and it performs very fast. <a href="https://harisjamil.pro">Haris Jamil</a>
Software Testing
Different Types of Software Testing
Verification
Validation
Unit Testing
Beta Testing
Alpha Testing
Black Box Testing
White Box testing
Error
Bug
Software Testing :
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 conditions by manual or automated means. It checks for the :-
Specification
Functionality
Performance
This ppt is done by my dear classmate Sap, almost each ppt I have uploaded is copied from net and other sources.I hope this will b a little useful for students..
Algorithmic Toolbox Certificate from Coursera for Aman AdhikariAman Adhikari
Certificate for online non-credit course authorized by University of California, San Diego and Higher School of Economics and offered through Coursera named, "Algorithmic Toolbox" for Aman Adhikari
Synthetic Fiber Construction in lab .pptxPavel ( NSTU)
Synthetic fiber production is a fascinating and complex field that blends chemistry, engineering, and environmental science. By understanding these aspects, students can gain a comprehensive view of synthetic fiber production, its impact on society and the environment, and the potential for future innovations. Synthetic fibers play a crucial role in modern society, impacting various aspects of daily life, industry, and the environment. ynthetic fibers are integral to modern life, offering a range of benefits from cost-effectiveness and versatility to innovative applications and performance characteristics. While they pose environmental challenges, ongoing research and development aim to create more sustainable and eco-friendly alternatives. Understanding the importance of synthetic fibers helps in appreciating their role in the economy, industry, and daily life, while also emphasizing the need for sustainable practices and innovation.
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
Embracing GenAI - A Strategic ImperativePeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
2024.06.01 Introducing a competency framework for languag learning materials ...Sandy Millin
http://sandymillin.wordpress.com/iateflwebinar2024
Published classroom materials form the basis of syllabuses, drive teacher professional development, and have a potentially huge influence on learners, teachers and education systems. All teachers also create their own materials, whether a few sentences on a blackboard, a highly-structured fully-realised online course, or anything in between. Despite this, the knowledge and skills needed to create effective language learning materials are rarely part of teacher training, and are mostly learnt by trial and error.
Knowledge and skills frameworks, generally called competency frameworks, for ELT teachers, trainers and managers have existed for a few years now. However, until I created one for my MA dissertation, there wasn’t one drawing together what we need to know and do to be able to effectively produce language learning materials.
This webinar will introduce you to my framework, highlighting the key competencies I identified from my research. It will also show how anybody involved in language teaching (any language, not just English!), teacher training, managing schools or developing language learning materials can benefit from using the framework.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
Francesca Gottschalk - How can education support child empowerment.pptxEduSkills OECD
Francesca Gottschalk from the OECD’s Centre for Educational Research and Innovation presents at the Ask an Expert Webinar: How can education support child empowerment?
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
The Roman Empire A Historical Colossus.pdfkaushalkr1407
The Roman Empire, a vast and enduring power, stands as one of history's most remarkable civilizations, leaving an indelible imprint on the world. It emerged from the Roman Republic, transitioning into an imperial powerhouse under the leadership of Augustus Caesar in 27 BCE. This transformation marked the beginning of an era defined by unprecedented territorial expansion, architectural marvels, and profound cultural influence.
The empire's roots lie in the city of Rome, founded, according to legend, by Romulus in 753 BCE. Over centuries, Rome evolved from a small settlement to a formidable republic, characterized by a complex political system with elected officials and checks on power. However, internal strife, class conflicts, and military ambitions paved the way for the end of the Republic. Julius Caesar’s dictatorship and subsequent assassination in 44 BCE created a power vacuum, leading to a civil war. Octavian, later Augustus, emerged victorious, heralding the Roman Empire’s birth.
Under Augustus, the empire experienced the Pax Romana, a 200-year period of relative peace and stability. Augustus reformed the military, established efficient administrative systems, and initiated grand construction projects. The empire's borders expanded, encompassing territories from Britain to Egypt and from Spain to the Euphrates. Roman legions, renowned for their discipline and engineering prowess, secured and maintained these vast territories, building roads, fortifications, and cities that facilitated control and integration.
The Roman Empire’s society was hierarchical, with a rigid class system. At the top were the patricians, wealthy elites who held significant political power. Below them were the plebeians, free citizens with limited political influence, and the vast numbers of slaves who formed the backbone of the economy. The family unit was central, governed by the paterfamilias, the male head who held absolute authority.
Culturally, the Romans were eclectic, absorbing and adapting elements from the civilizations they encountered, particularly the Greeks. Roman art, literature, and philosophy reflected this synthesis, creating a rich cultural tapestry. Latin, the Roman language, became the lingua franca of the Western world, influencing numerous modern languages.
Roman architecture and engineering achievements were monumental. They perfected the arch, vault, and dome, constructing enduring structures like the Colosseum, Pantheon, and aqueducts. These engineering marvels not only showcased Roman ingenuity but also served practical purposes, from public entertainment to water supply.
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...Levi Shapiro
Letter from the Congress of the United States regarding Anti-Semitism sent June 3rd to MIT President Sally Kornbluth, MIT Corp Chair, Mark Gorenberg
Dear Dr. Kornbluth and Mr. Gorenberg,
The US House of Representatives is deeply concerned by ongoing and pervasive acts of antisemitic
harassment and intimidation at the Massachusetts Institute of Technology (MIT). Failing to act decisively to ensure a safe learning environment for all students would be a grave dereliction of your responsibilities as President of MIT and Chair of the MIT Corporation.
This Congress will not stand idly by and allow an environment hostile to Jewish students to persist. The House believes that your institution is in violation of Title VI of the Civil Rights Act, and the inability or
unwillingness to rectify this violation through action requires accountability.
Postsecondary education is a unique opportunity for students to learn and have their ideas and beliefs challenged. However, universities receiving hundreds of millions of federal funds annually have denied
students that opportunity and have been hijacked to become venues for the promotion of terrorism, antisemitic harassment and intimidation, unlawful encampments, and in some cases, assaults and riots.
The House of Representatives will not countenance the use of federal funds to indoctrinate students into hateful, antisemitic, anti-American supporters of terrorism. Investigations into campus antisemitism by the Committee on Education and the Workforce and the Committee on Ways and Means have been expanded into a Congress-wide probe across all relevant jurisdictions to address this national crisis. The undersigned Committees will conduct oversight into the use of federal funds at MIT and its learning environment under authorities granted to each Committee.
• The Committee on Education and the Workforce has been investigating your institution since December 7, 2023. The Committee has broad jurisdiction over postsecondary education, including its compliance with Title VI of the Civil Rights Act, campus safety concerns over disruptions to the learning environment, and the awarding of federal student aid under the Higher Education Act.
• The Committee on Oversight and Accountability is investigating the sources of funding and other support flowing to groups espousing pro-Hamas propaganda and engaged in antisemitic harassment and intimidation of students. The Committee on Oversight and Accountability is the principal oversight committee of the US House of Representatives and has broad authority to investigate “any matter” at “any time” under House Rule X.
• The Committee on Ways and Means has been investigating several universities since November 15, 2023, when the Committee held a hearing entitled From Ivory Towers to Dark Corners: Investigating the Nexus Between Antisemitism, Tax-Exempt Universities, and Terror Financing. The Committee followed the hearing with letters to those institutions on January 10, 202
2. Topics include
Validation Planning
Testing Fundamentals
Test plan creation
Test-case generation
Black-box Testing
White Box Testing
Unit Testing
Integration Testing
System testing
Object-oriented Testing
3. Verification Vs.
Validation Two questions
Are we building the right product ? => Validation
Are we building the product right ? = > Verification
People
Money
Machines
Materials
Building the right product
Building product right
Efficiency
making best use of
resources in achieving
goals
Effectiveness
choosing effective goals and
achieving them
4. Verification &
Validation
Software V & V is a disciplined approach to assessing software
products throughout the SDLC.
V & V strives to ensure that quality is built into the software
and that the software satisfies business functional
requirements.
V & V is to ensures that software conforms to its specification
and meets the needs of the customers.
V & V employs review, analysis, and testing techniques to
determine whether a software product and its intermediate
deliverables comply with requirements. These requirements
include both business functional capabilities and quality
attributes.
V & V provide management with insights into the state of the
project and the software products, allowing for timely change
in the products or in the SDLC approach.
V & V is typically applied in parallel with software development
and support activities.
5. Verification involves checking that
The software conforms to its specification.
System meets its specified functional and non-functional
requirements.
“Are we building the product right ?”
Validation, a more general process ensure that the
software meets the expectation of the customer.
“Are we building the right product ?”
You can't test in quality. If its not there before you begin
testing, it won’t be there when you’re finished testing.
Verification &
Validation
6. Techniques of system
checking & Analysis
Software inspections
Concerned with analysis of the static system
representation to discover problems (static verification)
such as
• Requirements document
• Design diagrams and
• Program source code
It do not require the system to be executed.
This techniques include program inspections, automated
source code analysis and formal verification.
It can’t check the non-functional characteristics of the
software such as its performance and reliability.
7. Software testing
It involves executing an implementation of the software
with test data and examining the outputs of the software
and its operational behavior to check that it is performing
as required.
It is a dynamic techniques of verification and validation.
The system is executed with test data and its operational
behaviour is observed.
Two distinct types of testing
Defect testing : to find inconsistencies between a program
and its specification.
Statistical testing : to test program’s performance and
reliability and to check how it works under operational
conditions
Techniques of system
checking & Analysis
8. Static and Dynamic V &
V
Formal
specification
High-level
design
Requirements
specification
Detailed
design
Program
Prototype
Dynamic
validation
Static
verification
9. Software Testing
fundamentals
Testing is a set of activities that can be planned in
advance and conducted systematically.
Testing is the process of executing a program with the
intent of finding errors.
A good test case is one with a high probability of finding
an as-yet undiscovered error.
A successful test is one that discovers an as-yet-
undiscovered error.
10. Software testing
priciples
All tests should be traceable to customer
requirements.
Tests should be planned long before testing
begins.
The Pareto principle (80% of all errors will likely
be found in 20% of the code) applies to software
testing.
Testing should begin in the small and progress to
the large.
Exhaustive testing is not possible.
To be most effective, testing should be conducted
by an independent third party.
11. Operability-the better it works the more efficiently it can
be tested
Observability-what you see is what you test
Controllability-the better software can be controlled the
more testing can be automated and optimized
Decomposability-by controlling the scope of testing, the
more quickly problems can be isolated and retested
intelligently
Simplicity-the less there is to test, the more quickly we
can test
Stability-the fewer the changes, the fewer the
disruptions to testing
Understandability-the more information known, the
smarter the testing
Software Testability
Checklist
12. V&V Vs. Debugging
Verification and validation
A process that establishes the existence of defects in a
software system.
The ultimate goal of the V&V process is to establish
confidence that the software system is “fit for purpose”.
Debugging
A process that locates and corrects these defects
Locate
error
Design
error repair
Repair
error
Re-test
program
Test
results Specification Test
cases
13. Design test
cases
Prepare test
data
Runprogram
withtest data
Compare results
totest cases
Test
cases
Test
data
Test
results
Test
reports
The defect testing
process
Test data
Inputs which have been devised to test the system
Test cases
Inputs to test the system and the predicted outputs from
these inputs if the system operates according to its
specification
14. Project Planning
Plan Description
Quality Plan Describes the quality procedure and
standards that will be used in a project.
Validation Plan Describes the approach, resources and
schedule used for system validation.
Configuration
Management Plan
Describes the configuration management
procedures and structures to be used.
Maintenance Plan Predicts the maintenance requirements of
the system, maintenance costs and effort
required.
Staff development Plan Describes how the skills and experience of
the project team members will be developed.
17. Testing Process
Unit testing - Individual components are tested
independently, without other system components
Module testing - Related collections of dependent
components( class, ADT, procedures & functions) are tested,
without other system module.
Sub-system testing-Modules are integrated into sub-systems
and tested. The focus here should be on interface testing to
detect module interface errors or mismatches.
System testing - Testing of the system as a whole. Validating
functional and non-functional requirements & Testing of
emergent system properties.
Acceptance testing-Testing with customer data to check that
it is acceptable. Also called Alpha Testing
18. 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
Integration 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
The testing process
19. Acceptance Testing
Making sure the software works correctly for
intended user in his or her normal work
environment.
Alpha test-version of the complete software is
tested by customer under the supervision of the
developer at the developer’s site.
Beta test-version of the complete software is
tested by customer at his or her own site without
the developer being present
The testing process
20. Black-box testing
Also known as behavioral or functional testing.
The system is a “Blackbox” whose behavior can be
determined by studying its inputs and related outputs.
Knowing the specified function a product is to perform
and demonstrating correct operation based solely on its
specification without regard for its internal logic.
Focus on the functional requirements of the software i.e.,
information domain not the implementation part of the
software and disregards control structure.
The program test cases are based on the system
specification
It is performed during later stages of testing like in the
acceptance testing or beta testing.
21. I
e
Input test data
OeOutput test results
System
Inputs causing
anomalous
behaviour
Outputs which reveal
the presence of
defects
Black-box testing
22. Test are designed to answer the following questions:
How is functional validity tested?
How is system behavior and performance tested?
What classes of input behavior will make good test case?
Is the system particularly sensitive to certain input
values?
How are the boundaries of data class isolated?
What data rates and data volume can the system
tolerate?
What effect will specific combinations of data have on
system operations?
Black-box testing
23. Advantages of Black box
testing
Validates whether or not a given system conforms
to
its software specification
Introduce a series of inputs to a system and
compare
the outputs to a pre-defined test specification.
Test integration between individual system
components.
Tests are architecture independent — they do not
concern themselves with how a given output is
produced, only with whether that output is the
desired and expected output.
Require no knowledge of the underlying system,
one
need not be a software engineer to design black
box
tests.
24. Disadvantages of Black
box testing
Offer no guarantee that every line of code has been
tested.
Being architecture independent, it cannot determine
the efficiency of the code.
Will not find any errors, such as memory leaks, that
are not explicitly and instantly exposed by the
application.
26. Black-box technique that divides the input domain into
classes of data from which test cases can be derived
An ideal test case uncovers a class of errors( incorrect
processing of all incorrect data) that might require many
arbitrary test cases to be executed before a general error is
observed
Equivalence class guidelines:
If input condition specifies a range, one valid and two invalid
equivalence classes are defined
If an input condition requires a specific value, one valid and
two invalid equivalence classes are defined
If an input condition specifies a member of a set, one valid
and one invalid equivalence class is defined
If an input condition is Boolean, one valid and one invalid
equivalence class is defined
Equivalence
Partitioning
28. Between 10000 and 99999Less than 10000 More than 99999
9999
10000 50000
100000
99999
Input values
Between 4 and 10Less than 4 More than 10
3
4 7
11
10
Number of input values
Equivalence
Partitioning
29. Boundary Value Analysis (BVA)
Black-box technique that focuses on the boundaries of the
input domain rather than its center
BVA guidelines:
If input condition specifies a range bounded by values a and
b, test cases should include a and b, values just above and
just below a and b
If an input condition specifies and number of values, test
cases should be exercise the minimum and maximum
numbers, as well as values just above and just below the
minimum and maximum values
Apply guidelines 1 and 2 to output conditions, test cases
should be designed to produce the minimum and maxim
output reports
If internal program data structures have boundaries (e.g. size
limitations), be certain to test the boundaries
30. Comparison Testing
Also called back-to-back testing.
Black-box testing for safety critical systems ( such
as aircraft avionics, automobile braking system) in
which independently developed implementations of
redundant systems are tested for conformance to
specifications
Often equivalence class partitioning is used to
develop a common set of test cases for each
implementation.
31. Orthogonal Array
Testing
Black-box technique that enables the design of a
reasonably small set of test cases that provide
maximum test coverage
Focus is on categories of faulty logic likely to be
present in the software component (without
examining the code)
Priorities for assessing tests using an orthogonal
array
Detect and isolate all single mode faults
Detect all double mode faults
Mutimode faults
32. White-box or Glass Box
testing
Knowing the internal workings of a product,
tests are performed to check the workings of all
independent logic paths.
It derive test cases that:
Guarantee that all independent paths within a module
have been exercised at least once.
Exercise all logical decisions on their true and false
sides.
Execute all loops at their boundaries and within their
operational bounds, and
Exercise internal data structures to ensure their
validity.
Techniques being used: basic path and control
structure testing.
34. Tests complete systems or subsystems
composed of integrated components
Integration testing should be black-box testing
with tests derived from the specification
Main difficulty is localising errors
Incremental integration testing reduces this
problem.
Incremental integration strategies include
Top-down integration
Bottom-up integration
Regression testing
Smoke testing
Integration Testing
35. Top-down testing
Start with high-level system and integrate from the
top-down replacing individual components by stubs
where appropriate
Bottom-up testing
Integrate individual components in levels until the
complete system is created
In practice, most integration involves a combination
of these strategies
Approaches to
integration testing
37. Level NLevel NLevel NLevel NLevel N
Level N–1 Level N–1Level N–1
Testing
sequence
Test
drivers
Test
drivers
Bottom-up testing
38. System Testing
Recovery testing
Checks the system’s ability to recover from failures.
Security testing
Verifies that system protection mechanism prevent improper
penetration or data alteration
Stress testing
Program is checked to see how well it deals with abnormal
resource demands – quantity, frequency, or volume.
Performance testing
Designed to test the run-time performance of software,
especially real-time software.
39. Object-oriented Testing
The components to be tested are object classes
that are instantiated as objects
Larger gain than individual functions so
approaches to white-box testing have to be
extended
No obvious ‘top’ to the system for top-down
integration and testing
40. Acceptance Test
Format
Test Item List
Identification of Test-item
Testing Detail
Detailed testing procedure
Testing Result
Summary of testing-item
41. Test-item List
Item
No.
Test Item Sub –
item No.
Test-Sub Item Level
SR-02 Staff Review SR-02-01 Program Officer
Review
A
SR-02-02 Early Decline Report A
Test-Level
A- Basic Function, compulsory
B- Enhanced Function, compulsory
C- Enhanced Function, optional
42. Testing Details
Item No SR-02-01 Test Date
Item Staff Review Sub-item PO Review
Report: Early Decline
Precondition
Test Procedure
Test Standard
Test description
Test Result and
Conclusion
Passed
Failed
Sin of the Tester Sign of the
Manager
SR-02 Staff Review
43. References
From software engineering, A practitioner’s
approach by Roger S. Pressman
– Chapter 17: Software testing techniques
• Software Testing Fundamentals
• Test case design
• White-box testing- Basic path, Control Structure Testing
• Black-box testing
– Chapter 18: Software Testing Strategies
• A strategic approach to software testing
• Unit, Integration, Validation, System testing
From Software Engineering, Ian Sommerville
– Part5: Verification and Validation
• Chapter 19: Verification and validation
• Chapter 20: Software testing