TESTING (S,S,AND A,B) By KARTHIKEYAN KANDASAMY. TESTING Scenario testing – 1.System & 2. Usecase Defect bash System o Functional and non functional testing.

Slides:



Advertisements
Similar presentations
Test Yaodong Bi.
Advertisements

Software Testing How has agile changed the game? Karen Greaves.
Test process essentials Riitta Viitamäki,
SOFTWARE TESTING. Software Testing Principles Types of software tests Test planning Test Development Test Execution and Reporting Test tools and Methods.
Testing and Quality Assurance
Software Testing 3 Damian Gordon.
Component 4: Introduction to Information and Computer Science Unit 9: Components and Development of Large Scale Systems Lecture 5 This material was developed.
CT1404 Lecture 2 Requirement Engineering and Use Cases 1.
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
Implementation. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management. Understand.
Software Testing Prasad G.
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
Introduction to Software Testing
Types and Techniques of Software Testing
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
Pfleeger and Atlee, Software Engineering: Theory and Practice CS499 Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee 4 th Edition.
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
Web Development Process Description
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
ECE 355: Software Engineering
Extreme Programming Software Development Written by Sanjay Kumar.
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout.
Categories of Testing.
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 TESTING STRATEGIES CIS518001VA : ADVANCED SOFTWARE ENGINEERING TERM PAPER.
Software Systems Verification and Validation Laboratory Assignment 3 Integration, System, Regression, Acceptance Testing Assignment date: Lab 3 Delivery.
CS4311 Spring 2011 Verification & Validation Dr. Guoqiang Hu Department of Computer Science UTEP.
Introduction Telerik Software Academy Software Quality Assurance.
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
Objectives  Testing Concepts for WebApps  Testing Process  Content Testing  User Interface Testing  Component-level testing  Navigation Testing.
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
Introduction to Information and Computer Science Information Systems Lecture c This material (Comp4_Unit9c) was developed by OHSU, funded by the Department.
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee
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.
What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.
Software Testing Process By: M. Muzaffar Hameed.
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.
LECTURE 19 23/11/15 Software Quality and Testing.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
System Testing 12/09. Hierarchy of Testing Testing Program Testing Top Down Bottom Up Integration TestingUnit Testing System Testing Big Bang Sandwich.
System Testing Amina Al-Qattan Fatma Al-Mulla Shimaa Mulla
Software Quality & QA Management Jatin Parekh Sr Dir of QA, Visa
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
CS223: Software Engineering Lecture 31: Acceptance Testing.
Introduction to Software Testing Maili Markvardt.
Software Testing By Souvik Roy. What is Software Testing? Executing software in a simulated or real environment, using inputs selected somehow.
Non Functional Testing. Contents Introduction – Security Testing Why Security Test ? Security Testing Basic Concepts Security requirements - Top 5 Non-Functional.
Testing throughout Lifecycle Ljudmilla Karu. Verification and validation (V&V) Verification is defined as the process of evaluating a system or component.
Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik.
SaralTA Batch-07 Software Testing Presented By - Chittaranjan M.
Software Testing.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Testing the System.
Software Testing.
Chapter 2: Testing throughout the software life cycle
LEVEL OF TESTING J.ALFRED DANIEL, AP/CSE.
CHAPTER 2 Testing Throughout the Software Life Cycle
Introduction to Software Testing
Presentation transcript:

TESTING (S,S,AND A,B) By KARTHIKEYAN KANDASAMY

TESTING Scenario testing – 1.System & 2. Usecase Defect bash System o Functional and non functional testing Acceptance

SCENARIO TESTING Scenario testing is a software testing technique that makes best use of scenarios. Scenarios help a complex system to test better where in the scenarios are to be credible which are easy to evaluate. Methods in Scenario Testing: 1.System scenarios 2.Use-case and role-based scenarios

DEFECT BASH Defect bash (or bug bash) is a testing event where a group of people tries to find as many defects as possible from the software. OR It is an adhoc testing where people performing different role in an organization test the product together at the same time.

Enabling people “Cross boundaries and test beyond assigned areas” Bringing different people performing different roles together in the organization for testing—“Testing isn’t for testers alone” Letting everyone in the organization use the product before delivery—“Eat your own dog food” Bringing fresh pairs of eyes to uncover new defects—“Fresh eyes have less bias” Bringing in people who have different levels of product understanding to test the product together randomly—“Users of software are not same” Let testing doesn’t wait for lack of/time taken for documentation—“Does testing wait till all documentation is done?” Enabling people to say “system works” as well as enabling them to “break the system“—”Testing isn’t to conclude the system works or doesn’t work”

ACCEPTANCE TESTING Acceptance testing, a testing technique performed to determine whether or not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is has met the required criteria for delivery to end users. There are various forms of acceptance testing 1.User acceptance Testing 2.Business acceptance Testing 3.Alpha Testing 4.Beta Testing

Acceptance Criteria Acceptance criteria are defined on the basis of the following attributes Functional Correctness and Completeness Data Integrity Data Conversion Usability Performance Timeliness Confidentiality and Availability Installability and Upgradability Scalability Documentation

SYSTEM TESTING System Testing (ST) is a black box testing technique performed to evaluate the complete system the system's compliance against specified requirements. In System testing, the functionalities of the system are tested from an end-to-end perspective.

ACCEPTANCE TEST PLAN - ATTRIBUTES The Acceptance test plan has the following attributes: 1.Introduction 2.Acceptance Test Category 3.operation Environment 4.Test case ID 5.Test Title 6.Test Objective 7.Test Procedure 8.Test Schedule 9.Resources

ACCEPTANCE LIFECYCLE

Functional Testing Non- Functional Testing 1. In functional Testing tester tests how well the system performs. 1. In Non-Functional Testing tester tests how well the system responds. 2. Functional Testing is based on client requirements. 2. Non- Functional Testing is based on client expectations. 3. Functional Testing means Testing the application against business requirements. 3. Non- Functional Testing means Testing the application against clients and performance requirements. 4. It is a part of System Testing.4. It is also a part of System Testing 5. Functional Testing Validating the behavior of application. 5. Non- Functional Testing Validating the performance of application. 6. This Testing covers Unit Testing, Integration Testing, Smoke Testing, Sanity Testing, Regression Testing and so on. 6. This Testing covers Load/Performance Testing, Stress/Volume Testing, Security Testing, Installation Testing and so on. 7. It is always concentrating on customer requirements. 7. It is always concentrating on customer expectations. 8. Functional Testing means how is your system is doing. 8. Non- Functional Testing means how well your system is doing example usability, performance and stress testing.

A few examples of non-functional testing include the following kinds of tests - Performance Testing Security Testing Usability Testing Reliability and Dependability Testing Endurance testing Load testing Localization testing and Internationalization testing Ergonomics Testing Operational Readiness Testing Installation Testing Configuration Testing Compatibility Testing Interoperability Testing Maintainability Testing Availability Testing Recoverability Testing and Miscellaneous Testing