Testing with database in Flask - Performance & Optimization

Performance: Testing with database

MEDIUM IMPACT

This concept affects page load speed and interaction responsiveness by how database queries during tests impact server response time.

Running tests that involve database operations

Flask

import pytest

@pytest.fixture
def test_db():
    db.create_all()
    yield db
    db.drop_all()

def test_user_creation(client, test_db):
    user = User(name='Test')
    test_db.session.add(user)
    test_db.session.flush()  # no commit
    response = client.get('/users')
    assert response.status_code == 200

Uses an isolated in-memory test database and flushes instead of committing to avoid slow disk writes.

📈 Performance GainReduces test runtime by avoiding disk I/O; faster test feedback loop.

Running tests that involve database operations

Flask

def test_user_creation(client):
    user = User(name='Test')
    db.session.add(user)
    db.session.commit()
    response = client.get('/users')
    assert response.status_code == 200

This test commits to the real database, causing slow tests and possible data pollution.

📉 Performance CostBlocks test execution for multiple milliseconds per commit; slows overall test suite.

Performance Comparison

Pattern	DB Operations	Test Runtime	Server Response Delay	Verdict
Real DB commit in tests	Full commit to disk	High (slow)	High delay	[X] Bad
In-memory DB with flush	No commit, flush only	Low (fast)	Minimal delay	[OK] Good

Rendering Pipeline

Database testing affects server response time which impacts how fast the browser receives data to render. Slow DB tests delay server responses, increasing interaction latency.

→Server Processing

→Network Transfer

→Rendering

⚠️ BottleneckServer Processing due to blocking database commits

Core Web Vital Affected

INP

This concept affects page load speed and interaction responsiveness by how database queries during tests impact server response time.

Optimization Tips

1Avoid committing to the real database during tests to reduce blocking disk writes.

2Use in-memory or mock databases to speed up test execution.

3Flush session changes instead of committing when possible to minimize delays.

Performance Quiz - 3 Questions

Why is committing to the real database during tests a performance problem?

A It improves test accuracy and speed.

B It causes slow disk writes and blocks test execution.

C It reduces server response time.

D It has no impact on performance.

DevTools: Network

How to check: Run tests and observe server response times in the Network panel; look for long waiting (TTFB) times.

What to look for: High Time To First Byte (TTFB) indicates slow server response likely due to DB operations.

Practice

1. What is the main purpose of using a test database in Flask testing?

easy

A. To store user sessions permanently

B. To isolate tests so they don't affect the real data

C. To speed up the app in production

D. To replace the main database in deployment

Solution

1. Step 1: Understand test database role

   A test database is used to keep test data separate from real data to avoid unwanted changes.

2. Step 2: Identify isolation benefit

   This isolation ensures tests do not affect the real app data or state.

3. Final Answer:

   To isolate tests so they don't affect the real data -> Option B

4. Quick Check:

   Test database isolates data = C [OK]

Hint: Test DB keeps test data separate from real data [OK]

Common Mistakes:

• Thinking test DB speeds up production
• Confusing test DB with session storage
• Assuming test DB replaces main DB in deployment

2. Which Flask testing method is used to prepare the test database before each test runs?

easy

A. tearDown

B. initTest

C. setUp

D. runTest

Solution

1. Step 1: Recall Flask test lifecycle methods

   In Flask testing, setUp runs before each test to prepare the environment.

2. Step 2: Match method to database preparation

   Preparing the test database (like creating tables) happens in setUp.

3. Final Answer:

   setUp -> Option C

4. Quick Check:

   Prepare DB before test = setUp [OK]

Hint: Use setUp to prepare before each test [OK]

Common Mistakes:

• Confusing tearDown with setup
• Using runTest which is not for setup
• Assuming initTest is a Flask method

3. Given this test code snippet, what will print(len(users)) output?

def test_user_creation(self):
    user = User(name='Anna')
    db.session.add(user)
    db.session.commit()
    users = User.query.all()
    print(len(users))

medium

A. 1

B. 0

C. Error: session not initialized

D. Multiple users depending on previous tests

Solution

1. Step 1: Analyze user addition and commit

   The code adds one user and commits to the test database.

2. Step 2: Query all users after commit

   Querying all users returns a list with the one added user.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   One user added and committed = 1 [OK]

Hint: Commit before query to see added users [OK]

Common Mistakes:

• Forgetting to commit before query
• Assuming previous tests add users
• Thinking session is not initialized

4. What is wrong with this test code snippet?

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

medium

A. Missing call to create_all() in tearDown

B. tearDown should not remove session

C. drop_all() should be in setUp, not tearDown

D. No call to rollback() before drop_all()

Solution

1. Step 1: Understand tearDown purpose

   tearDown cleans up after tests by removing session and dropping tables.

2. Step 2: Identify missing rollback before drop_all()

   Without rollback, pending changes may not be discarded, potentially causing errors or inconsistent state.

3. Final Answer:

   No call to rollback() before drop_all() -> Option D

4. Quick Check:

   Rollback before drop_all to discard changes [OK]

Hint: Always rollback before dropping tables in tearDown [OK]

Common Mistakes:

• Thinking create_all belongs in tearDown
• Believing session removal is wrong in tearDown
• Ignoring rollback before drop_all

5. You want to test a Flask app that uses a database. Which sequence correctly sets up and cleans the test database for each test?

hard

A. Call db.create_all() in setUp, run test, then db.drop_all() in tearDown

B. Call db.drop_all() in setUp, run test, then db.create_all() in tearDown

C. Call db.session.commit() in setUp, then db.session.remove() in tearDown

D. Call db.create_all() and db.drop_all() both in setUp

Solution

1. Step 1: Understand test setup and cleanup

   Creating tables before each test ensures a fresh database state.

2. Step 2: Understand test teardown

   Dropping tables after each test cleans up to avoid data carryover.

3. Step 3: Match correct sequence

   Calling create_all() in setUp and drop_all() in tearDown is the correct pattern.

4. Final Answer:

   Call db.create_all() in setUp, run test, then db.drop_all() in tearDown -> Option A

5. Quick Check:

   Create tables before, drop after test = A [OK]

Hint: Create tables before test, drop after test [OK]

Common Mistakes:

• Dropping tables before test instead of after
• Calling create_all and drop_all both in setUp
• Confusing commit with setup/teardown