Software Testing

1,842 views

Published on

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • I think you liked this share. For more downloads like this goto the following url: http://goo.gl/05PIY
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
1,842
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
142
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Software Testing

  1. 1. Manual Testing
  2. 2. <ul><li>Overview of Testing </li></ul><ul><li>Quality Principles </li></ul><ul><li>Software Process </li></ul><ul><li>Standard and Certifications </li></ul><ul><li>Software Development Life Cycle </li></ul>TOPICS
  3. 3. <ul><li>To understand the role of testing in the total software development process. </li></ul><ul><li>To learn methods for testing: </li></ul><ul><ul><li>the internal software architecture </li></ul></ul><ul><ul><li>external system behavior (requirements ) </li></ul></ul>Goals
  4. 4. Overview of Testing
  5. 5. What is Software Testing ? Q: Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements or identify differences between expected and actual results. A:
  6. 6. <ul><li>Software Testing is important as it may cause mission failure, impact on operational performance and reliability if not done properly. </li></ul><ul><li>Effective software testing - deliver quality software products - satisfying - user’s requirements, needs and expectations. </li></ul>Q: A: Why Software Testing?
  7. 7. What are we Testing? Q: A: <ul><li>Input value ranges </li></ul><ul><li>Output ranges </li></ul><ul><li>Internal logic (processing) </li></ul><ul><li>External behavior </li></ul><ul><li>Internal module interfaces </li></ul><ul><li>External interfaces </li></ul>
  8. 8. <ul><li>Design a series of tests that have a high probability of finding errors prior to delivery. </li></ul>Goal of Testing
  9. 9. How much time should be spent for Testing? Q: Typically 30-40% of total SW project time prior to release. A:
  10. 10. Who Tests the Software?
  11. 11. QUALITY PRINCIPLES
  12. 12. <ul><ul><li>Quality is defined as meeting the customer’s requirements for the first time and every time. </li></ul></ul><ul><ul><li>Quality is much more than the absence of defects which allows us to meet customers expectations. </li></ul></ul>What is Quality ? Q: A:
  13. 13. <ul><ul><ul><li>Quality is the important factor affecting an organization’s long term performance. </li></ul></ul></ul><ul><ul><ul><li>Quality improves productivity and competitiveness in any organization. </li></ul></ul></ul>Why Quality ? Q: A:
  14. 14. <ul><li>Quality assurance is a planned and </li></ul><ul><li>systematic set of activities necessary to </li></ul><ul><li>provide adequate confidence that products </li></ul><ul><li>and services will conform to specified </li></ul><ul><li>requirements and meet user needs. </li></ul><ul><li>*It is process oriented. </li></ul><ul><li>*defect prevention based. </li></ul>Quality Assurance
  15. 15. <ul><li>Quality control is the process by which </li></ul><ul><li>product quality is compared with applicable </li></ul><ul><li>standards and the action taken when non </li></ul><ul><li>conformance is detected. </li></ul><ul><li>* It is product oriented. </li></ul><ul><li>* defect detection based. </li></ul>Quality Control
  16. 16. <ul><li>Quality </li></ul><ul><li>Cost </li></ul><ul><li>Schedule </li></ul>Factors Influencing a project
  17. 17. <ul><ul><li>“ A particular method of doing some thing, </li></ul></ul><ul><ul><li>generally involving a number of steps or operations “ </li></ul></ul><ul><li>The process that deals with the technical and </li></ul><ul><li>management issues of software development </li></ul><ul><li>is called S oftware Process </li></ul>Software Process
  18. 18. <ul><ul><li>Like all process the software development process follows a cycle comprised of the following four components. </li></ul></ul><ul><ul><li>Plan(P): Device a plan.Define your objective and determine the strategy and supporting methods required to achieve that objective. </li></ul></ul><ul><ul><li>Do(D): Executive the plan. Create the conditions and perform the necessary training to execute the plan. </li></ul></ul>Software Process
  19. 19. Software Process <ul><ul><li>Check (C): Check the results. Check to determine whether work is progressing according to the plan and whether the results are obtained. </li></ul></ul><ul><ul><li>Action (A): Take the necessary action. If your checkup reveals that the work is not being performed according to plan or that results are not what was anticipated device measures for appropriate action. </li></ul></ul>
  20. 20. Tester’s Workbench The tester’s workbench is a pictorial representation of how a specific test task is performed. Each workbench has the following components: Inputs – The entrance criteria or deliverables needed to perform testing.
  21. 21. Procedures –how work must be done; how methods, tools, techniques,and people are applied to perform a process. There are Do procedures and Check procedures. Procedures indicate the “best way” to meet standards. Deliverables – Any product or service produced by a process. Deliverables serve as both inputs to and outputs from a process. Standards – Measures used to evaluate products and identify nonconformance. Tools – Aids to performing the process.
  22. 23. ISO - International Organization for Standard SEI CMM - Software Engineering Institute - Capability Maturity Model(Carnegie Melon University) PCMM - People Capability Maturity Model Six Sigma - Zero Defect Orientation. Standards (or) Certifications
  23. 24. CMM level 5 Optimizing CMM level 4 Managed CMM level 3 Defined CMM level 2 Repeatable CMM level 1 Initial CMM -5 Levels
  24. 25. <ul><ul><li>Requirement Analysis </li></ul></ul><ul><ul><li>Design </li></ul></ul><ul><ul><li>Development </li></ul></ul><ul><ul><li>Testing </li></ul></ul><ul><ul><li>Implementation </li></ul></ul><ul><ul><li>Maintenance </li></ul></ul>SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
  25. 26. <ul><li>SRS - Software Requirement Specification </li></ul><ul><li>SRAS -Software Requirement Analysis Specification </li></ul><ul><li>SRS - FS (Functional Specification) </li></ul>Requirement Analysis
  26. 27. <ul><li>Design Phases: </li></ul><ul><ul><ul><ul><li>HLD : High Level Design. (System Design Document) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>LLD : Low Level Design. (Detailed Design Document) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>HLD+LLD => CDD (Comprehensive design document). </li></ul></ul></ul></ul>DESIGN
  27. 28. <ul><li>Coding :According to the Coding Format </li></ul><ul><li>Testing => Static(review) , Dynamic </li></ul><ul><li>Maintenance : Product Based Company ; Project Based Company ; </li></ul>Coding - Testing - Maintenance
  28. 29. What Testing Shows

×