Software Testing presentation


Published on

Published in: Technology, Education
  • 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

No notes for slide

Software Testing presentation

  1. 1. Software Testing BY Kajjal Rekha
  2. 2. EXIT Software: Software is a programme that is made to execute the specific task. Concept of Testing: A car has been made properly with design. Then it has been delivered to customer. The customer start the car and after going some distance, he realized the car has no breaks. Problem-There is no testing is done before handover. Software Testing: Software testing is a planned process that is used to identify the correctness, completeness, security and quality of software. Next
  3. 3. EXIT Why Need Testing Testing is necessary for many reasons such as: 1) To show that the application satisfies customers’ needs/expectations. 2) To show that application is fit for purpose 3) Verification and Validation 4) Self judgment not possible E.g---->A banking application is delivered to customer with few bugs in it. End user of bank will suffer some problem due to bugs in application so he may quit using this bank also can go for some legal actions. To prevent these kind of scenarios testing is done. This is very general example. because of improve the quality and increase the reliability of the product. Previous Next
  4. 4. EXIT Types of Testing There are many types of software testing strategies: 1) Alpha testing 2) Beta testing 3) Smoke testing (Ad-hoc testing) 4) Functional testing 5) Integration testing 6) Regression testing 7) System testing 8) Load testing 9) Stress testing 10) Performance testing 11) User acceptance testing 12) Black box testing 13) White box testing Previous Next
  5. 5. EXIT Testing Tools Manual Test: Executing the test cases manually without any tool support is known as manual testing. Autometed Test: Automated software testing is the best way to increase effectiveness, efficiency and coverage of your software testing . Best Test Automation Tools 1. 2. 3. 4. 5. Telerik Test Studio HP Unified Functional Testing (UFT) software Selenium automates browsers TestComplete watir Previous Next
  6. 6. EXIT Testing Life Cycle The testing of software has its own life cycle. It starts with study and analyzing the requirements. Here is the software testing life cycle: 1) Requirement study 2) Test planning 3) writing and review the test cases 4) Bug logging and tracking 5) Close and reopen bugs Previous Next
  7. 7. EXIT When Stop Testing This can be difficult to determine. Many modern software applications are so complex and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are... 1) Deadlines; 2) Test cases completed with certain percentage passed; 3) Test budget has been depleted; 4) Bug rate is least; Previous Next
  8. 8. EXIT Final Report Testing is an art. The testing coverage is defined by exit criteria (There is exit criteria and entry criteria in the Test Strategy). For example, if the exit criteria says “The software will be acceptable to the client only if there are no critical defects, no high defects, no medium defects and only two low defects”, then all the critical, high, medium should be zero. Only 2 low defects are acceptable. Thus, 100% coverage is measured by the exit criteria. Also, 100% test cases must be executed in order to cover 100% of testing. Previous Next
  9. 9. EXIT Contact Us Web Q it Solution Natun Bazar, Badda, Dhaka. ph: 0167-307-683-7 Previous
  10. 10. EXIT Testing Life Cycle Requirements Analysis : The process by which customer needs are understood and documented. Previous
  11. 11. EXIT Testing Life Cycle Test planning: Test planning involves scheduling and estimating the system testing process, establishing process standards and describing the tests that should be carried out. Previous
  12. 12. Testing Life Cycle Writing and reviewing test cases: These factors should be taken into attention when writing test cases of any level. All test cases should reviewed and updated all the time. Previous
  13. 13. EXIT Testing Life Cycle Bug logging and tracking: A bug tracking system or defect tracking system is a softare application that is designed to help keep track of reported softare bugs in software development efforts. It may be regarded as a type of issue tracking systems. Previous
  14. 14. EXIT Testing Life Cycle Close and reopen bugs: written defects as they are found . Once the defects were fixed, retested them and if the passed, closed them. It defects were not fixed , then reopen them. Previous
  15. 15. Do you want to exit this page? YES NO