Bug Triage & Smoke Testing

Question 1

What is Bug Triage?

Answer 1

Bug triage is a process where each bug is prioritized based on its severity, frequency, risk, etc. Triage term is used in the Software testing / QA to define the severity and priority of new defects.

Question 2

Why do we need to have ‘Bug Triage’?

Answer 2

The goal of Bug Triage is to evaluate, prioritize and assign the resolution of defects. The team needs to examine the severity of the defect, make changes as needed, finalize the resolution of the defects, and assign resources. Mainly used in agile project management.

Question 3

How often ‘Bug Triage’ needs to be conducted in a release?

Answer 3

The frequency of the Bug triage meeting is not fixed. It depends on project situation.
- Project schedule
- Number of defects in the system
- Impact on schedules of team members’ availability
- Overall project health

Question 4

Priority (and priority classes)

Answer 4

3 major classes:

• high (defects must be resolved ASAP as it affects the system severely and cannot be used until it fixed)
• medium (during the normal course of development activities defect should be resolved. It can wait until a new version is created)
• low (the defect is irritant but repair can be done once the more serious defects has been fixed)

Question 5

Severity

Answer 5

Severity is a degree of impact of the development or application.

The difference between SEVERITY and PRIORITY!
Severity - Impact on the process/application
Priority- Order to fix/take a look

Question 6

Smoke Testing

Answer 6

Smoke Testing is a kind of software testing performed after a software build to ascertain that the critical functionalities of the program are working fine. It is executed before any detailed functional or regression tests are executed on the software build. The purpose is to reject badly built applications so that the QA Team does not waste time installing and testing the software application.
- small set of test cases to ensure that the most important functions work
- it shows if a build is stable enough to proceed with further testing
- bugs are usually P1 (critical priority)
- “Happy Path” (it’s usually when user starts to use it with the intention to use it, not to break it)
- Like a test drive of a car

Question 7

What is Sanity Testing?

Answer 7

Sanity Testing is a kind of software testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If a sanity test fails, the build is rejected to save the time and costs involved in more rigorous testing.
- testing a story. very light testing, nothing deep.