sdlc-(15/12)

PowerPoint Presentation: 

Software-testing ….An overview

PowerPoint Presentation: 

Introduction What is Software Testing? Why testing is necessary? Who does the testing? What has to be tested? When is testing done? How often to test?

PowerPoint Presentation: 

What is software testing? The primary purpose of testing is to detect software failures so that defects may be discovered and corrected. Why testing is necessary? Software testing is performed to verify that the completed software package functions according to the expectations defined by the requirements/specifications Who does the testing?

PowerPoint Presentation: 

Phases of SDLC Requirement Specification and Analysis Design Coding Testing Implementation Maintenance SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

PowerPoint Presentation: 

Requirements Specification and Analysis User Requirement Specification(URS) System Requirement Specification-SRS

PowerPoint Presentation: 

The output of SRS is the input of design phase. Two types of design - High Level Design (HLD) Low Level Design (LLD) Design

PowerPoint Presentation: 

List of modules and a brief description of each module. Brief functionality of each module. Interface relationship among modules. Dependencies between modules (if A exists, B exists etc). Database tables identified along with key elements. Overall architecture diagrams along with technology details. High Level Design (HLD)

PowerPoint Presentation: 

Detailed functional logic of the module, in pseudo code. Database tables, with all elements, including their type and size. All interface details. All dependency issues Error message listings Complete input and outputs for a module. Low Level Design (LLD)

PowerPoint Presentation: 

Breaking down the product into independent modules to arrive at micro levels. 2 different approaches followed in designing – Top Down Approach Bottom Up Approach The Design process

PowerPoint Presentation: 

Coding Developers use the LLD document and write the code in the programming language specified. Testing The testing process involves development of a test plan, executing the plan and documenting the test results. Implementation Installation of the product in its operational environment.

PowerPoint Presentation: 

Srihari Techsoft Maintenance After the software is released and the client starts using the software, maintenance phase is started. 3 things happen - Bug fixing, Upgrade, Enhancement Bug fixing – bugs arrived due to some untested scenarios. Upgrade – Upgrading the application to the newer versions of the software. Enhancement - Adding some new features into the existing software.

PowerPoint Presentation: 

SOFTWARE LIFE CYCLE MODELS WATERFALL MODEL V-PROCESS MODEL SPIRAL MODEL PROTOTYPE MODEL INCREMENTAL MODEL EVOLUTIONARY DEVELOPMENT MODEL

PowerPoint Presentation: 

WATERFALL MODEL: Requirements: – defines needed information, function, behavior, performance and interfaces. Design data structures, software architecture, interface representations, algorithmic details. Implementation source code, database, user documentation, testing.

PowerPoint Presentation: 

INCREMENTAL MODEL: Construct a partial implementation of a total system Then slowly add increased functionality The incremental model prioritizes requirements of the system and then implements them in groups. Each subsequent release of the system adds function to the previous release, until all designed functionality has been implemented.

PowerPoint Presentation: 

SPIRAL MODEL: It uses risk reduction mechanism four major activities are planning, risk analysis , engineering, customer evaluation Each cycle involves the same sequence of steps as the waterfall process model

V-Shaped SDLC Model: 

V-Shaped SDLC Model A variant of the Waterfall that emphasizes the verification and validation of the product. Testing of the product is planned in parallel with a corresponding phase of development

Structured Evolutionary Prototyping Steps: 

Structured Evolutionary Prototyping Steps A preliminary project plan is developed An partial high-level paper model is created The model is source for a partial requirements specification A prototype is built with basic and critical attributes The designer builds the database user interface algorithmic functions The designer demonstrates the prototype, the user evaluates for problems and suggests improvements. This loop continues until the user is satisfied

Rapid Application Model (RAD): 

Rapid Application Model (RAD) Requirements planning phase (a workshop utilizing structured discussion of business problems) User description phase – automated tools capture information from users Construction phase – productivity tools, such as code generators, screen generators, etc. inside a time-box. (“Do until done”) Cutover phase -- installation of the system, user acceptance testing and user training

Agile SDLC’s: 

Agile SDLC’s Speed up or bypass one or more life cycle phases Usually less formal and reduced scope Used for time-critical applications Used in organizations that employ disciplined methods

Some Agile Methods: 

Some Agile Methods Adaptive Software Development (ASD) Feature Driven Development (FDD) Crystal Clear Dynamic Software Development Method (DSDM) Rapid Application Development (RAD) Scrum Extreme Programming (XP) Rational Unify Process (RUP)

Extreme Programming - XP: 

Extreme Programming - XP For small-to-medium-sized teams developing software with vague or rapidly changing requirements Coding is the key activity throughout a software project Communication among teammates is done with code Life cycle and behavior of complex objects defined in test cases – again in code

Testing Levels: 

Testing Levels Unit testing Integration testing System testing Acceptance testing

PowerPoint Presentation: 

Unit testing The most ‘micro’ scale of testing. Tests done on particular functions or code modules. Requires knowledge of the internal program design and code. Done by Programmers (not by testers).

PowerPoint Presentation: 

Integration Testing Testing of combined parts of an application to determine their functional correctness. ‘Parts’ can be code modules individual applications client/server applications on a network.

PowerPoint Presentation: 

Types of Integration Testing Big Bang testing :- all or most of the developed modules are coupled together to form a complete software system or major part of the system and then used for integration testing. Top Down Integration testing Bottom Up Integration testing

PowerPoint Presentation: 

Top-down approach

PowerPoint Presentation: 

Bottom-Up Approach

PowerPoint Presentation: 

System Testing To demonstrate that the system performs both functionally and operationally as specified Acceptance Testing To verify that the system meets the user requirements

PowerPoint Presentation: 

Srihari Techsoft Testing Levels/ Techniques White Box Black Box Incre- mental Thread Unit Testing X Integration Testing X X X System Testing X Acceptance Testing X

TESTING METHODOLOGIES AND TYPES: 

TESTING METHODOLOGIES AND TYPES

PowerPoint Presentation: 

Testing methodologies Black box testing White box testing Incremental testing

PowerPoint Presentation: 

Black box testing No knowledge of internal design or code required. Tests are based on requirements and functionality White box testing Knowledge of the internal program design and code required. Tests are based on coverage of code statements,branches,paths,conditions.

PowerPoint Presentation: 

Incremental Testing A disciplined method of testing the interfaces between unit-tested programs as well as between system components. Involves adding unit-testing program module or component one by one, and testing each result and combination.

PowerPoint Presentation: 

There are two types of incremental testing Top-down – testing form the top of the module hierarchy and work down to the bottom. Modules are added in descending hierarchical order. Bottom-up – testing from the bottom of the hierarchy and works up to the top. Modules are added in ascending hierarchical order.

PowerPoint Presentation: 

Major Testing Types Stress / Load Testing Performance Testing Recovery Testing Conversion Testing Usability Testing

PowerPoint Presentation: 

Stress Testing Testing under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database etc. Term often used interchangeably with ‘load’ and ‘performance’ testing. Performance testing Testing how well an application complies to performance requirements.

Usability Test: 

Recovery testing Testing how well a system recovers from crashes, HW failures or other problems. Conversion testing Testing of code that is used to convert data from existing systems for use in the newly replaced systems Usability Test Testing the system for the users to learn and use the product.

PowerPoint Presentation: 

Functional testing Black box type testing geared to functional requirements of an application. Done by testers. System testing Black box type testing that is based on overall requirements specifications; covering all combined parts of the system. End-to-end testing Similar to system testing; involves testing of a complete application environment in a situation that mimics real-world use.

PowerPoint Presentation: 

Sanity testing Initial effort to determine if a new software version is performing well enough to accept it for a major testing effort. Regression testing Re-testing after fixes or modifications of the software or its environment.

PowerPoint Presentation: 

Exploratory testing / ad-hoc testing Informal SW test that is not based on formal test plans or test cases; testers will be learning the SW in totality as they test it. Comparison testing Comparing SW strengths and weakness to competing products. Alpha testing Testing done when development is nearing completion; minor design changes may still be made as a result of such testing. Beta-testing Testing when development and testing are essentially completed and final bugs and problems need to be found before release.

TEST PLAN : 

TEST PLAN Objectives To create a set of testing tasks. Assign resources to each testing task. Estimate completion time for each testing task. Document testing standards.

PowerPoint Presentation: 

TEST CASES Test case is defined as A set of test inputs, execution conditions and expected results, developed for a particular objective. Documentation specifying inputs, predicted results and a set of execution conditions for a test item. Contents Test plan reference id Test case Test condition Expected behavior

THANK YOU: 

THANK YOU