Lesson 4: Bug Reporting and STLC

Size: px

Start display at page:

Download "Lesson 4: Bug Reporting and STLC"

Tobias Poole
5 years ago
Views:

1 Lesson 4: Bug Reporting and STLC

2 Website Home Work, Class Notes 2

3 Activity for Every Class: Status Call Please come few minutes early. Sit with with another one or two students Introduce yourself if you do not know them Talk to them about what you did since last class, what do we going to do in this class and if there are any blockers (regarding this QA course/class) Please do this in every class before the class begins at 830am 3

4 Opening Statement/Questions What is a bug (in testing)? What happens when a QA person/tester find a bug/defect/issue? 4

5 What is Bug? In Software testing, when the expected and actual behavior is not matching, an incident needs to be raised. An incident may be a Bug. It is a programmer's fault where a programmer intended to implement a certain behavior, but the code fails to correctly conform to this behavior because of incorrect implementation in coding. It is also known as Defect 5

6 Opening Statement/Questions Report appropriately Someone validates the issue/defect or as designed If fix is needed, it is assigned to developers When fixed, we tests to make sure that it is fixed Perform regression tests 6

7 BUG LIFE CYCLE 7

8 Bug Life Cycle 8

9 Testing Types Alpha testing Beta testing User Acceptance Testing Regression Testing 9

10 Testing Types Alpha testing - user comes to facility to test Beta testing - Software released (controlled) to the customer User Acceptance Testing - Software is tested by client/user to make sure it meets their needs 10

11 HW from Day (compare with image1) = (compare with image2) chtext=men%20shoes (compare with image3) 11

12 How to write bugs Steps Expected Behavior Actual Result Pass/Fail System should display System displayed Go to macys.com macy's Home Page macy's Home Page Pass Click on Sign In Link on the top right of the home page Enter valid credentials in the required fields and click on SIGN IN button System should take user to Secure Sign In page System should display account dashboard System took user to Secure Sign In page Pass System did not display account dashboard Fail 12

13 How to write bugs Use a valid credential to log in System should allow the user to log in System allowed the user to log in Pass - - Search Basketball Shoes from in Search Box System should display search results System displayed search results Pass From results, click on one of the products QuickView link to load the QuickView System should display the QuickView popup System displayed the QuickView popup Pass Add an item from product quickview Add the same item or another item System should display modal window with the product information and allow user to add the item in the cart System displayed modal window with the product information and allowed user to add the item in the cart System should display the added item in the cart System displayed the added item in the cart Pass Click the bag image System should take user to the Cart page System took user to the Cart page Pass Click on the name of the products System should take user to the product details page. Pass System took user to the product details page. Pass Click the bag image System should take user to the Cart page System took user to the Cart page Pass Click on the PROCED TO CHECKOUT button System should take user to a page where user can SIGN IN or CHECKOUT AS A GUEST System took user to CHECKOUT page to enter address Fail 13

14 What to include when writing bugs [Feature Name] Title Environment Steps to reproduce Expected Result Actual Result Visual Proof (screenshots, videos, text) 14

15 Title: Old Navy Search Results issue Environment - Production/QA, All major desktop browsers Steps to reproduce Go to Old Navy website Locate the search box Type Men Shoes in search box and hit enter 15

16 Title: Old Navy Search Results issue Expected Result System should display results which match design documents Actual Result Category name is wrong Shoe size etc. is wrong Visual Proof (screenshots, videos, text) 16

17 Before you REPORT - - Is it really a bug? Consult document/person - Is it reproducible consistently? - Is it browser related? Or, other settings related? (if you are not connected to internet, nothing will pass) - Isolate bug - identify exactly what the problem is. Saying "something is wrong" is not helpful 17

18 Before you REPORT - - Check if you are using the latest version - Check if the bug is known Please check whether the bug you are experiencing is already documented in the issue tracker. - File each issue separately If you have multiple issues, it is better to file them separately so they can be tracked more easily. 18

19 Bug Life Cycle 19

20 Regression Test Regression testing is the process of testing changes to computer programs to make sure that the older programming still works with the new changes. Regression testing is a normal part of the program development process 20

21 Regression Test When do we do regression test? Is it functional testing? How often do we perform this test? How many test cases do a regression test suite has? 21

22 Software Testing Life Cycle (STLC) 22

23 Preparing for a bug Steps Expected Behavior Actual Result Pass/Fail System should display System displayed Go to macys.com macy's Home Page macy's Home Page Pass Click on Sign In Link on the top right of the home page Enter valid credentials in the required fields and click on SIGN IN button System should take user to Secure Sign In page System should display account dashboard System took user to Secure Sign In page Pass System did not display account dashboard Fail 23

24 STLC 1. Requirement Analysis When the BRD is ready and shared with the stakeholders, the testing team starts high level analysis 2. Test Planning Test Team plans the strategy and approach. 3. Test Case Designing Develop the test cases based on scope and criterias. 4. Test Environment Setup When integrated environment is ready to validate the product. 5. Test Execution Real-time validation of product and finding bugs. 6. Test Closure Once testing is completed, matrix, reports, results are documented. 24

25 Summary of today s Lesson 25

26 Terminology Alpha testing Beta testing Retesting Regression Testing User Acceptance Testing Test Suite STLC Bug Life Cycle 26

27 27

28 28

29 Homework It will be posted in a day or two. I will send an when it is ready You will have 2 weeks to submit You can me after the first couple of attempts so that you can make sure that you are doing it right 29

Volume. User Manual and Resource Guide

Volume. User Manual and Resource Guide Volume 1 User Manual and Resource Guide User Manual and Resource Guide Game Gurus United States Telephone: (415) 800-3599 Brazil Telephone: 55 84-8723-2557 Email: info@gamegurus.com Table of Contents What