CRUD operation verification in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if a new record was successfully created.

Testing Fundamentals

assert response.status_code == [1]

Drag options to blanks, or click blank then click option'

A201

B404

C400

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Using 200 instead of 201 for creation success.

Confusing 404 (Not Found) with success codes.

The HTTP status code 201 means the resource was successfully created.

2fill in blank

medium

Complete the code to verify that the update operation changed the record's name.

Testing Fundamentals

assert updated_record.[1] == 'New Name'

Drag options to blanks, or click blank then click option'

Aname

Bdate

Cstatus

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Checking the wrong attribute like 'id' or 'status'.

Not verifying the updated value.

We check the name attribute to confirm the update.

3fill in blank

hard

Fix the error in the code that verifies deletion by checking the record count.

Testing Fundamentals

assert len(records) [1] initial_count - 1

Drag options to blanks, or click blank then click option'

A<

B>

C==

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using < or > instead of ==.

Using != which allows wrong counts.

After deletion, the number of records should be exactly one less, so we use ==.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps user IDs to emails for active users only.

Testing Fundamentals

{user.[1]: user.[2] for user in users if user.active}

Drag options to blanks, or click blank then click option'

Aid

Bemail

Cname

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'name' or 'status' instead of 'email' for values.

Mixing keys and values.

The dictionary keys are user IDs and values are emails for active users.

5fill in blank

hard

Fill all three blanks to filter records with score above 50 and create a dictionary of names to scores.

Testing Fundamentals

result = {record.[1]: record.[2] for record in records if record.[3] > 50}

Drag options to blanks, or click blank then click option'

Aname

Bscore

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' instead of 'name' as keys.

Filtering on the wrong attribute.

We map names to scores and filter where score is greater than 50.

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