Software testing by risk management

Uploaded on


  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. www .KNAPP.c omSoftware Testing by Risk Management
  • 2. www .KNAPP.c omTesting methodology Software testing methodology, as shown at the next slide, implement the approach which supports examination of the project’s requirements, setting priorities based on risk analysis, and then determination of where to focus the testing efforts within the budget and the time constrains The test planning, based on the risk analysis, presents the testing functional breakdown, and briefly describes each test purpose. The design phase produces several STD documents (for each of the usability, performance, functionality, values range, track, recovery, & stability testing cycles Each testing phase measurements and defects will be concluded by a Software Test Report. A defects review ought to be done in order to reassess the pre-defined requirements
  • 3. www .KNAPP.c om Testing methodology Development Testing Life Cycle Life Cycle Requirements Risk AnalysisSystem Requirements Document Risk Analysis Document Test Plan System Test Detailed Plan (STP) System Design Design Test Design System Test Functionality Performance Sanity RegressionCoding / Construction Compatibility Recovery Stability Usability End to End Testing Approaches Stress Load Volume Compliance Non Functional System Test Reassessment of Results (STR) Requirements
  • 4. www .KNAPP.c om Testing Guidelines New Return Requirements Enhancements Single Business Bug Bug Flow ProcessRegression x x x x xSanity x x x x x xPerformanceFunctionality x x x x x xSystem Test x x x xEnd to End x xNonFunctional
  • 5. www .KNAPP.c omTesting approaches Regression Regression testing is any type of software testing that seeks to uncover new errors, or regressions, in existing functionality after changes have been made to a system, such as functional enhancements, patches or configuration changes Sanity A sanity test or sanity check is a basic test to quickly evaluate whether a claim or the result of a calculation can possibly be true. It is a simple check to see if the produced material is rational (that the materials creator was thinking rationally, applying sanity). The point of a sanity test is to rule out certain classes of obviously false results, not to catch every possible error Performance Performance Testing covers a wide range of engineering or functional evaluations where a material, product, system, or person is not specified by detailed material or component specifications: rather, emphasis is on the final measurable performance characteristics. Testing can be a qualitative or quantitative procedure Functionality Functional testing is a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output System Test System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the systems compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic End to End End-to-end testing is the process of testing transactions or business level products as they pass right through the computer systems. Thus this generally ensures that all aspects of the business are supported by the systems under test
  • 6. www .KNAPP.c omDefinitions Functionality the quality or state of being functional; especially: the set of functions or capabilities associated with computer software or hardware or an electronic device Enhancements Heighten, increase; especially: to increase or improve in value, quality, desirability, or attractiveness Patches A patch is a piece of software designed to fix problems with, or update a computer program or its supporting data Configuration changes Qualitative The term refers to descriptions or distinctions based on some quality or characteristic rather than on some quantity or measured value Quantitative The term refers to a type of information based in quantities or else quantifiable data Black-box testing Method of software testing that tests the functionality of an application as opposed to its internal structures or workings (see white-box testing). Specific knowledge of the applications code/internal structure and programming knowledge in general is not required. The tester is only aware of what the software is supposed to do, but not how White-box testing Also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of testing software that tests internal structures or workings of an application, as opposed to its functionality Compliance Conformity in fulfilling official requirements
  • 7. www .KNAPP.c omTest Plan and Report– high level structure Reporting and communication – Test plan – Test cases development and coverage – Test execution progress – Testing results
  • 8. www .KNAPP.c omDeveloped Interfaces Testing approach  Regression – Scope / week X / NA  Sanity – Scope / week X / NA  Performance – Scope / week X / NA  Functionality – Scope / week X NA
  • 9. www .KNAPP.c omDeveloped Components Testing approach  Regression – Scope / week X / NA  Sanity – Scope / week X / NA  Performance – Scope / week X / NA  Functionality – Scope / week X NA
  • 10. www .KNAPP.c omDeveloped Requirments Testing approach  R1 – Regression – Scope / week X / NA – Sanity – Scope / week X / NA – Performance – Scope / week X / NA – Functionality – Scope / week X NA  R2 – Regression – Scope / week X / NA – Sanity – Scope / week X / NA – Performance – Scope / week X / NA – Functionality – Scope / week X NA – End to End - Scope / week X NA
  • 11. www .KNAPP.c omIntegration Requirments Testing approach  Regression – Scope / week X / NA  Sanity – Scope / week X / NA  Performance – Scope / week X / NA  Functionality – Scope / week X NA
  • 12. www .KNAPP.c om Failed Test Cases Analysis
  • 13. www .KNAPP.c omNot tested and failed test casesper suite <> Component X – Failed – To be tested Component X – Failed – To be tested Component X – 8 Failed – To be tested Component X – Failed – To be tested
  • 14. www .KNAPP.c omChallenges during test <>
  • 15. www .KNAPP.c omChanges due to Challenges <>
  • 16. www .KNAPP.c omOpen Issues <>