Why CRUD operation verification in Testing Fundamentals? - Purpose & Use Cases

The Big Idea

What if your app's core data actions break and you don't notice until users complain?

The Scenario

Imagine you have a simple app where users can add, view, update, and delete their contacts. You try to check each action by clicking buttons and typing data yourself every time you want to test if it works.

The Problem

Doing this by hand is slow and tiring. You might miss a step or forget to check if the data really changed. It's easy to make mistakes and hard to repeat the same checks exactly the same way every time.

The Solution

CRUD operation verification automates these checks. It runs tests that create, read, update, and delete data automatically, then confirms the app behaves correctly. This saves time and catches errors you might miss by hand.

Before vs After

✗ Before

Click 'Add', type name, save, then check if name appears.

✓ After

assert createUser('Alice') == 'success'
assert readUser('Alice').name == 'Alice'
assert updateUser('Alice', 'Alicia') == 'success'
assert deleteUser('Alicia') == 'success'

What It Enables

It lets you trust your app's basic data actions work perfectly every time, even after changes.

Real Life Example

When a bank updates its app, automated CRUD tests check that customers can still add new payees, view account details, change contact info, and remove old accounts without errors.

Key Takeaways

Manual testing of CRUD is slow and error-prone.

Automated verification runs reliable checks fast.

This builds confidence that data actions always work.

Practice

1. Which CRUD operation is responsible for adding new data to a system?

easy

A. Delete

B. Read

C. Update

D. Create

Solution

1. Step 1: Understand CRUD operations

   CRUD stands for Create, Read, Update, and Delete, each representing a basic data operation.

2. Step 2: Identify the operation for adding data

   The 'Create' operation is used to add new data entries into the system.

3. Final Answer:

   Create -> Option D

4. Quick Check:

   Adding new data = Create [OK]

Hint: Create means add new data to the system [OK]

Common Mistakes:

• Confusing 'Create' with 'Update'
• Thinking 'Read' adds data
• Mixing 'Delete' with adding data

2. Which of the following is the correct syntax to verify a Delete operation in a test case?

easy

A. assert data.exists() == True

B. assert data.is_deleted() == True

C. assert data.count() > 0

D. assert data.is_present() == True

Solution

1. Step 1: Understand Delete verification

   To verify deletion, the test must confirm the data no longer exists or is marked deleted.

2. Step 2: Choose assertion that confirms deletion

   assert data.is_deleted() == True correctly checks that the data was deleted.

3. Final Answer:

   assert data.is_deleted() == True -> Option B

4. Quick Check:

   Delete check uses is_deleted() == True [OK]

Hint: Check deletion with is_deleted() == True [OK]

Common Mistakes:

• Using exists() == True after deletion
• Checking count() > 0 which means data exists
• Confusing is_present() with deletion status

3. Consider this test code snippet verifying an Update operation:

original_value = record.get('name')
record.update({'name': 'Alice'})
updated_value = record.get('name')
assert updated_value == 'Alice'

What will be the result of this test if the update works correctly?

medium

A. Test passes because updated_value matches 'Alice'

B. Test fails because original_value is not checked

C. Test fails due to syntax error in update method

D. Test passes but updated_value remains original_value

Solution

1. Step 1: Analyze the update operation

   The code updates the 'name' field to 'Alice' and retrieves it again.

2. Step 2: Check the assertion logic

   The assertion checks if updated_value equals 'Alice', which should be true if update works.

3. Final Answer:

   Test passes because updated_value matches 'Alice' -> Option A

4. Quick Check:

   Updated value == 'Alice' means test passes [OK]

Hint: Assert updated value equals new data after update [OK]

Common Mistakes:

• Assuming original_value must be checked in this test
• Thinking update method has syntax error
• Believing updated_value stays unchanged after update

4. A tester wrote this code to verify a Create operation:

new_record = db.create({'id': 1, 'value': 100})
assert new_record.id == 1
assert new_record.value == 100
assert db.find(1) == None

What is the error in this test?

medium

A. The assertion db.find(1) == None is incorrect after creation

B. The new_record object does not have id attribute

C. The create method should not return a record

D. The value 100 is not valid for creation

Solution

1. Step 1: Understand Create operation verification

   After creating a record, it should be found in the database.

2. Step 2: Analyze the assertion db.find(1) == None

   This assertion expects no record found, which contradicts the creation.

3. Final Answer:

   The assertion db.find(1) == None is incorrect after creation -> Option A

4. Quick Check:

   Created record must be found, so find(1) != None [OK]

Hint: After create, find should return the record, not None [OK]

Common Mistakes:

• Expecting find to return None after creation
• Assuming create returns nothing
• Confusing attribute existence on new_record

5. You want to verify all CRUD operations on a user profile. Which sequence of test steps is best to ensure data integrity?

hard

A. Create user, Update user, Delete user, Read user

B. Read user, Create user, Update user, Delete user

C. Create user, Read user, Update user, Delete user

D. Delete user, Create user, Read user, Update user

Solution

1. Step 1: Understand logical CRUD test order

   First, create data to have something to work with, then read to verify creation.

2. Step 2: Follow with update and delete

   Update tests changes, and delete confirms removal, maintaining data integrity.

3. Final Answer:

   Create user, Read user, Update user, Delete user -> Option C

4. Quick Check:

   CRUD order: Create, Read, Update, Delete [OK]

Hint: Test CRUD in order: Create, Read, Update, Delete [OK]

Common Mistakes:

• Deleting before creating data
• Reading before data exists
• Updating before creation