0% found this document useful (0 votes)
20 views4 pages

Test Case Document For The Web Service Registry Platform Use Case

The document outlines test cases for a Web Service Registry Platform, detailing features such as registering new services, searching for services, updating service status, and validating service metadata. Each test case includes steps to execute, expected and actual outputs, and the status of the test. The results indicate that all test cases passed, confirming the functionality of the platform.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views4 pages

Test Case Document For The Web Service Registry Platform Use Case

The document outlines test cases for a Web Service Registry Platform, detailing features such as registering new services, searching for services, updating service status, and validating service metadata. Each test case includes steps to execute, expected and actual outputs, and the status of the test. The results indicate that all test cases passed, confirming the functionality of the platform.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Test Case Document for Web Service Registry Platform

Feature Test Case Steps to Execute Test Case Expected Output Actual Output Status More Information
Feature #1: Register New 1. Log in as a researcher or Service should be registered and Service is registered Pass Ensure all metadata
Create a Web Service administrator. visible in the web service correctly and visible with (name, description, API
Registry of 2. Navigate to the "Register registry with the entered all metadata on the "Web link, etc.) are correctly
Active Web Web Service" page. metadata (name, description, Services" page. displayed.
Services 3. Fill in the service name, API link, category, and tags).
description, API
documentation link, category,
and tags.
4. Click "Submit".
Feature #2: Search for 1. Log in as any user A list of relevant web services is Relevant web services Pass Verify search results
Service Web Services (researcher, developer, displayed based on the search appear, filtered based on are filtered based on
Discovery & business analyst). term, including metadata like search term, and metadata tags, description, and
Search 2. Navigate to the search bar. name, description, API link, etc. displayed. keywords.
3. Enter a search term (e.g.,
"machine learning", "AI").
4. Click "Search".
Feature #3: Update Web 1. Log in as a researcher or Service status is updated Service status updated to Pass Verify that service
Service Service Status administrator. correctly, and the status change "Under Maintenance" status updates are
Status 2. Navigate to an existing is reflected in the registry (e.g., successfully. reflected immediately
Tracking service in the registry. Active -> Under Maintenance). and can be filtered by
3. Click "Edit" on the service. status.
4. Change the status to
"Under Maintenance" or
"Deprecated".
5. Save changes.
Feature #2: Filter Web 1. Log in as a user. Only web services in the "Data Web services in the "Data Pass Ensure that the filter
Service Services by 2. Navigate to the service Analytics" category should be Analytics" category are functionality is applied
Discovery & Category registry. shown in the search results. correctly displayed. correctly and is
Search 3. Apply a filter, such as "Data intuitive.
Analytics".
4. Review the search results
based on the applied
category.
Feature #1: Validate 1. Log in as a researcher or All metadata fields must be All required fields (e.g., Pass Verify the validation of
Create a Service administrator. mandatory and validated before name, description) are mandatory fields.
Registry of Metadata 2. Register a new web service. the service can be submitted. validated, and an error is
Active Web Fields 3. Ensure all metadata fields thrown for missing fields.
Services (name, description, API
documentation link, category,
tags) are filled out.4. Submit
the service.
Feature #3: View Service 1. Log in as a user. Service status (e.g., Active) Service status (Active, Pass Ensure that status is
Service Status in 2. Navigate to the service should be clearly displayed in Deprecated) is visible on prominently displayed.
Status Details details page. the service details. the details page.
Tracking 3. Select a service.
4. Check the current status of
the service (Active,
Deprecated, or Under
Maintenance).
Feature #2: Search by Tag 1. Log in as a user. The system returns services Services tagged with "AI" Pass Verify tag-based search
Service (e.g., "AI") 2. Navigate to the search tagged with "AI" and displays appear in search results. functionality.
Discovery & page. metadata like service name and
Search 3. Enter a tag keyword, such description.
as "AI"
.4. Click "Search".
Feature #1: Service 1. Log in as a researcher or The system should display an Error message shown for Pass Verify validation for
Create a Registration administrator. error message indicating the missing/invalid data (e.g., invalid data inputs.
Registry of with Invalid 2. Attempt to register a new invalid data. missing API link).
Active Web Data service with invalid data (e.g.,
Services missing API link, invalid tags).
Feature #1: Register 1. Log in as a researcher or The system should detect the Duplicate registration is Pass Verify that the system
Create a Duplicate Web administrator. duplicate and prevent prevented, and an error correctly handles
Registry of Service 2. Attempt to register a web registration. message is shown. duplicates.
Active Web service that already exists
Services (same name, same API link).
Test Case Execution Explanation:

1. Feature: Describes the functionality being tested (e.g., service registration, service discovery, etc.).

2. Test Case: Provides a specific test scenario that checks the functionality.

3. Steps to Execute Test Case: Lists the exact steps to be taken in order to execute the test case.

4. Expected Output: Defines the expected outcome from executing the test case.

5. Actual Output: Describes what actually happened when the test was executed. This field is filled in during testing.

6. Status: Indicates whether the test passed or failed. Typically, this will be filled out during testing and can be marked as:

o Pass: If the system behaves as expected.


o Fail: If the system does not behave as expected.

7. More Information: Additional comments or notes that may be relevant (e.g., known issues, test environment specifics).
Result analysis (EXAMPLE)

The experimental results of the proposed Hybrid framework for web services discovery are shown in Figure 1. Based on the user's query, it
recommends services with minimal response time and high ratings to the user.

Results obtained from Hybrid framework (QoS Results obtained from Hybrid framework (QoS
&QoE) for E-Book services &QoE) for weather services

475
375
425

Response Time(ms)
325
Response Time(ms)

375
275
325
275 225

225 175

175
125
125
75
75
25
25
Weather 5 Weather 2 Weather 4 Weather 1
E_book 1 E_book 3 E_book 4
Re- 158.4 294.7 431.6 Re- 119 129 310.1 342.8
spon
sponse se
time( time(
ms) ms)
ser- 3 3 3 2
service 3 2 2 vice
rat- rat-
ings(1- ings(
1-5)
5)

Figure 1 Results obtained from the Hybrid framework for various services

You might also like