Ui Testing
In this lesson, we'll explore how to test the published event search functionality through the user interface.
Testing through the UI provides a practical way to validate that our search feature works as expected from the user's perspective.
Manual UI Testing
The search functionality allows users to find published events by matching text in the event details.
Let's walk through the testing process:
- First, ensure your application is running by executing a clean compile:
./mvnw clean compile-
Navigate to your frontend application where you should see the published events displayed (in this case, "Test Event Three" and "Test Event Four").
-
To properly test and monitor the search functionality, open your browser's developer tools (F12 in most browsers) and select the Network tab.
Testing Search Scenarios
Let's test different search scenarios to verify the functionality:
- Basic Search Test:
- Enter "test" in the search field
- Click search
- Verify both events are returned
- Check the network tab shows a 200 status code
- Specific Event Search:
- Enter "test event three"
- Verify only "Test Event Three" is displayed
- Enter "test event four"
- Verify only "Test Event Four" is displayed
- Venue Details Search:
- Enter "details" in the search field
- Verify only events containing "details" in their venue information are displayed
- Empty Search:
- Clear the search field
- Click search
- Verify all published events are displayed
When testing through the UI, pay attention to:
- The immediate response of the interface
- The network requests being made
- The accuracy of the returned results
- The handling of different search terms
Summary
- Tested the search event functionality using the user interface
