Stored procedure testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to call the stored procedure named 'GetUserById' with parameter 5.

Testing Fundamentals

CALL GetUserById([1]);

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

A'5'

B5

CuserId

DNULL

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the parameter as a string with quotes.

Using a variable name instead of a value.

The stored procedure expects a numeric parameter, so passing 5 without quotes is correct.

2fill in blank

medium

Complete the code to create a stored procedure named 'AddProduct' that inserts a product with name parameter.

Testing Fundamentals

CREATE PROCEDURE AddProduct(IN productName VARCHAR(100)) BEGIN INSERT INTO products(name) VALUES([1]); END;

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

ANEW.productName

B'productName'

Cname

DproductName

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around the parameter name.

Using a column name instead of the parameter.

The parameter name 'productName' is used directly without quotes to insert the value.

3fill in blank

hard

Fix the error in the stored procedure call to 'UpdateStock' with productId and quantity parameters.

Testing Fundamentals

CALL UpdateStock([1], 10);

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

AproductId

B10

CNULL

D'productId'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the parameter as a quoted string.

Passing NULL instead of a valid value.

The parameter should be passed as a variable or value without quotes, so 'productId' as a string is incorrect.

4fill in blank

hard

Fill both blanks to declare and set an output parameter 'totalCount' in a stored procedure.

Testing Fundamentals

CREATE PROCEDURE CountUsers(OUT [1] INT) BEGIN SELECT COUNT(*) INTO [2] FROM users; END;

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

AtotalCount

BuserCount

DcountUsers

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the OUT parameter and the variable.

Forgetting to declare the OUT parameter.

The output parameter name must be the same in declaration and in the SELECT INTO statement.

5fill in blank

hard

Fill all three blanks to create a stored procedure 'DeleteUser' that deletes a user by id and returns success status.

Testing Fundamentals

CREATE PROCEDURE DeleteUser(IN [1] INT, OUT [2] BOOLEAN) BEGIN DELETE FROM users WHERE id = [3]; SET [2] = ROW_COUNT() > 0; END;

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

AuserId

Bsuccess

Ddeleted

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the input parameter and WHERE clause.

Not setting the output parameter correctly.

The input parameter and WHERE clause use 'userId'. The output parameter is 'success' to indicate if a row was deleted.

Practice

1. What is the main purpose of testing a stored procedure in a database?

easy

A. To verify that the procedure performs the expected operations correctly

B. To create new tables in the database

C. To delete all data from the database

D. To change the database schema automatically

Solution

1. Step 1: Understand stored procedure testing goal

   Testing stored procedures means checking if they do what they are supposed to do.

2. Step 2: Identify correct purpose

   Creating tables, deleting data, or changing schema are not testing goals but database operations.

3. Final Answer:

   To verify that the procedure performs the expected operations correctly -> Option A

4. Quick Check:

   Testing = Verify expected operations [OK]

Hint: Testing checks if procedure works as expected [OK]

Common Mistakes:

• Confusing testing with creating or deleting data
• Thinking testing changes database structure
• Assuming testing runs automatically without checks

2. Which SQL command is used to execute a stored procedure named GetUserData with an input parameter userId?

easy

A. EXECUTE GetUserData userId;

B. RUN PROCEDURE GetUserData userId;

C. START GetUserData(userId);

D. CALL GetUserData(userId);

Solution

1. Step 1: Recall correct syntax for calling stored procedures

   The standard SQL command to run a stored procedure is CALL procedure_name(parameters);

2. Step 2: Match syntax with options

   Only CALL GetUserData(userId); uses CALL with parentheses and parameter correctly.

3. Final Answer:

   CALL GetUserData(userId); -> Option D

4. Quick Check:

   CALL + procedure + (params) = correct call [OK]

Hint: Use CALL with parentheses to run procedures [OK]

Common Mistakes:

• Using EXECUTE without parentheses
• Using RUN PROCEDURE which is invalid syntax
• Forgetting parentheses around parameters

3. Consider this stored procedure call:
CALL CalculateDiscount(100, 0.1);
If the procedure returns the discounted price by subtracting the discount (price * rate), what is the expected output?

medium

A. 10

B. 110

C. 90

D. 100

Solution

1. Step 1: Understand inputs and calculation

   Price is 100, discount rate is 0.1 (10%). Discount amount = 100 * 0.1 = 10.

2. Step 2: Calculate discounted price

   Discounted price = 100 - 10 = 90.

3. Final Answer:

   90 -> Option C

4. Quick Check:

   100 - (100*0.1) = 90 [OK]

Hint: Subtract price * rate from price for discount [OK]

Common Mistakes:

• Adding instead of subtracting discount
• Using discount rate as final price
• Confusing discount amount with discounted price

4. You have this stored procedure call:
CALL UpdateUserEmail(123, '[e-mail]');
But it returns an error: ERROR: procedure UpdateUserEmail does not exist.
What is the most likely cause?

medium

A. The procedure name is misspelled or does not exist

B. The email format is invalid

C. The user ID 123 does not exist

D. The database connection is lost

Solution

1. Step 1: Analyze error message

   The error says the procedure does not exist, which means the database cannot find a procedure named UpdateUserEmail.

2. Step 2: Identify likely cause

   This usually happens if the procedure name is wrong or it was not created.

3. Final Answer:

   The procedure name is misspelled or does not exist -> Option A

4. Quick Check:

   Error about procedure existence = name or creation issue [OK]

Hint: Check procedure name spelling and existence first [OK]

Common Mistakes:

• Assuming input data causes procedure not found error
• Blaming connection issues without checking procedure
• Ignoring error message details

5. You want to test a stored procedure CalculateTax that takes an income amount and returns tax owed.
The procedure has a bug: it returns NULL for zero income instead of 0.
Which test case will best detect this bug?

hard

A. Call CalculateTax(1000) and check if result is positive

B. Call CalculateTax(0) and check if result is 0

C. Call CalculateTax(-100) and check for error

D. Call CalculateTax(NULL) and check for NULL

Solution

1. Step 1: Understand the bug

   The procedure returns NULL instead of 0 when income is zero.

2. Step 2: Choose test case to detect bug

   Testing with zero income and expecting 0 will reveal if NULL is returned incorrectly.

3. Final Answer:

   Call CalculateTax(0) and check if result is 0 -> Option B

4. Quick Check:

   Test zero input to catch NULL instead of 0 bug [OK]

Hint: Test edge inputs like zero to find null bugs [OK]

Common Mistakes:

• Testing only positive values misses zero case
• Testing negative income when not required
• Assuming NULL input tests zero income bug