• Save
SDLC vs STLC
Upcoming SlideShare
Loading in...5
×
 

SDLC vs STLC

on

  • 40,664 views

Difference between sdlc and stlc , bug lifecycle and testing methodologies.

Difference between sdlc and stlc , bug lifecycle and testing methodologies.

Statistics

Views

Total Views
40,664
Views on SlideShare
40,394
Embed Views
270

Actions

Likes
41
Downloads
0
Comments
12

6 Embeds 270

http://www.paxotech.com 116
http://sanitytesting.wordpress.com 112
http://www.scoop.it 38
http://statictesting.wordpress.com 2
http://localhost 1
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

15 of 12 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • nice clear information
    Are you sure you want to
    Your message goes here
    Processing…
  • so helpful but pls enable the save option frnd
    Are you sure you want to
    Your message goes here
    Processing…
  • so helpful...thank you so much for your effort :)
    Are you sure you want to
    Your message goes here
    Processing…
  • Really very helpful information ..Thank q ..
    Are you sure you want to
    Your message goes here
    Processing…
  • This is helpful for freshers to seek SQA job
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

SDLC vs STLC SDLC vs STLC Presentation Transcript

  • Software Testing& Quality Assurance
  • 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 specified requirements
  • Objectives of Testing :1) To confirm whether the application is developed according to customer requirements or not2) Finding defects3) To make sure all problems are resolved and close.4) Finally testing is helpful to deliver a quality product and risk-free product to the customer.
  • Software Development Life CycleVSSoftware Testing Life Cycle
  • Requirements gathering Gather as much information as possible about the details & specifications of the desired software from the client. This is nothing but the Requirements gathering stage done by The Business Analyst(BA) . He would prepare one document called Business Requirement Specification
  • Analysis Phase In this step all the requirements are analysed and studied. Estimating the resources. For example:- Time, Number of people etc Design Phase Plan the programming language like java , php , .net; database like oracle , mysql etc which would be suited for the project. also some high level functions & architecture. This is the Design Stage.
  • Coding Phase In this phase the Developers would prepare theSource Code Testing Phase Next you ,Test the software to verify that it is builtas per the specifications given by the client. This isthe TEST stage.
  • Maintenance Phase Once your software product is ready , you may to do some code changes to accommodate enhancements requested by the client. This would be Maintenance stage
  •  All these levels constitute the waterfall method of software development lifecycle. Testing in the waterfall model starts only after implementation is done. If we make serious mistakes in requirements ,design and architecture of software we will have to redesign the entire software to correct the error. To address this concern , the V model of testing was developed where for every phase, in the Development life cycle there is a corresponding Testing phase
  • V-Model In V-model, Development and testing are performed in parallel.
  • V-Model The left side of the model is Software Development Life Cycle – SDLC The right side of the model is Software Test Life Cycle – STLC Also called as Verification and Validation Model. Verification and Validation are the basic ingredients ofSoftware Quality Assurance (SQA) activities. “Verification” checks whether we are building the rightsystem, and “Validation” checks whether we are building the system right.
  • Verification Strategies Verification Strategies comprise of the following: Requirements Review. Design Review. Code Walkthrough. Code Inspections.
  • Validation Strategies Unit Testing. Integration Testing. System Testing. Performance Testing. Alpha Testing. User Acceptance Testing (UAT). Installation Testing. Beta Testing.
  • Testing The different stages in Software Test Life Cycle – Each of these stages have a definite Entry and Exit criteria , Activities & Deliverables associated with it.
  • Requirement AnalysisThe Test Engineer would study the document prepared by the BA in the first phase, and send a Review Report to Business Analyst(BA).Review Report is a document prepared by the Test Engineer while studying the BRS document and the points which he cannot understand and not clear are written in that report and sent to BA.
  • Requirement AnalysisActivities Identify types of tests to be performed. Gather details about testing priorities and focus. Prepare Requirement Traceability Matrix (RTM). Identify test environment details where testing is supposed to be carried out.Deliverables Requirement Traceability Matrix (RTM).
  • Test Planning This phase is also called Test Strategy phase. Typically , in this stage, a Senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the Test Plan.
  • Test Planning Activites  Preparation of test plan/strategy document for various types of testing  Test tool selection  Test effort estimation  Resource planning and determining roles and responsibilities.  Training requirement Deliverables  Test plan /strategy document.  Effort estimation document.
  • Test Case Development This phase involves creation, verification and rework of test cases & test scripts. Test data , is identified/created and is reviewed and then reworked as well.
  • Test Case DevelopmentActivities Create test cases, automation scripts (if applicable) Review and baseline test cases and scripts Create test dataDeliverables Test cases/scripts Test data
  • Test Environment Setup Test environment decides the software and hardware conditions under which a work product is tested. Test environment set-up is one of the critical aspects of testing process and can be done in parallel with Test Case Development Stage. Test team may not be involved in this activity if the customer/development team provides the test environment in which case the test team is required to do a readiness check (smoke testing) of the given environment.
  • Test Environment SetupActivities Understand the required architecture, environment set-up and prepare hardware and software requirement list for the Test Environment. Setup test Environment and test data Perform smoke test on the buildDeliverables Environment ready with test data set up Smoke Test Results.
  • Test Execution During this phase test team will carry out the testing based on the test plans and the test cases prepared. Bugs will be reported back to the development team for correction and retesting will be performed.
  • Test ExecutionActivities Execute tests as per plan Document test results, and log defects for failed cases Map defects to test cases in RTM Retest the defect fixes Track the defects to closureDeliverables Completed RTM with execution status Test cases updated with results Defect reports
  • Defects While executing test cases you may find that actual results vary from the expected results. This is nothing but a defect also called incident or bug. From discovery to resolution a defect moves through a definite lifecycle called the defect or bug lifecycle.
  • Defect Life Cycle When a tester finds a defect .The defect is assigned a status , new. The defect is assigned to development project manager who will analyze the defect. He will check whether it is a valid defect. If not , next the defect is checked whether it is in scope. Suppose you find a problem with the email functionality. But it is not part of the current release .Such defects are postponed. Next, manager checks whether a similar defect was raised earlier . If yes defect is assigned a status duplicate.
  • Defect Life Cycle If no the defect is assigned to developer who starts fixing the code. During this stage defect is assigned a status in- progress. Once code is fixed. Defect is assigned a status fixed Next the tester will re-test the code. In case the test case passes the defect is closed. If the test cases fails again the defect is re-opened and assigned to the developer
  • Defect Life Cycle The Tester/Developer finds the Bug. Reports the Defect in the Defect Tracking Tool. Status “Open” The concerned Developer is informed The Developer fixes the Defect The Developer changes the If the Defect re-occurs, the Status to “Resolved” status changes to “Re-Open” The Tester Re-Tests and changes Status to “Closed”
  • Test Cycle Closure Testing team will meet, discuss and analyze testing artifacts to identify strategies that have to be implemented in future, taking lessons from the current test cycle. The idea is to remove the process bottlenecks for future test cycles and share best practices for any similar projects in future.
  • Test Cycle ClosureActivities Evaluate cycle completion criteria based on Time, Test coverage, Cost, Software, Critical Business Objectives , Quality Document the learning out of the project Prepare Test closure report Qualitative and quantitative reporting of quality of the work product to the customer. Test result analysis to find out the defect distribution by type and severityDeliverables Test Closure report Test metrics
  • Thanks