Structural and functional testing

Dec 4, 2013Download as PPTX, PDF8 likes16,450 views

This document discusses structural and functional testing. Structural testing generates test cases based on the internal structure of a program, while functional testing generates test cases based on the program's functionality without considering internal structure. Some types of structural testing include statement coverage, branch coverage, path coverage, and conditional coverage. Types of functional testing include equivalence class partitioning and boundary value analysis. Testing has limitations in that it can find errors but not prove their absence, does not help find root causes, and only identifies known issues without uncovered defects.

STRUCTURAL
AND
FUNCTIONAL TESTING

Dr. Himanshu Hora
SRMS College of Engineering & Technology
Bareilly (INDIA)

CONTENTS







What is testing?
Goals of testing
Principles of Testing
Structural and Functional Testing
Types of Structural and Functional Testing
Limitations

TESTING
 According to the glossary of the IEEE
standardization , testing is defined as:
“The process of analyzing a software
item to detect the differences between existing
and required conditions (that is, bugs) and
to evaluate the features of
the software item”

GOALS OF TESTING
 Goal of testing:
finding faults in the software
producing a zero defect software
testing should be traceable
it should be deterministic

PRINCIPLES OF TESTING
 Test a program to try to make it fail
 Start testing early

Cont…
 Testing must be done by different persons at
different levels

Cont…
 Test a program innovatively
 Use both static and dynamic testing

STRUCTURAL TESTING
 Generates test cases based on the structure of
the program
 Also known as white box testing
 The internal structure of the program is taken
into account

FUNCTIONAL TESTING
 Generates test cases based on the functionality
of the software
 Also known as black box testing
 The internal structure of the program is hidden
from the testing process

Cont…
 Identify the functions which software is
expected to perform

 Treats the software as a "black box", examining
functionality without any knowledge of
internal implementation

TYPES OF STRUCTURAL
TESTING
 The different types of structural testing
are :
 Statement coverage: all statements in the
programs should be executed at least once
 Branch coverage: all branches in the
program should be executed at least once

Cont…

 Path coverage: all execution paths in the
program should be executed at lest once
 Conditional coverage: For conditional
branches, this means that, we execute the
TRUE branch at least once and the FALSE
branch at least once

TYPES OF FUNCTIONAL
TESTING
 The different types of functional testing are:


Equivalence class partitioning: In this
approach, the domain of input values to a
program is partitioned into a set of equivalent
classes



Boundary value analysis: It is the analysis of
the programming error that frequently occurs at
the boundaries of different equivalence classes of
inputs

LIMITATIONS
 Testing can be used to show the presence of
errors, but never to show their absence
 Software testing does not help in finding root
causes
 It can only identify the known issues or errors.
It gives no idea about defects still uncovered.

THANK YOU

Dr. Himanshu Hora
SRMS College of Engineering & Technology
Bareilly (INDIA)

This document discusses techniques for black box testing software. It defines black box testing as testing software functionality without knowledge of its internal implementation or code structure. The techniques described are equivalence partitioning, boundary value analysis, state transition testing, graph-based testing, error guessing, and comparison testing. Equivalence partitioning divides inputs into classes based on similar outcomes to reduce test cases. Boundary value analysis focuses on edge cases rather than the full input range. State transition testing checks behavior changes between states with the same inputs. Graph-based testing visualizes the relationships between inputs and outputs. Error guessing leverages the tester's experience to find common mistakes. Comparison testing looks for differences between versions of the same software.

Equivalence class testingMani Kanth

Equivalence class testing is a software testing technique that divides input values into valid and invalid categories called equivalence classes. Representative values are selected from each class as test data. This technique reduces the number of test cases needed while maintaining thorough coverage. An example divides numbers into classes of valid 2-3 digit numbers and invalid single digit numbers to test a program's valid and invalid number handling. There are different types of equivalence class testing that vary in robustness. The technique helps reduce testing time and cases but requires expertise to define classes and may not test all boundary conditions.

Introduction to software testingHadi Fadlallah

Software Testing 101QA Hannah

Chapter 13 software testing strategiesSHREEHARI WADAWADAGI

Black box software testingRana Muhammad Asif

Black box testing is a software testing technique where the internal structure and implementation of the system is not known. It focuses on validating the functionality of the system based on requirements and specifications. Some key techniques of black box testing include equivalence partitioning, boundary value analysis, and error guessing. Equivalence partitioning divides test cases into equivalence classes based on expected behavior. Boundary value analysis tests values at the boundaries of equivalence classes. Error guessing involves creating test cases based on intuition about potential errors. Black box testing is applied at various levels including unit, integration, system, and non-functional testing.

Software testing methods, levels and typesConfiz

This document provides an overview of software testing concepts and definitions. It discusses key topics such as software quality, testing methods like static and dynamic testing, testing levels from unit to acceptance testing, and testing types including functional, non-functional, regression and security testing. The document is intended as an introduction to software testing principles and terminology.

Software TestingMousmi Pawar

The document discusses various topics related to software testing including: 1. Software testing helps improve software quality by testing conformance to requirements and is important to uncover errors before delivery to customers. 2. Testing involves specialists at different stages from early development through delivery and includes unit testing of individual components, integration testing of combined components, and system testing of the full system. 3. Proper testing methods include black box testing of inputs/outputs, white box testing of code structures, and testing at different levels from units to full system as well as by independent third parties.

Software testingMadhumita Chatterjee

This document provides an introduction to software testing. It defines software testing as a process used to identify correctness, completeness, and quality of computer software. The key points covered include: why software testing is important; who should be involved in testing; when testing should start and stop in the software development lifecycle; the differences between verification and validation; types of errors; types of testing including manual and automation; methods like black box and white box testing; levels of testing from unit to acceptance; and definitions of test plans and test cases.

SOFTWARE TESTING UNIT-4 Mohammad Faizan

The document discusses various aspects of software testing including definitions, principles, objectives, types and processes. It defines testing as "the process of executing a program with the intent of finding errors". The key principles discussed are that testing shows presence of bugs but not their absence, exhaustive testing is impossible, early testing is beneficial, and testing must be done by an independent party. The major types of testing covered are unit testing, integration testing and system testing.

Software testing.pptKomal Garg

Software testing is the process of evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. Software testing is a process that should be done during the development process. In other words software testing is a verification and validation process. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs (errors or other defects). Software testing can be stated as the process of validating and verifying that a computer program/application/product: • meets the requirements that guided its design and development, • works as expected, • can be implemented with the same characteristics, • and satisfies the needs of stakeholders. Software Development Process Cycle:-  PLAN (P): Device a plan. Define your objective and determine the strategy and supporting methods required to achieve that objective.  DO (D): Execute the plan. Create the conditions and perform the necessary training to execute the plan.  CHECK (C): Check the results. Check to determine whether work is progressing according to the plan and whether the results are obtained.  ACTION (A): Take the necessary and appropriate action if checkup reveals that the work is not being performed according to plan or not as anticipated.

Software testing Kunal Prajapati

The document discusses software testing concepts like verification, validation, whitebox testing, and blackbox testing. Verification ensures the product satisfies specifications, while validation ensures it meets customer requirements. Whitebox testing uses internal knowledge to test code, while blackbox testing treats the system as a black box without internal knowledge. The document also covers different types of testing like unit, integration, and functional testing.

System testing pptL ESHWAR

System testing involves testing a fully integrated software application to verify it meets requirements. It is done after unit and integration testing. System testing checks interactions between components, verifies functional and non-functional requirements, and validates the architecture. Test cases cover use cases and validate all types of requirements. The system is tested as a whole in a controlled environment to check for defects before delivery.

Types of Software TestingNishant Worah

This document discusses various types of software testing techniques used in the software development lifecycle (SDLC). It begins by describing different SDLC models like waterfall, prototyping, RAD, spiral and V-models. It then discusses the importance of testing at different stages of SDLC and different types of testing like static vs dynamic, black box vs white box, unit vs integration etc. The rest of the document elaborates on specific black box and white box testing techniques like equivalence partitioning, boundary value analysis, cause-effect graphing, statement coverage and basis path testing.

Seminar on Software TestingBeat Fluri

(1) The document discusses software testing and provides an introduction to various testing techniques. (2) It discusses the challenges of software testing including the large input space, different execution paths, and coincidental correctness. Testing aims to find bugs early and is part of quality assurance. (3) The document then provides short glossaries defining key testing terms like test case, test suite, oracle, and fault model. It also discusses the V-Model and different testing levels from unit to system testing.

Software testingbalamurugan.k Kalibalamurugan

Parallel AlgorithmsDr Sandeep Kumar Poonia

The document discusses parallel algorithms and parallel computing. It begins by defining parallelism in computers as performing more than one task at the same time. Examples of parallelism include I/O chips and pipelining of instructions. Common terms for parallelism are defined, including concurrent processing, distributed processing, and parallel processing. Issues in parallel programming such as task decomposition and synchronization are outlined. Performance issues like scalability and load balancing are also discussed. Different types of parallel machines and their classification are described.

Agile software developmentMuhammad Amjad Rana

This document discusses agile software development methods. It outlines the agile manifesto which values individuals and interactions over processes, working software over documentation, and customer collaboration over contract negotiation. Some key agile principles include customer satisfaction, welcome changing requirements, and frequent delivery of working software. Common agile methods like extreme programming and scrum are also summarized. Advantages include improved customer satisfaction and responsiveness to change, while disadvantages include potential lack of documentation.

Black Box TestingTestbytes

Unit 3 Control Flow Testingravikhimani

Coupling and cohesionSutha31

White box testingNeethu Tressa

White box testing involves testing internal program structure and code. It includes static testing like code reviews and structural testing like unit testing. Static testing checks code against requirements without executing. Structural testing executes code to test paths and conditions. Code coverage metrics like statement coverage measure what code is executed by tests. Code complexity metrics like cyclomatic complexity quantify complexity to determine necessary test cases. White box testing finds defects from incorrect code but may miss realistic errors and developers can overlook own code issues.

Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...Ankit Prajapati

Author : Mr. Ankit Prajapati (Sr. Software Analyst) Below topics are covered in this presentation !!!  Software Testing  Skills required for Software Testing  Methods of Software Testing  Levels of Software Testing  Types of Software Testing  SDLC vs STLC  Test Management (Defect Life Cycle)  Deliverables of Software Testing  Automation Testing  Difference (Manual vs Automation)  Automation Testing Tools  References YouTube Link: https://www.youtube.com/watch?v=rTPh4kHgbdM

Testing concepts pptRathna Priya

Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.

Black box and white box testingAWADHESH PRATAP SINGH UNIVERSITY, REWA (M.P.)

unit testing and debuggingKarthigaGunasekaran1

Incremental model (software engineering)MuhammadTalha436

The incremental model is a process where software development is divided into standalone modules, with each module going through requirements, design, implementation, and testing phases. Each subsequent release of a module adds additional functionality until the complete system is achieved. The key phases are requirement analysis to identify needed functionality, design and development of system functions, testing each existing and new function, and implementation through coding and upgrading the working product. The incremental model is best for projects with lengthy timelines, less skilled teams, or customers wanting early access to prioritized features.

Variants of Turing MachineRajendran

This document discusses variants of Turing machines that increase their computational power and proves that any language accepted by a variant Turing machine is also accepted by a standard Turing machine. It covers variants such as multiple tapes, two-way infinite tapes, and nondeterminism. For each variant, it provides a proof that the standard Turing machine is equally powerful by simulating the variant with the standard model.

Reliability and its principalsHimanshu

The document discusses the principles of reliability in software engineering. It defines reliability as the probability of failure-free operation over a specified time period and environment. There are four key factors that influence reliability: numerical value, intended function, life, and environmental conditions. The most important aspects that impact reliability are design, production, and transportation. Reliability can be achieved through simple design, redundancy, overdesign, fail-safe devices, and proper maintenance. Related concepts discussed include availability, maintainability, and principles of software engineering and validation.

CBAMAsim Shahzad

This document provides an overview of the Cost Benefit Analysis Method (CBAM) for analyzing architectural decisions. CBAM considers both the technical impacts of decisions as well as the associated costs and financial benefits. It involves stakeholders prioritizing scenarios, assigning utility values to quality attributes, developing architectural strategies to address scenarios, and calculating the costs and benefits of strategies to determine the highest return on investment. The process is iterative, with the second iteration incorporating uncertainty through risk assessment. CBAM aims to help organizations optimally allocate resources by selecting strategies that maximize financial gains and minimize risks.

More Related Content

What's hot (20)

Software testingMadhumita Chatterjee

SOFTWARE TESTING UNIT-4 Mohammad Faizan

Software testing.pptKomal Garg

Software testing Kunal Prajapati

System testing pptL ESHWAR

Types of Software TestingNishant Worah

Seminar on Software TestingBeat Fluri

Software testingbalamurugan.k Kalibalamurugan

Parallel AlgorithmsDr Sandeep Kumar Poonia

Agile software developmentMuhammad Amjad Rana

Black Box TestingTestbytes

Unit 3 Control Flow Testingravikhimani

Coupling and cohesionSutha31

White box testingNeethu Tressa

Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...Ankit Prajapati

Testing concepts pptRathna Priya

Black box and white box testingAWADHESH PRATAP SINGH UNIVERSITY, REWA (M.P.)

unit testing and debuggingKarthigaGunasekaran1

Incremental model (software engineering)MuhammadTalha436

Variants of Turing MachineRajendran

Software testingMadhumita Chatterjee

SOFTWARE TESTING UNIT-4 Mohammad Faizan

Software testing.pptKomal Garg

Software testing Kunal Prajapati

System testing pptL ESHWAR

Types of Software TestingNishant Worah

Seminar on Software TestingBeat Fluri

Software testingbalamurugan.k Kalibalamurugan

Parallel AlgorithmsDr Sandeep Kumar Poonia

Agile software developmentMuhammad Amjad Rana

Black Box TestingTestbytes

Unit 3 Control Flow Testingravikhimani

Coupling and cohesionSutha31

White box testingNeethu Tressa

Software Testing - Part 1 (Techniques, Types, Levels, Methods, STLC, Bug Life...Ankit Prajapati

Testing concepts pptRathna Priya

Black box and white box testingAWADHESH PRATAP SINGH UNIVERSITY, REWA (M.P.)

unit testing and debuggingKarthigaGunasekaran1

Incremental model (software engineering)MuhammadTalha436

Variants of Turing MachineRajendran

Viewers also liked (12)

Reliability and its principalsHimanshu

CBAMAsim Shahzad

Architecture ReviewHimanshu

The document discusses architecture reviews, which assess an architecture's ability to fulfill quality requirements and identify risks. It describes the goals of ensuring documentation, coherence, standards compliance, and achieving project goals. Types of reviews include project process, purchase process, and iterative reviews. The basic review flow involves submitting documents, review, resolving issues, and approval or rejection. Roles in the process include the moderator, recorder, reviewers, and author/design team. Benefits are identifying risks, assessing quality attributes, promoting practices, and capturing design rationale.

Software reliability tools and common software errorsHimanshu

The document discusses various software reliability tools and common software errors. It describes tools like SMERFS, SRMP, SoftRel, and CASRE which are used for statistical modeling and estimation of software reliability. SMERFS is designed to estimate and predict reliability during testing using failure data. SRMP contains nine models and uses maximum likelihood estimation. SoftRel simulates project occurrences using a Piecewise-Poisson Markov Process. CASRE was developed by NASA to make reliability estimation easier. Common software errors discussed include errors in handling, preventing, detecting and recovering from errors, as well as boundary, calculation, initial state, race condition and load condition errors.

AbcHimanshu

The document discusses the Architecture Business Cycle (ABC), which describes the relationships between a system's architecture, its environment, and the factors that influence the architecture. The ABC shows how architectures are shaped by stakeholders, the developing organization, technical environments, and the architect's experience. It also illustrates how the architecture then influences those same factors through a feedback loop. The ideal architecture fulfills requirements, is well-documented, satisfies stakeholders, and balances quality attributes through analysis and incremental changes. The ABC provides a framework for understanding how architectures develop and are refined over the software lifecycle.

Business analysis in data warehousingHimanshu

SaamHimanshu

The document describes the Software Architecture Analysis Method (SAAM) which is a structured process for evaluating software architectures before an architecture is finalized. It involves developing scenarios to illustrate system usage and modification activities. Candidate architectures are described and scenarios are classified as directly or indirectly supported by each architecture. Indirect scenarios require evaluating potential changes needed. The interactions between scenarios that require changes to common components are also assessed. An overall evaluation compares architectures by weighting scenarios and tabulating costs estimates.

Importance of software architectureHimanshu

The document discusses software architecture and its importance. It makes three key points: 1) Software architecture includes diagrams that define the elements (boxes) and interactions (lines) of a system. This is a first cut at designing the system. 2) A software architecture represents the earliest design decisions, which are the hardest to change but most critical to get right. It communicates the design to stakeholders. 3) Functional requirements define what the system must do but not essential quality attributes like performance, reliability, and security. The architecture must be analyzed to determine if it will deliver these qualities.

Structural patternsHimanshu

This document discusses various structural design patterns including Adapter, Bridge, Composite, Decorator, Facade, Flyweight, and Proxy. It defines each pattern, provides examples of how and when to use each pattern, and in some cases includes UML diagrams. The document also discusses how the Decorator pattern can be used to solve the problem of creating specialized robot doctors in an automated hospital that each perform a core set of functions plus additional specialized functions.

Architecture business cycleHimanshu

The document discusses the Architecture Business Cycle (ABC), which describes the relationships between a system's architecture, its environment, and the factors that influence both. The ABC is a cycle of influences between the architecture and various technical, business, and social environments. It shows how architectures are shaped by stakeholders, the developing organization, the architect's experience, and the technical environment. In turn, architectures influence the organization's structure and goals, customer requirements, and the architect's experience on subsequent systems. The cycle represents how organizational goals and requirements inform the architecture, which then informs the developed systems and feeds back to influence the organization.

Software archiecture lecture07Luktalja

The document discusses the architecture of the Initial Sector Suite System (ISSS), which was intended to upgrade air traffic control systems in the United States. ISSS had ultrahigh availability requirements due to its safety-critical nature. Its architecture used hardware and software redundancy, distributed processing, and layering to achieve high availability and performance. It also employed interface wrapping and standard protocols to support openness, modifiability, and interoperability with other systems.

ATAMHimanshu

ATAM (Architecture Tradeoff Analysis Method) is a comprehensive method to evaluate a software architecture. It elicits business goals and how well an architecture satisfies quality goals such as through tradeoffs. The evaluation team includes roles like a team leader, evaluation leader, and stakeholders. Through phases like presenting the business drivers and architecture, brainstorming scenarios, and analyzing approaches, ATAM outputs include identifying sensitivity points, risks, and mapping decisions to requirements.

Reliability and its principalsHimanshu

CBAMAsim Shahzad

Architecture ReviewHimanshu

Software reliability tools and common software errorsHimanshu

AbcHimanshu

Business analysis in data warehousingHimanshu

SaamHimanshu

Importance of software architectureHimanshu

Structural patternsHimanshu

Architecture business cycleHimanshu

Software archiecture lecture07Luktalja

ATAMHimanshu

Similar to Structural and functional testing (20)

White box & black box testingSaket Khopkar

Software TestingVishal Singh

The document provides an introduction to software testing. It discusses that software testing verifies and validates that software meets requirements and works as expected. The main purposes of testing are verification, validation, and defect finding. Examples of why software testing is important are provided. The document outlines what is tested, who does the testing, and strategies for unit testing, integration testing, regression testing, validation testing, system testing, stress testing, and performance testing.

Software testingEng Ibrahem

Testing and types of TestingMunaam Munawar

This document discusses different types of testing in object-oriented analysis and design (OOAD). It describes system testing, which tests integrated software and systems. Unit testing tests individual software modules, while integration testing combines components to test interactions. User testing evaluates usability from an end user perspective, measuring factors like ease of use, learning time, and productivity increase. The document outlines categories and strategies for these various testing types used during software development and verification.

Software testing basicRohit Singh

This is the power point presentation on Software Testing. Software Testing is the process of finding error or bug in the developed software product based on the client requirement. This power point presentation give the basic knowledge about the software testing. Learn more at blog : -- https://solutionbyexpert.blogspot.com/2020/08/become-expert-secret-of-success-ii.html for mathematics classes visit the below link --- https://www.youtube.com/watch?v=g07wTZYYzKo&t=188s https://www.youtube.com/watch?v=KleKFXSXGPY&t=853s for physics classes visit the below link -- https://www.youtube.com/watch?v=6ha1sxMy4mU https://www.youtube.com/watch?v=2k5uI6Gm-8Y our facebook link -- https://www.facebook.com/Online-Smart-Classes-108395901487258 #coding #coding development skill program #java

Software Testing Concepts: A Compresive guide .pdfRuhiParveen6

white box and black box testing in software engineeringNabeelRehman21

Software Testing.pptxsonalshitole

The document discusses different types of software testing including manual testing techniques like white box, black box and grey box testing. It also discusses automated testing like unit testing, integration testing, system testing, functional testing, non-functional testing types like performance, load, stress, scalability, stability and usability testing. Compatibility testing is also discussed which checks if the software works across different platforms and environments.

Software TetingRuchika Sinha

Software testing is a process that evaluates the functionality and quality of software. It involves examining software through various testing types and processes to verify it meets requirements and is error-free. The main types of software testing include static vs dynamic, black box vs white box, automated vs manual, and regression testing. The goal of testing is to identify bugs and ensure the software works as intended.

Best software testing coursebestonlinecoursescoupon

Software testing is the primary process that to learn by all the beginners who are aspiring about testing. It is a process that we want to find the errors during the time of program or application executes. It is also said to be the validating and verifying the software implementation and program. The testing is mainly following during the time of validating product quality. The best software testing course is providing by the instructors under different categories for the learners to learn more about the details on testing. Here some of the sessions are to be following such as technology without coding, tester foundation level training for the beginners, etc.

Software testing strategiesSophia Girls' College(Autonomous), Ajmer

The document discusses strategies for software testing. It defines different levels of testing including unit testing, integration testing, system testing, and validation testing. It also discusses different testing approaches such as test-driven development, behavior-driven development, and agile testing. The document provides details on unit testing, integration testing, system testing, and validation testing. It discusses testing strategies, testing methods including black box testing and white box testing, and the differences between black box and white box testing.

Software testing pptHeritage Institute Of Tech,India

Testing is the process of identifying bugs and ensuring software meets requirements. It involves executing programs under different conditions to check specification, functionality, and performance. The objectives of testing are to uncover errors, demonstrate requirements are met, and validate quality with minimal cost. Testing follows a life cycle including planning, design, execution, and reporting. Different methodologies like black box and white box testing are used at various levels from unit to system. The overall goal is to perform effective testing to deliver high quality software.

black and white Box testing.pptxPavanNikhil3

The document discusses different types of software testing techniques, including black box testing and white box testing. It provides details on black box testing, which focuses on external inputs and outputs without knowledge of internal code. Key aspects of black box testing covered include independence from internal structure and focus on requirements. The document also discusses different types of functional testing like unit, integration, system, and acceptance testing. It then covers various non-functional testing techniques such as performance, security, usability, compatibility, and reliability testing. Specific black box testing techniques like equivalence partitioning and boundary value analysis are also summarized.

Software testingSengu Msc

Testing is the process of evaluating a system or its components to identify differences between expected and actual results. It involves executing a system to identify gaps, errors, or missing requirements. There are different types of testing such as unit testing, integration testing, system testing, and acceptance testing. Testing can be manual, automated, functional, or non-functional. Functional testing evaluates system functionality while non-functional testing evaluates attributes like performance and security. Common non-functional test types are load testing and stress testing which analyze a system's behavior under different load conditions.

Software testingSengu Msc

Testing is the process of evaluating a system or its components to identify errors or gaps between expected and actual results. It can be done manually or through automation. There are different types of testing like unit testing, integration testing, system testing, and acceptance testing. Testing also includes functional testing to check system requirements and non-functional testing to evaluate performance. Key aspects of testing include the software development life cycle (SDLC) and different models like waterfall, prototyping, incremental, spiral, and agile.

White-Box and Black-Box testing Introduction.pptxajaychelikhani

Software testing pptSavyasachi14

The document discusses different types of software testing. It states that software testing is a process that verifies that a system meets requirements and finds errors. There are two main types of testing: whitebox testing, where internal code structure is known, and blackbox testing, where it is unknown. Whitebox testing is used for verification while blackbox testing is used for validation from an end user perspective. The document also outlines various stages of testing like unit testing, integration testing, and functional testing.

How to Make the Most of Regression and Unit Testing_ A Comprehensive Guide.pdfflufftailshop

Testing is pivotal in the Software Development Life Cycle (SDLC). Ensuring the seamless functionality of every software component is imperative to meet both business and user expectations. Amid the diverse array of tests and testing methodologies, it's not uncommon for regression testing and unit testing to be conflated, leading to confusion. Distinguishing these two vital testing types is paramount for the success of the SDLC and, ultimately, for delivering high-quality software.

Software testing senguSengu Msc

Testing is the process of executing a program with the intention of finding errors. Software testing is an analysis that gives data to estimate quality and includes executing programs to find bugs. Testing is done by software testers, developers, project leads, and end users and includes both manual and automated methods. Functional testing examines a system's functionality against requirements while non-functional testing examines reliability, efficiency and other non-functional aspects.

unittesting-190620114546 (1).pptx documentAkshayaM79

White box & black box testingSaket Khopkar

Software TestingVishal Singh

Software testingEng Ibrahem

Testing and types of TestingMunaam Munawar

Software testing basicRohit Singh

Software Testing Concepts: A Compresive guide .pdfRuhiParveen6

white box and black box testing in software engineeringNabeelRehman21

Software Testing.pptxsonalshitole

Software TetingRuchika Sinha

Best software testing coursebestonlinecoursescoupon

Software testing strategiesSophia Girls' College(Autonomous), Ajmer

Software testing pptHeritage Institute Of Tech,India

black and white Box testing.pptxPavanNikhil3

Software testingSengu Msc

White-Box and Black-Box testing Introduction.pptxajaychelikhani

Software testing pptSavyasachi14

How to Make the Most of Regression and Unit Testing_ A Comprehensive Guide.pdfflufftailshop

Software testing senguSengu Msc

unittesting-190620114546 (1).pptx documentAkshayaM79

More from Himanshu (20)

Software product lineHimanshu

(1) A software product line is a set of software systems that share a common set of core assets but can be customized to meet specific needs. (2) Core assets include shared components, architecture, tools, and documentation that are developed and maintained to create products for a particular domain. (3) Establishing a software product line reduces costs through reuse of core assets, improves time to market for new products, and increases quality and predictability by leveraging proven architectures and components.

Shared information systemsHimanshu

This document discusses various architectural styles for information systems. It begins by defining data and information, then describes factors that affect the usefulness of information like quality, timeliness, completeness and relevance. It then presents a taxonomy of architectural styles including data flow, data-centered, virtual machine, independent component, and call-and-return styles. For each style it provides the goals, characteristics, advantages, and disadvantages. It also discusses heterogeneous styles and different types of management information systems.

SaamHimanshu

SAAM (Software Architecture Analysis Method) is a method used to evaluate a system architecture based on scenarios. It was the first documented software architecture analysis method. SAAM involves preparing descriptions of candidate architectures, evaluating the impact of various stakeholder scenarios on the architectures, and identifying issues with architectures under study. Key activities in SAAM include scenario development, architecture description, scenario classification, scenario evaluation, interaction assessment, and overall evaluation. The goal is to compare architectures and evaluate them against quality requirements.

Design PatternHimanshu

This document discusses the design of a document editor called Lexi. It addresses several design problems including document structure, formatting, user interface embellishment, supporting multiple look-and-feel standards and window systems, and user operations like undo/redo. It proposes solutions to these problems using several design patterns like composite, decorator, factory, bridge, command, and iterator patterns to achieve flexibility, extensibility and independence of algorithms and structures. The goal is to create a reusable and extensible design that can be understood and communicated effectively between team members.

Creational patternHimanshu

Creational patterns deal with object creation and aim to create objects in a suitable manner. There are three main creational patterns: the factory pattern, which provides a consistent interface for creating properly configured objects; the abstract factory pattern, which is a factory for factories and handles more complex situations; and the singleton pattern, which ensures a single instance of an object and consistency of data by restricting object instantiation.

White box black box & gray box testingHimanshu

This document discusses and compares white box, black box, and gray box testing methods. White box testing examines internal program structure and logic and requires knowledge of source code. Black box testing examines functionality without knowledge of internal workings. Gray box testing combines aspects of white and black box by having limited internal knowledge. Each method has advantages like code coverage for white box or large tester pools for black box, and disadvantages like cost or limited coverage. The document provides details on each method and how they differ in tester knowledge and perspective.

Pareto analysisHimanshu

Pareto analysis is a technique used to identify the key causes that contribute to a problem. It is based on the principle that 80% of problems are caused by 20% of the causes. The document outlines the history and procedure of Pareto analysis. The procedure involves gathering data on causes of a problem, ranking them by frequency, plotting them on graphs, and using the graphs to identify the vital few causes that contribute to 80% of the problem. An example is provided where Pareto analysis is used to identify the main causes of long waiting times at a clinic. The analysis finds that 7 main causes account for 80% of the waiting time problem.

Load runner & win runnerHimanshu

This document provides an introduction and overview of Load Runner and Win Runner software. Load Runner is an automated performance testing tool from HP that examines system behavior under load. Win Runner is an automated functional GUI testing tool that allows recording and playback of user interactions as test scripts. Both were originally developed by Mercury Interactive, which was acquired by HP. The document describes how each tool works, their typical processes, and provides some facts about Load Runner and Win Runner.

Crud and jadHimanshu

The document discusses CRUD (Create, Read, Update, Delete) operations and JAD (Joint Application Development). CRUD represents the basic SQL operations - Create, Read, Update, Delete. A CRUD analysis validates that a data model accounts for all required create, retrieve, update, delete functions. JAD is a process where developers, managers, users work together to build a product using structured interview sessions over 3-6 months. It aims to improve quality, communication and reduce costs and errors compared to traditional development.

Junit and cactusHimanshu

The document discusses the automated testing tools JUnit and Cactus. It outlines some pitfalls of using these tools, such as not using assertions correctly, writing unfocused test methods, and failing to isolate tests. However, it does not mention important drawbacks like the high cost and complexity of distributed testing with Cactus. Alternative tools like HttpUnit may provide simpler web testing without requiring test code on multiple JVMs. While automated testing can save time and money, tools like JUnit and Cactus have limitations and are not perfect for all types of testing.

Risk based testing and random testingHimanshu

The document discusses risk based testing and random testing approaches. It outlines the challenges of time and resource constraints when testing software. Risk based testing uses risk analysis and metrics to focus testing on high risk areas in order to save time and money while maintaining quality. Metrics are developed to manage and organize large test projects. Random testing involves automatically generating random inputs and scenarios to stress test software in ways not covered by nominal testing. It can be used with differential and fault injection testing against a reference implementation to automatically check test results.

Testing a data warehousesHimanshu

The document discusses testing of data warehouses. It notes that organizations need data warehouse testing more than ever to check data quality, completeness, and correct transformations. The document outlines different types of data warehouse testing and the testing process. It emphasizes planning testing phases and staffing as well as avoiding risks. Key focus points in testing include underlying data and data warehouse components. The document also compares database testing to data warehouse testing and notes challenges of testing including data selection from multiple sources and inconsistent data.

Software testing tools and its taxonomyHimanshu

This document discusses software testing tools and proposes a taxonomy for classifying them. It begins by addressing common myths and facts about software testing and developers. It then provides definitions of software testing and examples of over 20 specific software testing tools. The document proposes that a taxonomy is needed to classify tools to help testers choose the right ones. It reviews existing tool taxonomies and their shortcomings before concluding and thanking the reader.

Software reliability engineering processHimanshu

The document outlines the software reliability engineering (SRE) process. It defines software reliability as the ability of a system to perform without failure under specified conditions for a given time period. The SRE process involves 6 steps: 1) listing systems to test, 2) developing operational profiles, 3) defining acceptable reliability levels, 4) preparing tests, 5) executing tests, and 6) guiding the testing and release process. The goal is to measure, predict, and manage reliability through statistical modeling from the customer's perspective of minimizing failures.

Software reliability growth modelHimanshu

This document discusses software reliability growth models, which use system test data to predict the number of defects remaining in software and determine if the software is ready to ship. Most models have a parameter related to the total number of defects. Knowing the number of residual defects helps decide how much more testing is needed. Examples of models include the Goel-Okumoto model, which models the failure rate as approaching a total number of defects over time. The assumptions of the Goel-Okumoto model include that failure times are exponentially distributed and the number of failures follows a non-homogeneous Poisson process.

Regression and performance testingHimanshu

This document discusses software regression testing and performance testing. It defines regression testing as retesting software after changes to check for defects in modified areas and unaffected areas. Regression testing happens at the unit, integration, and system levels and requires analyzing software changes and impacts. Performance testing evaluates a system's compliance with performance requirements by testing response times under various loads. It helps ensure applications meet customers' expectations as defined in SLAs. The document discusses performance testing tools and benefits of the approach while cautioning that performance testing is as much an art as a science due to the many variables involved.

Eleven step of software testing processHimanshu

The 11-step software testing process follows a "V" model where the first five steps involve verifying interim deliverables and the last six steps involve validating the executable software. The 11 steps are: 1) assess development plan and status, 2) develop test plan, 3) test requirements, 4) test design, 5) test during programming, 6) execute and record results, 7) acceptance test, 8) report results, 9) test installation, 10) test software changes, and 11) evaluate test effectiveness. The process aims to validate and verify that the software meets requirements, works as expected, can be implemented consistently, and satisfies stakeholder needs.

Off the-shelf components (cots)Himanshu

This document discusses testing off-the-shelf (COTS) components. It defines COTS components as independently developed and reusable parts that are selected from a repository and assembled to build software systems. While COTS components reduce development costs and time, they present challenges to testing due to being treated as black boxes without access to requirements or development processes. The document outlines types of COTS component testing, including black-box testing of inputs/outputs, fault injection to evaluate error handling, operational testing in integrated systems, and interface propagation analysis to observe impacts of faults between components.

Building a software testing environmentHimanshu

This document discusses building a software testing environment. It emphasizes that senior management is responsible for creating an environment conducive to effective and efficient testing. This involves addressing topics like management's risk appetite, the role of testing, testing policies, support provided, and resources allocated. It also discusses developing a testing strategy that identifies test factors and phases to reduce risks. The strategy is represented as a test factor/test phase matrix that maps risks to development phases. Overall, the document provides guidance on how management can support testing and stresses the importance of a structured, risk-based approach.

Reconstructing Software ArchitectureHimanshu

Software architecture reconstruction is the process of analyzing an existing software system to produce an architectural representation of it. It involves extracting information from various sources like code, documentation, and profiles. This information is converted into a standard database format and combined from different sources through view fusion. The main activities of reconstruction are visualization and interaction with the views, and recognizing patterns in the code. It is an iterative process requiring both technical expertise and architectural skills to understand dependencies and evaluate how an implemented system conforms to its intended architecture.

Software product lineHimanshu

Shared information systemsHimanshu

SaamHimanshu

Design PatternHimanshu

Creational patternHimanshu

White box black box & gray box testingHimanshu

Pareto analysisHimanshu

Load runner & win runnerHimanshu

Crud and jadHimanshu

Junit and cactusHimanshu

Risk based testing and random testingHimanshu

Testing a data warehousesHimanshu

Software testing tools and its taxonomyHimanshu

Software reliability engineering processHimanshu

Software reliability growth modelHimanshu

Regression and performance testingHimanshu

Eleven step of software testing processHimanshu

Off the-shelf components (cots)Himanshu

Building a software testing environmentHimanshu

Reconstructing Software ArchitectureHimanshu

Recently uploaded (20)

How to track Cost and Revenue using Analytic Accounts in odoo Accounting, App...Celine George

Analytic accounts are used to track and manage financial transactions related to specific projects, departments, or business units. They provide detailed insights into costs and revenues at a granular level, independent of the main accounting system. This helps to better understand profitability, performance, and resource allocation, making it easier to make informed financial decisions and strategic planning.

LDMMIA Reiki Master Spring 2025 Mini UpdatesLDM Mia eStudios

Presentation on Tourism Product Development By Md Shaifullar RabbiMd Shaifullar Rabbi

SPRING FESTIVITIES - UK AND USA -Colégio Santa Teresinha

K12 Tableau Tuesday - Algebra Equity and Access in Atlanta Public Schoolsdogden2

Algebra 1 is often described as a “gateway” class, a pivotal moment that can shape the rest of a student’s K–12 education. Early access is key: successfully completing Algebra 1 in middle school allows students to complete advanced math and science coursework in high school, which research shows lead to higher wages and lower rates of unemployment in adulthood. Learn how The Atlanta Public Schools is using their data to create a more equitable enrollment in middle school Algebra classes.

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

SCI BIZ TECH QUIZ (OPEN) PRELIMS XTASY 2025.pptxRonisha Das

Quality Contril Analysis of Containers.pdfDr. Bindiya Chauhan

CBSE - Grade 8 - Science - Chemistry - Metals and Non Metals - WorksheetSritoma Majumder

Introduction All the materials around us are made up of elements. These elements can be broadly divided into two major groups: Metals Non-Metals Each group has its own unique physical and chemical properties. Let's understand them one by one. Physical Properties 1. Appearance Metals: Shiny (lustrous). Example: gold, silver, copper. Non-metals: Dull appearance (except iodine, which is shiny). 2. Hardness Metals: Generally hard. Example: iron. Non-metals: Usually soft (except diamond, a form of carbon, which is very hard). 3. State Metals: Mostly solids at room temperature (except mercury, which is a liquid). Non-metals: Can be solids, liquids, or gases. Example: oxygen (gas), bromine (liquid), sulphur (solid). 4. Malleability Metals: Can be hammered into thin sheets (malleable). Non-metals: Not malleable. They break when hammered (brittle). 5. Ductility Metals: Can be drawn into wires (ductile). Non-metals: Not ductile. 6. Conductivity Metals: Good conductors of heat and electricity. Non-metals: Poor conductors (except graphite, which is a good conductor). 7. Sonorous Nature Metals: Produce a ringing sound when struck. Non-metals: Do not produce sound. Chemical Properties 1. Reaction with Oxygen Metals react with oxygen to form metal oxides. These metal oxides are usually basic. Non-metals react with oxygen to form non-metallic oxides. These oxides are usually acidic. 2. Reaction with Water Metals: Some react vigorously (e.g., sodium). Some react slowly (e.g., iron). Some do not react at all (e.g., gold, silver). Non-metals: Generally do not react with water. 3. Reaction with Acids Metals react with acids to produce salt and hydrogen gas. Non-metals: Do not react with acids. 4. Reaction with Bases Some non-metals react with bases to form salts, but this is rare. Metals generally do not react with bases directly (except amphoteric metals like aluminum and zinc). Displacement Reaction More reactive metals can displace less reactive metals from their salt solutions. Uses of Metals Iron: Making machines, tools, and buildings. Aluminum: Used in aircraft, utensils. Copper: Electrical wires. Gold and Silver: Jewelry. Zinc: Coating iron to prevent rusting (galvanization). Uses of Non-Metals Oxygen: Breathing. Nitrogen: Fertilizers. Chlorine: Water purification. Carbon: Fuel (coal), steel-making (coke). Iodine: Medicines. Alloys An alloy is a mixture of metals or a metal with a non-metal. Alloys have improved properties like strength, resistance to rusting.

apa-style-referencing-visual-guide-2025.pdfIshika Ghosh

Title: A Quick and Illustrated Guide to APA Style Referencing (7th Edition) This visual and beginner-friendly guide simplifies the APA referencing style (7th edition) for academic writing. Designed especially for commerce students and research beginners, it includes: ✅ Real examples from original research papers ✅ Color-coded diagrams for clarity ✅ Key rules for in-text citation and reference list formatting ✅ Free citation tools like Mendeley & Zotero explained Whether you're writing a college assignment, dissertation, or academic article, this guide will help you cite your sources correctly, confidently, and consistent. Created by: Prof. Ishika Ghosh, Faculty. 📩 For queries or feedback: [email protected]

Phoenix – A Collaborative Renewal of Children’s and Young People’s Services C...Library Association of Ireland

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

How to Manage Opening & Closing Controls in Odoo 17 POSCeline George

The ever evoilving world of science /7th class science curiosity /samyans aca...Sandeep Swamy

The Ever-Evolving World of Science Welcome to Grade 7 Science4not just a textbook with facts, but an invitation to question, experiment, and explore the beautiful world we live in. From tiny cells inside a leaf to the movement of celestial bodies, from household materials to underground water flows, this journey will challenge your thinking and expand your knowledge. Notice something special about this book? The page numbers follow the playful flight of a butterfly and a soaring paper plane! Just as these objects take flight, learning soars when curiosity leads the way. Simple observations, like paper planes, have inspired scientific explorations throughout history.

Introduction to Vibe Coding and Vibe EngineeringDamian T. Gordon

YSPH VMOC Special Report - Measles Outbreak Southwest US 5-3-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

A measles outbreak originating in West Texas has been linked to confirmed cases in New Mexico, with additional cases reported in Oklahoma and Kansas. The current case count is 817 from Texas, New Mexico, Oklahoma, and Kansas. 97 individuals have required hospitalization, and 3 deaths, 2 children in Texas and one adult in New Mexico. These fatalities mark the first measles-related deaths in the United States since 2015 and the first pediatric measles death since 2003. The YSPH Virtual Medical Operations Center Briefs (VMOC) were created as a service-learning project by faculty and graduate students at the Yale School of Public Health in response to the 2010 Haiti Earthquake. Each year, the VMOC Briefs are produced by students enrolled in Environmental Health Science Course 581 - Public Health Emergencies: Disaster Planning and Response. These briefs compile diverse information sources – including status reports, maps, news articles, and web content– into a single, easily digestible document that can be widely shared and used interactively. Key features of this report include: - Comprehensive Overview: Provides situation updates, maps, relevant news, and web resources. - Accessibility: Designed for easy reading, wide distribution, and interactive use. - Collaboration: The “unlocked" format enables other responders to share, copy, and adapt seamlessly. The students learn by doing, quickly discovering how and where to find critical information and presenting it in an easily understood manner. CURRENT CASE COUNT: 817 (As of 05/3/2025) • Texas: 688 (+20)(62% of these cases are in Gaines County). • New Mexico: 67 (+1 )(92.4% of the cases are from Eddy County) • Oklahoma: 16 (+1) • Kansas: 46 (32% of the cases are from Gray County) HOSPITALIZATIONS: 97 (+2) • Texas: 89 (+2) - This is 13.02% of all TX cases. • New Mexico: 7 - This is 10.6% of all NM cases. • Kansas: 1 - This is 2.7% of all KS cases. DEATHS: 3 • Texas: 2 – This is 0.31% of all cases • New Mexico: 1 – This is 1.54% of all cases US NATIONAL CASE COUNT: 967 (Confirmed and suspected): INTERNATIONAL SPREAD (As of 4/2/2025) • Mexico – 865 (+58) ‒Chihuahua, Mexico: 844 (+58) cases, 3 hospitalizations, 1 fatality • Canada: 1531 (+270) (This reflects Ontario's Outbreak, which began 11/24) ‒Ontario, Canada – 1243 (+223) cases, 84 hospitalizations. • Europe: 6,814

Understanding P–N Junction Semiconductors: A Beginner’s GuideGS Virdi

Dive into the fundamentals of P–N junctions, the heart of every diode and semiconductor device. In this concise presentation, Dr. G.S. Virdi (Former Chief Scientist, CSIR-CEERI Pilani) covers: What Is a P–N Junction? Learn how P-type and N-type materials join to create a diode. Depletion Region & Biasing: See how forward and reverse bias shape the voltage–current behavior. V–I Characteristics: Understand the curve that defines diode operation. Real-World Uses: Discover common applications in rectifiers, signal clipping, and more. Ideal for electronics students, hobbyists, and engineers seeking a clear, practical introduction to P–N junction semiconductors.

Presentation of the MIPLM subject matter expert Erdem KayaMIPLM

Geography Sem II Unit 1C Correlation of Geography with other school subjectsProfDrShaikhImran

UNIT 3 NATIONAL HEALTH PROGRAMMEE. SOCIAL AND PREVENTIVE PHARMACYDR.PRISCILLA MARY J

How to track Cost and Revenue using Analytic Accounts in odoo Accounting, App...Celine George

LDMMIA Reiki Master Spring 2025 Mini UpdatesLDM Mia eStudios

Presentation on Tourism Product Development By Md Shaifullar RabbiMd Shaifullar Rabbi

SPRING FESTIVITIES - UK AND USA -Colégio Santa Teresinha

K12 Tableau Tuesday - Algebra Equity and Access in Atlanta Public Schoolsdogden2

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

SCI BIZ TECH QUIZ (OPEN) PRELIMS XTASY 2025.pptxRonisha Das

Quality Contril Analysis of Containers.pdfDr. Bindiya Chauhan

CBSE - Grade 8 - Science - Chemistry - Metals and Non Metals - WorksheetSritoma Majumder

apa-style-referencing-visual-guide-2025.pdfIshika Ghosh

Phoenix – A Collaborative Renewal of Children’s and Young People’s Services C...Library Association of Ireland

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

How to Manage Opening & Closing Controls in Odoo 17 POSCeline George

The ever evoilving world of science /7th class science curiosity /samyans aca...Sandeep Swamy

Introduction to Vibe Coding and Vibe EngineeringDamian T. Gordon

YSPH VMOC Special Report - Measles Outbreak Southwest US 5-3-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

Understanding P–N Junction Semiconductors: A Beginner’s GuideGS Virdi

Presentation of the MIPLM subject matter expert Erdem KayaMIPLM

Geography Sem II Unit 1C Correlation of Geography with other school subjectsProfDrShaikhImran

UNIT 3 NATIONAL HEALTH PROGRAMMEE. SOCIAL AND PREVENTIVE PHARMACYDR.PRISCILLA MARY J

Structural and functional testing

1. STRUCTURAL AND FUNCTIONAL TESTING Dr. Himanshu Hora SRMS College of Engineering & Technology Bareilly (INDIA)

2. CONTENTS       What is testing? Goals of testing Principles of Testing Structural and Functional Testing Types of Structural and Functional Testing Limitations

3. TESTING  According to the glossary of the IEEE standardization , testing is defined as: “The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the features of the software item”

4. GOALS OF TESTING  Goal of testing: finding faults in the software producing a zero defect software testing should be traceable it should be deterministic

5. PRINCIPLES OF TESTING  Test a program to try to make it fail  Start testing early

6. Cont…  Testing must be done by different persons at different levels

7. Cont…  Test a program innovatively  Use both static and dynamic testing

8. STRUCTURAL TESTING  Generates test cases based on the structure of the program  Also known as white box testing  The internal structure of the program is taken into account

9. FUNCTIONAL TESTING  Generates test cases based on the functionality of the software  Also known as black box testing  The internal structure of the program is hidden from the testing process

10. Cont…  Identify the functions which software is expected to perform  Treats the software as a "black box", examining functionality without any knowledge of internal implementation

11. TYPES OF STRUCTURAL TESTING  The different types of structural testing are :  Statement coverage: all statements in the programs should be executed at least once  Branch coverage: all branches in the program should be executed at least once

12. Cont…  Path coverage: all execution paths in the program should be executed at lest once  Conditional coverage: For conditional branches, this means that, we execute the TRUE branch at least once and the FALSE branch at least once

13. TYPES OF FUNCTIONAL TESTING  The different types of functional testing are:  Equivalence class partitioning: In this approach, the domain of input values to a program is partitioned into a set of equivalent classes  Boundary value analysis: It is the analysis of the programming error that frequently occurs at the boundaries of different equivalence classes of inputs

14. LIMITATIONS  Testing can be used to show the presence of errors, but never to show their absence  Software testing does not help in finding root causes  It can only identify the known issues or errors. It gives no idea about defects still uncovered.

15. THANK YOU Dr. Himanshu Hora SRMS College of Engineering & Technology Bareilly (INDIA)

Structural and functional testing

Recommended

More Related Content

What's hot (20)

Viewers also liked (12)

Similar to Structural and functional testing (20)

More from Himanshu (20)

Recently uploaded (20)

Structural and functional testing