Skip to content

Part 3: Verification and Cleanup

In this part, you'll verify that the features added in Part 2 work correctly together, and then clean up the hands-on environment.

Goals of This Part

  • Test the added features
  • Clean up the hands-on environment

Step 1: Test the Added Features

Practice: Let's test the added features

Test the features added in Part 2 without repeating the same verification point.

If testing was already completed in Part 2

During Part 2, IBM Bob may automatically create test scripts and complete the tests after you click the run button. Even in that case, use this step to double-check that the added features work as expected.

Test viewpoints

On the search screen, one search shows all added fields on each product card. Therefore, this section separates testing into response field verification and price filter behavior verification.

Test 1: Overall Response Field Verification

Procedure

  1. Open the search screen (http://localhost:8002)

  2. Search for:

    red sneakers

  3. Verify the product cards

Verification Points

  • A product image is displayed on each card (image_url)
  • A recommendation reason is displayed in clear language (recommendation_reason)
  • The existing product name, price, category, description, and similarity are still displayed

Test 2: Price Filter Behavior Verification

Procedure

  1. On the search screen, enter 50 as the minimum price and 100 as the maximum price

  2. Search for:

    sneakers

  3. Verify results: All product prices are within the 50-100 dollar range

Verification Points

  • Only products within the specified price range are displayed
  • Products outside the range are not displayed
  • Product images and recommendation reasons are still displayed

Optional: Try Various Price Ranges

Search query Minimum price Maximum price
camera 500 1000
camera 0 200

Test Completion Check

  • Verified product images and recommendation reasons in one search
  • Verified that the price filter excludes products outside the range
  • Verified that the added features work correctly together

Step 2: Environment Cleanup

Practice: Clean up the virtual environment

Deactivate the virtual environment used in the hands-on and delete the hands-on folder.

Purpose of Cleanup

In this hands-on, you worked inside the vector-search-builder-en folder on your desktop. When you finish working, first deactivate the virtual environment. Then delete the vector-search-builder-en folder from your desktop to remove the hands-on files, project-local venv, and configuration files together.

Request IBM Bob to Clean Up

Enter the following in IBM Bob's chat input field:

Delete this workspace.

If IBM Bob asks you to confirm the deletion, choose to delete the folder. If IBM Bob shows the commands instead of running them, run them yourself as in "If cleaning up manually" below.

How cleanup works

deactivate only exits the virtual environment in the current terminal. Deleting the vector-search-builder-en folder afterwards also removes the project-local venv and configuration files.

If cleaning up manually

Execute the following in the terminal:

deactivate
cd ~/Desktop
rm -rf vector-search-builder-en

deactivate
cd %USERPROFILE%\Desktop
rmdir /s /q vector-search-builder-en
If deleting only venv

Usually, deleting the entire vector-search-builder-en folder is enough. If you want to keep the project files and remove only the virtual environment, execute the following:

deactivate
cd ~/Desktop/vector-search-builder-en/setup/participant
rm -rf venv

deactivate
cd %USERPROFILE%\Desktop\vector-search-builder-en\setup\participant
rmdir /s /q venv
What if I want to keep the venv?

If you plan to use the technologies learned in this hands-on in the future, you don't need to delete the venv folder. Just run deactivate and reuse it later.

Cleanup Completion Check

  • Deactivated the virtual environment
  • Deleted the vector-search-builder-en folder

Part 3 Completion Check

  • Tested the features added in Part 2 using non-overlapping verification points

FAQ

Test fails
  1. Verify application is running
  2. Verify changes are saved

  3. Restart the application manually

    1. Press Ctrl+C in the terminal running the application (stop)
    2. Start the application ( How to start)

Next →