1 / 18

Basics of Software Testing Tutorial

Testing performed by a developer on completion of the code is also categorized as testing. Reviewing the design in the design phase with the intent to improve the design is also considered as testing.

ifourtechnolab
Download Presentation

Basics of Software Testing Tutorial

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Testing Training iFour Consultancy Basic of Software Testing https://www.ifourtechnolab.com/microsoft-technology

  2. Topics • Understanding How Actual Testing Process take steps in Projects? • When and How to Start? • Points to keep in mind • Which method of testing can be use and When? • Bug Life cycle https://www.ifourtechnolab.com/microsoft-technology

  3. How Actual Testing Process take steps in Projects? • When and How to start? • During the requirement gathering phase, the analysis and verification of requirements are also considered as testing. • Reviewing the design in the design phase with the intent to improve the design is also considered as testing. • Testing performed by a developer on completion of the code is also categorized as testing. https://www.ifourtechnolab.com/microsoft-technology

  4. When and How to start? • Also consider this points for When and How to start? • Test Strategy • Test Plan • Test Cases • Test Data • Test Environment https://www.ifourtechnolab.com/microsoft-technology

  5. Test Strategy Flowchart of How to start testing Test Plan Test Cases Test Data Test Environment https://www.ifourtechnolab.com/microsoft-technology

  6. How Actual Testing Process take steps in Projects? • Points to keep in mind • Understand the task • Understand that what functionality/feature need to test • Think scenarios for that functionality/feature • Also think about the expected result for that • Check impact of that functionality/feature on other module https://www.ifourtechnolab.com/microsoft-technology

  7. How Actual Testing Process take steps in Projects? • Which method of testing can be use and When? • Ad-hoc Testing • Smoke Testing • Functional Testing • Regression testing • Retesting https://www.ifourtechnolab.com/microsoft-technology

  8. When to use? • Ad-hoc testing • This testing is without any planning and documentation. • Ad-hoc testing is used once tester getting build from developer and tester know any functionality flow. • For Ad-hoc testing tester need to test application as per their perspective. https://www.ifourtechnolab.com/microsoft-technology

  9. When to use? • Smoke testing • It is also called as build verification testing. It is used after getting any build tester check the main functionality is working or not. • Result of testing is used to decide that build is stable or not enough to test further. • Smoke testing is done once tester getting build foe testing. • Smoke testing is generally done by developer. • As per tester’s view once getting build need to do smoke testing because if build is not stable then no any further testing is required. https://www.ifourtechnolab.com/microsoft-technology

  10. When to use? • Functional testing • In functional testing, test the functionality of application as per the business requirements. • Once tester do smoke testing then need to do functional testing. • In functional testing need to check that completed functionality. • Also check that with positive and negative scenarios. • In functional testing execute the test cases which we created. • Also compare the Actual result with Expected result. https://www.ifourtechnolab.com/microsoft-technology

  11. When to use? • Regression testing • Regression testing is done when any change comes after that need to check that due to new change/functionality previously working functionality is impacted or not. • Regression testing is done when any new functionality is implemented in project. • Regression is also done when any new change comes then also need to check the previous working functionality. https://www.ifourtechnolab.com/microsoft-technology

  12. When to use? • Retesting • Retesting is done after any defect is resolved to make sure that defect is resolved or not it is retesting. • Retesting is done when bug is resolved. • In retesting need to check that, that bug is resolved or not. https://www.ifourtechnolab.com/microsoft-technology

  13. How Actual Testing Process take steps in Projects? • Bug Life Cycle • Bug life cycle is a specific states of defect which is goes through different states in entire life. • Bug life cycle is differ from organization to organization. • Bug life cycle start when tester found any defect. https://www.ifourtechnolab.com/microsoft-technology

  14. Flow diagram of Bug life Cycle NEW Assigned Open Fixed Duplicate/Rejected/Differed/Not a Bug Verified Pending Retest Retest Closed Reopen https://www.ifourtechnolab.com/microsoft-technology

  15. Bug life cycle • Stages of Bug life cycle • New - When tester find any new defect at that time bug status is New. • Assigned - Once tester post bug and then Any lead assign that bug to particular developer at that time that bug status is Assigned. • Open - When developer start work on that bug at that time status is Open. • Fixed - When developer make changes related to that bug then he/she change that bug status as Fixed. • Pending Retest - After fixing the defect, the developer assigns that defect to the tester for retesting the defect at their end and till the tester works on retesting the defect, the state of the defect remains in Pending Retest. https://www.ifourtechnolab.com/microsoft-technology

  16. Bug life cycle • Retest - When tester start work on that defect or check that that defect is resolved or not at that time at that status is Retest. • Reopen – While testing that defect tester find same issue again then tester change that status to Reopen. • Closed – When that defect resolved and working as per requirement then tester change that bug status as a Closed. https://www.ifourtechnolab.com/microsoft-technology

  17. Bug life cycle • More status of Bug life cycle • These status are not used frequently. • Duplicate – If defect is repeated or correspond to that defect other defect is already there then status is changed to Duplicate. • Rejected/Invalid – If defect is not genuine then bug status is Rejected/Invalid. • Deferred – If that bug is not in priority and expected to fixed in next release then that bug status is Deferred. • Not a Bug – If a defect does not have an any impact on functionality of the application then that bug status is Not a Bug. https://www.ifourtechnolab.com/microsoft-technology

  18. Thank you https://www.ifourtechnolab.com/microsoft-technology

More Related