CSE 201 Lecture Notes - Lecture 16: Seapine Software, Bug Tracking System, Use Case
26 Apr 2019
School
Department
Course
Professor
Document Summary
Eventually testers are going to find bug. Create story or task to fix bug. Fix the bug (when appropriate/work with customer) Check the fix and verify that it works. Update the bug report back to beginning of cycle. No matter how hard you work at coding carefully, some bugs will slip through. Sometimes: they"re programming errors, other times they"re just functionality issues. Even if it"s just to record and not fix until future. Most important thing about dealing with bugs = making sure they get recorded and tracked. Doesn"t matter which bug tracking software you use. Main thing is to make sure whole team knows how to use whatever piece of software you use. Keep track of everything: discussions, code changes, decisions. Whenever something changes, talk it over with team. If impact is significant in terms of functionality or schedule, then you"ve got to go back to the customer.
