Test progress reporting in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Test Progress Metrics

Which metric best describes the percentage of tests that have been executed out of the total planned tests?

A Test Execution Progress

B Test Coverage

C Defect Density

D Test Pass Rate

💡 Hint

Think about how much testing work has been done compared to what was planned.

Test Execution Progress measures how many tests have been run compared to the total planned tests, showing how far testing has advanced.

❓ Predict Output

intermediate

Output of Test Progress Calculation Code

What is the output of this Python code that calculates test progress percentage?

Testing Fundamentals

total_tests = 50
executed_tests = 30
progress = (executed_tests / total_tests) * 100
print(f"Test progress: {progress:.1f}%")

A Test progress: 30.0%

B Test progress: 50.0%

C Test progress: 60.0%

D Test progress: 15.0%

💡 Hint

Calculate the ratio of executed tests to total tests and multiply by 100.

30 executed tests out of 50 total means 30/50 = 0.6, multiplied by 100 is 60.0%.

❓ assertion

advanced

Correct Assertion for Test Progress Value

Which assertion correctly verifies that the test progress variable is at least 75%?

Testing Fundamentals

test_progress = 0.8  # Represents 80%

A assert test_progress > 75

B assert test_progress >= 0.75

C assert test_progress == 75

D assert test_progress >= 75

💡 Hint

Remember the variable is a decimal fraction, not a percentage number.

Since test_progress is 0.8 (80%), comparing it to 0.75 (75%) is correct. Comparing to 75 is wrong because it's not a percentage number.

🔧 Debug

advanced

Identify the Bug in Test Progress Reporting Code

What error will this JavaScript code cause when reporting test progress?

Testing Fundamentals

const totalTests = 100;
const executedTests = 40;
const progress = executedTests / totalTests * 100;
console.log('Test progress: ' + progress.toFixed(1) + '%');
if (progress > 100) {
  console.log('Progress cannot exceed 100%');
}

A Logical error: progress can never be greater than 100

B TypeError because toFixed is called on a string

C ReferenceError due to undefined variable

D No error; outputs 'Test progress: 40.0%'

💡 Hint

Check the data types and calculations carefully.

The code correctly calculates progress as 40, calls toFixed on a number, and prints the progress. No error occurs.

❓ framework

expert

Best Practice for Reporting Test Progress in Automation Framework

In a test automation framework, which approach best ensures accurate and real-time test progress reporting?

A Use event listeners to update progress immediately after each test completes

B Update a shared progress variable after each test and log progress at the end

C Calculate progress only once after all tests finish running

D Manually count passed tests and calculate progress after execution

💡 Hint

Think about how to get progress updates as tests run, not after all finish.

Using event listeners allows the framework to update progress in real-time as each test completes, providing accurate and timely reporting.