PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

Lecture 8: Testing, Verification and Validation
SOFTWARE TESTING. Software Testing Principles Types of software tests Test planning Test Development Test Execution and Reporting Test tools and Methods.
System Integration Verification and Validation
Testing and Quality Assurance
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
System/Software Testing Error detection and removal determine level of reliability well-planned procedure - Test Cases done by independent quality assurance.
Software Quality Assurance Plan
Software Testing 3 Damian Gordon.
System Construction and Implementation Objectives:
CMSC 345, Version 11/07 SD Vick from S. Mitchell Software Testing.
Illinois Institute of Technology
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
Managing Software Quality
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
Software Systems Verification and Validation Laboratory Assignment 3 Integration, System, Regression, Acceptance Testing Assignment date: Lab 3 Delivery.
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
Lecture 11 Testing and Debugging SFDV Principles of Information Systems.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.
Chapter SIX Implementation, Testing and Pragmatics Making it a reality.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Sylnovie Merchant, Ph.D. MIS 161 Spring 2005 MIS 161 Systems Development Life Cycle II Lecture 5: Testing User Documentation.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Testing, Testing & Testing - By M.D.ACHARYA QA doesn't make software but makes it better.
MANUAL TESTING KS SESSION PRESENTED BY 26/11/015 VISHAL KUMAR.
PRESENTER PRIYANKA GUPTA.  Testing the complete system with respect to requirements.  In System testing, the functionalities of the system are tested.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
1 Software Testing Strategies: Approaches, Issues, Testing Tools.
What is a level of test?  Defined by a given Environment  Environment is a collection of people, hard ware, software, interfaces, data etc.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Integration testing After different modules of a system have been coded and unit tested: –modules are integrated in steps according to an integration plan.
CS 325: Software Engineering February 16, 2016 Designing a Design Class Diagram Design Class Diagrams DCD: Restaurant Example DCD: ATM Example Software.
Tool Support for Testing Classify different types of test tools according to their purpose Explain the benefits of using test tools.
SOFTWARE TESTING LECTURE 9. OBSERVATIONS ABOUT TESTING “ Testing is the process of executing a program with the intention of finding errors. ” – Myers.
Software Testing By Souvik Roy. What is Software Testing? Executing software in a simulated or real environment, using inputs selected somehow.
Advanced Higher Computing Science
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Software Testing Strategies for building test group
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Software Engineering (CSI 321)
Software Testing.
SOFTWARE TESTING OVERVIEW
Chapter 8 – Software Testing
Quality Management Perfectqaservices.
Software Testing.
Chapter 2: Testing throughout the software life cycle
Chapter 18 Software Testing Strategies
LEVEL OF TESTING J.ALFRED DANIEL, AP/CSE.
CHAPTER 2 Testing Throughout the Software Life Cycle
Introduction to Software Testing
Lecture 09:Software Testing
Verification and Validation Unit Testing
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Testing and Test-Driven Development CSC 4700 Software Engineering
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Software Testing & Quality Management
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
System Testing.
Systems Construction and Implementation
System Construction and Implementation
Systems Construction and Implementation
DEPLOYING SECURITY CONFIGURATION
TYPES OF TESTING.
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
System Analysis and Design:
Software Testing Strategies
Presentation transcript:

PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR Department of computer science and engineering Software TESTING METHODOLOGIES PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR

STM UNIT-4

STM Validation Activities: Unit testing, Integration Testing, Function testing, System testing, Acceptance testing

STM Unit Testing:   A unit is the smallest testable part of an application like functions, classes, procedures, interfaces. Unit testing is a method by which individual units of source code are tested to determine if they are fit for use. This module where the required inputs for the module under test are simulated for the purpose of module or unit testing is known as driver module.

STM Stubs: Stubs are dummy modules which are known as "called programs" which is used when sub programs are under construction. Integration Testing:   Once all the individual units are created and tested, we start combining those ―Unit Tested‖ modules and start doing the integrated testing. So the meaning of Integration testing is quite straight forward-Integrate/combine the unit tested module one by one and test the behaviour as a combined unit.

STM Function Testing:   Function testing is defined as ―the process of attempting to detect discrepancies between the functional specifications of a software and its actual behavior‖. When an integrated system is tested, all its specified functions and external interfaces are tested on the software. Every functionality of the system specified in the functions is tested according to its external specifications. The function test must determine if each component or business event:

STM System Testing:   --System testing is the type of testing to check the behavior of a complete and fully integrated software product based on the software requirements specification (SRS) document. --The main focus of this testing is to evaluate Business / Functional / End-user requirements

STM Recovery Testing: Recovery is just like the exception handling feature of a programming language. It is a type of non-functional testing. Recovery testing is done in order to check how fast and better the application can recover after it has gone through any type of crash or hardware failure etc.

STM Security Testing: --It is a type of non-functional testing.  --Security testing is basically a type of software testing that’s done to check whether the application or the product is secured or not.

STM Performance Testing: --Software performance testing is a means of quality assurance (QA). --It involves testing software applications to ensure they will perform well under their expected workload.

STM Load Testing: --Load testing is a type of non-functional testing. --A load test is type of software testing which is conducted to understand the behaviour of the application under a specific expected load.

STM Stress Testing: ·It is a type of non-functional testing. ·It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results.

STM Usability Testing: --Usability testing is an essential element of quality assurance. -- It is the measure of a product’s potential to accomplish the goals of the user

STM Compatibility / Conversion/Configuration Testing: --Compatibility is a non- functional testing to ensure customer satisfaction.   It is to determine whether your software application or product is proficient enough to run in different browsers, database, hardware, operating system, mobile devices and networks

STM Acceptance Testing:   --After the system test has corrected all or most defects, the system will be delivered to the user or customer for acceptance testing. --Acceptance testing is basically done by the user or customer although other stakeholders may be involved as well.

STM Types of Acceptance Testing: --> Alpha Testing   Types of Acceptance Testing: --> Alpha Testing  --> Beta Testing

STM Regression testing   Progressive Vs regressive testing, Regression testability, Objectives of regression testing, When regression testing done?, Regression testing types, Regression testing techniques

STM Progressive Vs Regressive testing: --All the test case design methods or testing technique, discussed till now are referred to as progressive testing or development testing. Regression Testability: Regression testability refers to the property of a program, modification or test suite that lets it be effectively and efficiently regression-tested.