CRUD operation verification in Testing Fundamentals - Full Explanation

Introduction

When building software that stores and manages data, it is crucial to make sure that creating, reading, updating, and deleting data works correctly. Without verifying these actions, the software might lose or corrupt important information, causing problems for users.

Explanation

Create Operation Verification

This step checks if new data can be added successfully to the system. It involves confirming that the data is stored exactly as intended and that no errors occur during the creation process.

Ensuring new data is correctly saved is the first step in CRUD verification.

Read Operation Verification

This step ensures that stored data can be retrieved accurately. It tests if the system returns the correct data when requested, reflecting any recent changes or additions.

Accurate retrieval of data confirms the system's ability to provide up-to-date information.

Update Operation Verification

This step verifies that existing data can be changed as expected. It checks that updates are saved properly and that the modified data replaces the old data without errors.

Verifying updates ensures data remains current and correct after changes.

Delete Operation Verification

This step confirms that data can be removed from the system when no longer needed. It tests that deleted data is no longer accessible and that the deletion does not affect other data.

Proper deletion prevents unwanted data from lingering and keeps the system clean.

Real World Analogy

Imagine managing a personal library. You add new books to your shelf (create), look for a book to read (read), replace a damaged book with a new edition (update), and remove books you no longer want (delete). Checking each step ensures your library stays organized and useful.

Create Operation Verification → Adding a new book to your shelf and making sure it is placed correctly

Read Operation Verification → Finding and reading the correct book from your shelf

Update Operation Verification → Replacing an old book with a new edition on your shelf

Delete Operation Verification → Removing a book you no longer want from your shelf

Diagram

Diagram

┌─────────┐    ┌─────────┐    ┌─────────┐    ┌─────────┐
│ Create  │ → │ Read    │ → │ Update  │ → │ Delete  │
└─────────┘    └─────────┘    └─────────┘    └─────────┘

This diagram shows the four CRUD operations in sequence, representing the flow of data management.

Key Facts

Create → Adding new data to a system.

Read → Retrieving existing data from a system.

Update → Modifying existing data in a system.

Delete → Removing data from a system.

Verification → Testing to confirm that operations work as expected.

Code Example

Testing Fundamentals

import unittest

class TestCRUDOperations(unittest.TestCase):
    def setUp(self):
        self.data_store = {}

    def test_create(self):
        self.data_store['item1'] = 'value1'
        self.assertIn('item1', self.data_store)

    def test_read(self):
        self.data_store['item2'] = 'value2'
        self.assertEqual(self.data_store.get('item2'), 'value2')

    def test_update(self):
        self.data_store['item3'] = 'old_value'
        self.data_store['item3'] = 'new_value'
        self.assertEqual(self.data_store['item3'], 'new_value')

    def test_delete(self):
        self.data_store['item4'] = 'value4'
        del self.data_store['item4']
        self.assertNotIn('item4', self.data_store)

if __name__ == '__main__':
    unittest.main()

Common Confusions

Believing that verifying one CRUD operation is enough to ensure data integrity.

Believing that verifying one CRUD operation is enough to ensure data integrity. Each CRUD operation affects data differently and must be tested separately to guarantee full data integrity.

Assuming that if data can be created, it can automatically be read or updated correctly.

Assuming that if data can be created, it can automatically be read or updated correctly. Create, read, update, and delete are independent operations; success in one does not guarantee success in others.

Summary

CRUD operation verification ensures that creating, reading, updating, and deleting data all work correctly and independently.

Each operation must be tested separately to maintain data accuracy and system reliability.

Testing CRUD operations helps prevent data loss, errors, and inconsistencies in software applications.

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