Testing and quality assurance in Intro to Computing - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to print a message when a test passes.

Intro to Computing

if test_result == [1]:
    print("Test passed!")

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

ANone

BFalse

CTrue

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using False instead of True

Using 0 or None which mean failure or no result

The test_result should be True to indicate the test passed.

2fill in blank

medium

Complete the code to raise an error if a test fails.

Intro to Computing

if not test_passed:
    raise [1]("Test failed!")

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

AIndexError

BAssertionError

CTypeError

DValueError

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated error types like TypeError or IndexError

Not raising any error on failure

AssertionError is commonly used to indicate a failed test assertion.

3fill in blank

hard

Fix the error in the test function to correctly check equality.

Intro to Computing

def test_sum():
    result = sum([1, 2, 3])
    assert result [1] 6

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

A==

B!=

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using != which means not equal

Using > or < which check inequality

The test should assert that the result is equal to 6 using ==.

4fill in blank

hard

Fill both blanks to create a test that checks if a number is positive.

Intro to Computing

def test_positive(num):
    assert num [1] 0 and num [2] 0

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

A>

B<

C!=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of >

Using == instead of !=

The test checks if num is greater than 0 and not equal to 0.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that filters passing scores.

Intro to Computing

passing_scores = {student: score for student, score in scores.items() if score [1] [2] and student [3] ''}

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

A>=

B60

C!=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of >=

Using == instead of !=

Using wrong passing score value

This comprehension keeps students with scores greater or equal to 60 and non-empty names.

Practice

1. What is the main purpose of testing in software development?

easy

A. To check if the software works as expected

B. To design the user interface

C. To write the software code

D. To deploy the software to users

Solution

1. Step 1: Understand the role of testing

   Testing is done to verify that software behaves correctly and meets requirements.

2. Step 2: Compare options with testing purpose

   Only To check if the software works as expected describes checking software functionality, which matches testing's main goal.

3. Final Answer:

   To check if the software works as expected -> Option A

4. Quick Check:

   Testing = Check software works [OK]

Hint: Testing means checking software behavior matches expectations [OK]

Common Mistakes:

• Confusing testing with coding
• Thinking testing is deployment
• Mixing testing with design tasks

2. Which of the following is the correct syntax to write a test case name in many testing frameworks?

easy

A. test_function

B. TestFunction

C. testFunction()

D. functionTest

Solution

1. Step 1: Identify common test naming conventions

   Many testing frameworks use lowercase with underscores for test case names, like test_function.

2. Step 2: Compare options with naming style

   test_function matches the common snake_case style used in tests, while others do not follow typical test naming.

3. Final Answer:

   test_function -> Option A

4. Quick Check:

   Test case names often use snake_case [OK]

Hint: Test names usually use lowercase with underscores [OK]

Common Mistakes:

• Using camelCase or PascalCase for test names
• Omitting 'test' prefix in test names
• Confusing function names with test names

3. Consider this pseudocode for a test checking if a number is positive:

function testIsPositive() {
  input = -5
  result = isPositive(input)
  assert(result == false)
}

What will the test result be if isPositive returns true for negative numbers by mistake?

medium

A. Test passes successfully

B. Test is skipped automatically

C. Test causes a runtime error

D. Test fails because assertion is false

Solution

1. Step 1: Understand the test logic

   The test expects isPositive(-5) to return false. The assertion checks if result equals false.

2. Step 2: Analyze the wrong function behavior

   If isPositive wrongly returns true for -5, the assertion result == false fails.

3. Final Answer:

   Test fails because assertion is false -> Option D

4. Quick Check:

   Wrong output causes assertion failure [OK]

Hint: If output differs from expected, assertion fails [OK]

Common Mistakes:

• Assuming test passes despite wrong output
• Confusing assertion failure with runtime error
• Thinking test skips on failure

4. A developer wrote this test code:

def test_divide():
  result = divide(10, 0)
  assert(result == 0)

What is the main problem with this test?

medium

A. It has a syntax error in assert

B. It uses wrong variable names

C. It does not check for division by zero error

D. It tests the wrong function

Solution

1. Step 1: Understand division by zero behavior

   Dividing by zero usually causes an error or exception, not a result of zero.

2. Step 2: Analyze the test assertion

   The test expects result to be zero, but it should check if an error is raised instead.

3. Final Answer:

   It does not check for division by zero error -> Option C

4. Quick Check:

   Division by zero needs error handling test [OK]

Hint: Division by zero should raise error, not return zero [OK]

Common Mistakes:

• Assuming divide returns zero on zero divisor
• Ignoring exception handling in tests
• Confusing syntax errors with logic errors

5. A software team wants to improve overall quality by combining testing with good development practices. Which approach best describes quality assurance?

hard

A. Only running automated tests before release

B. Using testing plus code reviews, documentation, and process checks

C. Writing code without any tests to save time

D. Ignoring user feedback after software release

Solution

1. Step 1: Define quality assurance scope

   Quality assurance (QA) includes testing and also good practices like code reviews, documentation, and process improvements.

2. Step 2: Evaluate options against QA definition

   Using testing plus code reviews, documentation, and process checks covers testing plus other practices, matching QA's broad approach. Others focus only on testing or ignore quality.

3. Final Answer:

   Using testing plus code reviews, documentation, and process checks -> Option B

4. Quick Check:

   QA = Testing + good practices [OK]

Hint: QA means testing plus good development practices [OK]

Common Mistakes:

• Thinking QA is only testing
• Skipping documentation and reviews
• Ignoring user feedback importance