What is testing? manual testing toppics

1
Session On Software Testing

• BY
• RAMESH.P

2
THIS PRESENTATION DEALS WITH

• SDLC
• S/W DEVELOPMENTS MODELS
• TESTING TIME ESTIMATION FACTORS
• TESTING TIME ESTIMATION TABLE
• MOM SHEET
• TEST STRATEGIES (STATIC/DYNAMIC TESTING)
• BUG LIFE CYCLE
• BUG TRACKING SYSTEM
• S/W TESTING LIFE CYCLE
• TYPES OF S/W TESTING
• REQUIREMENT TRACEBILITY MATRIX
• TEST SCENARIOS
• TEST CASES

3
SOFTWARE DEVELOPMENT LIFE CYCLE

• REQUIREMENT ANALISYS
• DESIGNING
• CODING
• TESTING
• MAINTAINANCE

4
SOFTEARE DEVELOPMENT MODELS

1. WATERFALL MODEL
2. SPIRAL MODEL
3. INCREMENTAL MODEL
4. RAD MODEL
5. V Model
6. Prototype Model

5
TESTING TIME ESTIMATION

• DEPENDS ON
• Estimation sheet for project testing
• According to project cost
• According to resources available for testing.
• And average time of resources

6
TESTING TIME ESTIMATION TABLE
FEATURE IN PROJECT TIME FOR UI TESTING (IN HRS) TIME FOR FUNCTIONALITY TESTING TIME FOR DB TESTING TIME FOR MESCILLINEOUS TESTING


7
MOM SHEET

• Prepared To Manage The Meeting Time And To Avoid
  The Wastage Of Resources Time.
• Fields In Mom Sheet
• Date
• Time
• Topic
• No. Of invitees
• Session taken by
• No.of presentees
• No.of absentees
• Agenda
• Discussion point
• Discussion description
• Outcome
• Action

8

• TEST STRATEGIES
• 1)Static testing
• 2)Dynamic testing
• STATIC TESTING
• The testing which is performed up to actual
  testing phase is called static testing. The below
  tasks can performed under the static testing
• Requirement gathering and analysis
• Test plan preparation
• Test strategy(type of testing)
• Preparation of requirement traceability matrix
• Writing test scenarios
• Defining test cases
• Identifying dependencies and collecting data
• Test environment preparation/ test bed
  preperation

9

• Dynamic testing The testing which performed at
  the actual testing phase is called dynamic
  testing.
• Below tasks can be performed at dynamic testing
  stage
• Test execution
• Defect identification
• Reports preparation
• Test execution report
• Bugs report
• Testing summary report
• Open issues report
• Sign off report
• Tracking the defects
• Testing closure document preparation

10
Bug Life Cycle
RE OPEN
NEW
NOT OK
RE TESTING
WONT FIX
OPEN
FIXED
CANT REPRODUCE
OK
INVALIED
FIXED LATER
DUPLICATE
CLOSE
11

• Common fields in bug tracking
• Bug id
• Bug description
• Bug summary
• Severity
• BlockerS1
• CriticalS2
• MajorS3
• MinorS4
• TriviolS5
• Priority
• very highP1
• HighP2
• Mediump3
• Lowp4
• Very lowp5
• Steps to re produce
• Attachments
• Assigned to

12
SOFTWARE TESTING LIFE CYCLE

• Requirement gathering and analysis
• Test plan preparation
• Test strategy
• Test designing
• Test data preparation
• Test environment setup
• Test execution
• Defect identification, reporting and tracking
• Testing closure document

13

• TYPES OF TESTING
• Functionality testing Here functionality of the
  build can be test.
• Retesting This is also same as functionality
  testing but it can e performed after a bug is
  cleared.
• Regression testing This testing can be tests the
  dependant areas of a function.
• Integration testing Testing of functionality
  after integrating the modules.
• Smoke testing the testing of the build
  deployment and site link can be under smoke
  testing.
• Sanity testing main functionality can be checked
  first.
• Adhoc testing only seleted test cases can be
  tested here.
• Visibility testing
• Compatibility testing in which browsers our
  application can work and on what oss can test
  here.
• System testing/ application testing testing of
  the whole application.
• Exploratery testing
• Ui testing
• Monkey testing
• User acceptance testing testing by the client
  wheher the application is satisfying the client
  needs or not.
• performance testing
• Stress testing
• Load testing

14
Fields in Requirement traceability matrix

• Si.no
• Brd name
• Business requirement id as in brd
• Functional requirement description as in brd
• Fsd name
• Usecase Id as in fsd
• Usecase description as in fsd
• Module
• Test case id
• Test scenario
• Execution action flow
• Execution data requirement
• Test data
• Pdc
• Comments
• OU(operating unit)
• Tools covered
• Type of testing
• Status

15
Some common fields in test scenariostable

• Si.no
• Scenario Id
• Scenario summary
• Scenario description
• Preority

16
Some common fields in test case table

• Si.no
• Test case Id
• Test case summary
• Test steps
• Expected result
• Actual result(pass/fail/not applicable)
• Comments
• Preority
• Pre condition

17

• THANK YOU
• BY
• RAMESH

18
THANK YOU

• BY
• RAMESH.P