Testing and quality assurance in Intro to Computing - Draw & Build Visually

Draw This - beginner

Draw a flowchart that shows the basic steps of testing and quality assurance for a software program. Include steps for planning tests, executing tests, checking results, and fixing errors.

10 minutes

Hint 1

Hint 2

Hint 3

Hint 4

Grading Criteria

Start and End symbols present

Decision diamonds used for checking test results and all tests passed

Process boxes for planning, executing, reporting, and fixing

Correct flow from test execution to result checking

Loop back to re-execute tests after fixing errors

Clear labeling of pass and fail paths

Solution

  +-------------------+
  | Start Testing Plan |
  +---------+---------+
            |
            v
  +-------------------+
  | Execute Test Case  |
  +---------+---------+
            |
            v
  +-------------------+
  | Check Test Result? |
  +----+---------+----+
       |         |
       | Pass    | Fail
       |         |
       v         v
+--------------+  +----------------+
| All Tests    |  | Report & Fix   |
| Passed?      |  | Errors         |
+----+----+---+  +--------+-------+
     |    |               |
     |    |               v
     |    |        +--------------+
     |    |        | Re-execute   |
     |    |        | Test Case    |
     |    |        +------+-------+
     |    |               |
     |    +---------------+
     |                    
     v                    
+------------+            
| End Testing|            
+------------+            

This flowchart starts with planning the testing process. Then, it moves to executing a test case. After execution, it checks the test result.

If the test passes, it checks if all tests have passed. If yes, testing ends successfully.

If the test fails, errors are reported and fixed, then the test case is re-executed. This loop continues until all tests pass.

Variations - 2 Challenges

[intermediate] Draw a flowchart for testing a single feature of a software application, including planning, running the test, checking results, and deciding if the feature is ready or needs improvement.

[advanced] Draw a detailed flowchart for quality assurance that includes test planning, multiple test executions, bug reporting, fixing, regression testing, and final approval.

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