Defect reporting best practices in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a clear and concise defect title.

Testing Fundamentals

defect = {
    'title': '[1]',
    'description': 'App crashes on login',
    'severity': 'High'
}

Drag options to blanks, or click blank then click option'

AApp crashes on login

BBug found

CCrash

DLogin issue

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague or too short titles that don't explain the issue.

Leaving the title empty or generic.

The defect title should be clear and concise, describing the issue precisely. 'App crashes on login' clearly states the problem.

2fill in blank

medium

Complete the code to include the correct severity level for a critical defect.

Testing Fundamentals

defect['severity'] = '[1]'

Drag options to blanks, or click blank then click option'

ALow

BMinor

CCritical

DTrivial

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'Critical' with 'Low' or 'Minor' severity.

Not assigning severity at all.

Critical severity indicates a defect that causes major failure or data loss and needs immediate attention.

3fill in blank

hard

Fix the error in the defect report by completing the code with the correct status value.

Testing Fundamentals

defect['status'] = '[1]'

Drag options to blanks, or click blank then click option'

ACloseded

BOpen

CIn Progress

DResolved

Attempts:

3 left

💡 Hint

Common Mistakes

Typos in status values causing confusion.

Using invalid or unsupported status terms.

The status 'Open' is correct for a newly reported defect. 'Closeded' is a typo and invalid.

4fill in blank

hard

Fill both blanks to create a defect report dictionary with a proper priority and reproducibility.

Testing Fundamentals

defect_report = {
    'priority': '[1]',
    'reproducible': '[2]'
}

Drag options to blanks, or click blank then click option'

AHigh

BNo

CYes

DLow

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing priority levels or using invalid values.

Incorrectly marking reproducibility.

Priority 'High' means the defect should be fixed soon. 'Reproducible' set to 'Yes' means the defect happens every time under the same conditions.

5fill in blank

hard

Fill all three blanks to complete the defect report with correct reporter, environment, and steps format.

Testing Fundamentals

defect = {
    'reporter': '[1]',
    'environment': '[2]',
    'steps_to_reproduce': '[3]'
}

Drag options to blanks, or click blank then click option'

Atester01

BWindows 11

C1. Open app\n2. Click login\n3. Observe crash

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic or unclear reporter names.

Not specifying environment details.

Writing vague or incomplete reproduction steps.

The reporter is 'tester01', environment is 'Windows 11', and steps to reproduce are clearly listed to help developers understand the issue.