[Solved] What is wrong with this test code snippet? def tearDown(self): db.session.remove() db.drop_all() — Ans: No call to rollback() before drop_all() | Flask

Flask - Testing Flask Applications

What is wrong with this test code snippet?

def tearDown(self):
    db.session.remove()
    db.drop_all()

AMissing call to create_all() in tearDown

BtearDown should not remove session

Cdrop_all() should be in setUp, not tearDown

DNo call to rollback() before drop_all()

Step-by-Step Solution

Solution:

Step 1: Understand tearDown purpose
tearDown cleans up after tests by removing session and dropping tables.
Step 2: Identify missing rollback before drop_all()
Without rollback, pending changes may not be discarded, potentially causing errors or inconsistent state.
Final Answer:
No call to rollback() before drop_all() -> Option D
Quick Check:
Rollback before drop_all to discard changes [OK]

Quick Trick: Always rollback before dropping tables in tearDown [OK]

Common Mistakes:

MISTAKES

Master "Testing Flask Applications" in Flask

9 interactive learning modes - each teaches the same concept differently

More Flask Quizzes

What is wrong with this test code snippet?