Bird
Raised Fist0
Testing Fundamentalstesting~10 mins

Smoke testing and sanity testing in Testing Fundamentals - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define a smoke test function that checks if the main page loads.

Testing Fundamentals
def test_main_page_loads():
    response = client.get('/')
    assert response.status_code == [1]
Drag options to blanks, or click blank then click option'
A200
B404
C500
D302
Attempts:
3 left
💡 Hint
Common Mistakes
Using 404 which means page not found.
Using 500 which means server error.
2fill in blank
medium

Complete the code to perform a sanity test that verifies a feature flag is enabled.

Testing Fundamentals
def test_feature_flag_enabled():
    feature_flag = get_feature_flag('new_ui')
    assert feature_flag is [1]
Drag options to blanks, or click blank then click option'
ATrue
BFalse
CNone
D0
Attempts:
3 left
💡 Hint
Common Mistakes
Using False which means the feature is disabled.
Using None which means no value.
3fill in blank
hard

Fix the error in the test that checks if the login page contains the text 'Welcome'.

Testing Fundamentals
def test_login_page_text():
    response = client.get('/login')
    assert 'Welcome' [1] response.text
Drag options to blanks, or click blank then click option'
A!=
B==
Cin
Dnot in
Attempts:
3 left
💡 Hint
Common Mistakes
Using '==' which checks for exact match.
Using 'not in' which checks the opposite.
4fill in blank
hard

Fill both blanks to create a dictionary comprehension that maps test names to their pass status only if they passed.

Testing Fundamentals
results = {test[1]: status for test, status in test_results.items() if status [2] True}
Drag options to blanks, or click blank then click option'
A.upper()
B==
Cis
D.lower()
Attempts:
3 left
💡 Hint
Common Mistakes
Using '==' instead of 'is' for boolean comparison.
Using '.lower()' instead of '.upper()' for test names.
5fill in blank
hard

Fill both blanks to create a test report dictionary with test names in lowercase, their results, and only include failed tests.

Testing Fundamentals
failed_tests = {test[1]: result for test, result in all_tests.items() if result[2] False}
Drag options to blanks, or click blank then click option'
A.lower()
Cis
D.upper()
Attempts:
3 left
💡 Hint
Common Mistakes
Adding parentheses after result in the dictionary comprehension.
Using '==' instead of 'is' for boolean comparison.
Using '.upper()' instead of '.lower()' for test names.

Practice

(1/5)
1. What is the main purpose of smoke testing in software testing?
easy
A. To perform security testing on the application
B. To quickly check if the main features of a new build work
C. To verify the user interface design
D. To test detailed functionality of all features

Solution

  1. Step 1: Understand smoke testing purpose

    Smoke testing is done to quickly verify that the main features of a new software build are working and the build is stable enough for further testing.
  2. Step 2: Compare options with smoke testing definition

    To quickly check if the main features of a new build work matches this purpose exactly, while others describe different testing types.
  3. Final Answer:

    To quickly check if the main features of a new build work -> Option B
  4. Quick Check:

    Smoke testing = Quick main feature check [OK]
Hint: Smoke test = quick main feature check after build [OK]
Common Mistakes:
  • Confusing smoke testing with detailed testing
  • Thinking smoke testing checks UI design
  • Mixing smoke testing with security testing
2. Which of the following is the correct description of sanity testing?
easy
A. Checking specific functionality after small changes or bug fixes
B. Testing all features in detail after a major release
C. Performing load testing to check performance
D. Running automated tests for regression

Solution

  1. Step 1: Define sanity testing

    Sanity testing is a quick check of specific functionality or bug fixes after small changes to ensure they work as expected.
  2. Step 2: Match options to sanity testing

    Checking specific functionality after small changes or bug fixes correctly describes this focused testing, while others describe different testing types.
  3. Final Answer:

    Checking specific functionality after small changes or bug fixes -> Option A
  4. Quick Check:

    Sanity testing = Focused check after small changes [OK]
Hint: Sanity test = check specific fixes after small changes [OK]
Common Mistakes:
  • Confusing sanity testing with full regression testing
  • Thinking sanity testing covers all features
  • Mixing sanity testing with performance testing
3. Consider this scenario: A new build is deployed with multiple new features and bug fixes. Which testing should be done first to decide if detailed testing can proceed?
medium
A. Sanity testing on the fixed bugs only
B. Full regression testing on all features
C. Smoke testing on main features of the build
D. Performance testing under load

Solution

  1. Step 1: Identify testing purpose after new build

    After a new build with many changes, smoke testing is done first to quickly check main features and decide if the build is stable for further testing.
  2. Step 2: Evaluate options for initial testing

    Smoke testing on main features of the build matches this initial check. Sanity testing (Sanity testing on the fixed bugs only) is for small changes, not full builds. Full regression (Full regression testing on all features) and performance (Performance testing under load) come later.
  3. Final Answer:

    Smoke testing on main features of the build -> Option C
  4. Quick Check:

    New build? Start with smoke testing [OK]
Hint: New build? Start with smoke testing main features [OK]
Common Mistakes:
  • Starting with sanity testing on big builds
  • Skipping smoke testing and doing full regression immediately
  • Confusing performance testing as first step
4. A tester runs sanity testing after a small bug fix but finds unrelated features failing. What is the likely cause?
medium
A. Sanity testing scope was too narrow, missing regression tests
B. Smoke testing was done incorrectly
C. The bug fix introduced new unrelated bugs
D. Performance testing was skipped

Solution

  1. Step 1: Understand sanity testing scope

    Sanity testing focuses on verifying specific fixes or features, not the entire application.
  2. Step 2: Analyze failure of unrelated features

    If unrelated features fail, it means sanity testing missed broader checks. Full regression testing is needed to catch such issues.
  3. Final Answer:

    Sanity testing scope was too narrow, missing regression tests -> Option A
  4. Quick Check:

    Unrelated failures after sanity test? Need regression [OK]
Hint: Sanity test checks fixes only; unrelated fails need regression [OK]
Common Mistakes:
  • Blaming smoke testing for unrelated failures
  • Assuming bug fix always causes unrelated failures
  • Ignoring need for regression testing
5. A software team wants to improve testing efficiency after frequent small updates. Which approach best combines smoke and sanity testing?
hard
A. Perform performance testing before smoke or sanity testing
B. Skip smoke testing and run full regression after each update
C. Only run sanity testing on all features after every update
D. Run smoke testing on main features after every build, then sanity testing on specific fixes

Solution

  1. Step 1: Understand testing goals for frequent small updates

    To improve efficiency, quick checks are needed to catch major issues early, then focused checks on fixes.
  2. Step 2: Evaluate combined approach of smoke and sanity testing

    Running smoke testing on main features ensures build stability, followed by sanity testing on specific fixes ensures correctness of changes.
  3. Step 3: Eliminate other options

    Skipping smoke testing or running full regression every time is inefficient. Performance testing is unrelated to this goal.
  4. Final Answer:

    Run smoke testing on main features after every build, then sanity testing on specific fixes -> Option D
  5. Quick Check:

    Smoke then sanity for efficient small update testing [OK]
Hint: Smoke test main features, then sanity test fixes for efficiency [OK]
Common Mistakes:
  • Skipping smoke testing for faster results
  • Running full regression after every small update
  • Confusing performance testing with smoke/sanity
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard