12                                                                                                            

How do you log bugs/defects?

Defects logging, is a process of finding defects in the application under test or product by testing and recording feedback from customers and making new versions of the product that fix the defects or client feedback.

Defect tracking is an important process in software engineering as Complex and business-critical systems have hundreds of defects. One of the challenging factors is Managing, evaluating and prioritizing these defects. The number of defects gets multiplied over some time and to effectively manage them, a defect tracking system is used to make the job easier.

Reporter: Your name and email address.

Product: In which product did you find this bug.

Version: The product version, if any.

Component: These are the major sub-modules of the product.

Platform: Mention the hardware platform where you found this bug. The various platforms like ‘PC’, ‘MAC’, ‘HP’, ‘Sun’ etc.

Operating system: Mention all the operating systems where you found the bug. Operating systems like Windows, Linux, Unix, SunOS, and Mac OS. Also, mention the different OS versions like Windows NT, Windows 2000, Windows XP etc., if applicable.

Priority: When should a bug be fixed? Priority is generally set from P1 to P5. P1 as “fix the bug with the highest priority” and P5 as ” Fix when time permits”.

Severity: This describes the impact of the bug.

Types of Severity:

  • Blocker: No further testing work can be done.

Status: When you are logging the bug into any bug tracking system then by default the bug status will be ‘New’.
Later on, the bug goes through various stages like Fixed, Verified, Reopen, Won’t Fix, etc.


                                                                                                                                                Industry connect

Comments

Post a Comment

Popular posts from this blog

 34 What are the different ceremonies in an agile team? The  agile ceremonies list  includes: Sprint Planning Daily Stand-Up Sprint Review Sprint Retrospective 1. Sprint Planning The Sprint Planning ceremony sets teams up for success by ensuring everyone understands the sprint goals and how to achieve them. Structure Attendees Timing Duration Agile Framework The Product Owner brings the product backlog to discuss with the Development Team. The Scrum Master facilitates. Together, the Scrum Team does effort or storey point estimations. The product backlog must contain all the details necessary for estimation. The Product Owner should be able to clarify any doubts regarding the product backlog. 2. Daily Stand-Up The daily stand-up brings the team together and sets everyone up for the day. The team uses this time to identify blockers and share plans for the day. Structure Attendees Timing Duration Agile framework  This is an informal, standing meeting. All members of the...
Read more
 38 How do you choose which test case to automate? A test case should be automated if: The task is going to be repeated. It’s going to save time. The requirements, the test, or the task are low risk, stable, and unlikely to change often. The test is subject to human error. The test is time-consuming. The test has significant downtime between steps. The test is repetitive.
Read more
Image
4   Why do production and test environments have to be similar? The software requirement developed (Production) should be met with customer requirements. In three cases production server should be similar to the testing environment.  1. Software should be similar on both server 2. Hardware should be similar in both server 3. Data that is used for the business proposal should be similar on both server  Industry Connect
Read more