,question,answer
0,Policy Search,Login to the application with valid credentials. Verify user is navigated to the search screen successfully. Enter the valid search criteria and click on search. Search results should be displayed on the screen successfully.
1,Policy Creation from Underwriting workbench,"On receiving the request from customers the insurance agent will mail the customer details to the FD. FD will update all the details in the admin system like insurer, reinsured, broker, coverage, LOB etc and submission id is generated out of it and is flown into the underwriting system. In Underwriting system the request review and risk assessment are done with the help of experienced risk engineers and the details are sent to admin system. Through admin system data is passed to costing system where premium calculation is carried out. Post premium calculation quote is generated and shared with the customer. Once customer acknowledges the quote the policy is generated and is in inforce. From document system policy document is generated and mailed to the customer."
2,Policy Decline from Insurer,If any fraudulent actions are verified by risk engineer then the submission id gets turned down in underwriting system. Equivalent policy in admin system also gets rejected.
3,Policy rejection from customer,"On receiving the request from customer the insurance agent will mail the customer details to the FD. FD will update all the details in the admin system like insurer, reinsured, broker, coverage, LOB etc and submission id is generated out of it and is flown into the underwriting system. In Underwriting system, the request review and risk assessment are done with the help of experienced risk engineers and the details are sent to admin system. In Underwriting system, the request review and risk assessment are done with the help of experienced risk engineers and the details are sent to admin system. Post premium calculation, quote is generated and shared with the customer. Customer might not accept the quote incase of various reasons i.e., Premium too high or insufficient cover etc. Then the policy is turned down and the closed policy document is shared with the customer."
4,Policy Creation,"Pre Requisites: Sufficient Access to the Application. Login to the application with valid credentials. Verify user is navigated to the application home page. Verify the fields are displayed as per the expected criteria. Verify user is able to edit the fields. Verify user is able to enter the Premium values for the Policy. Verify user is able to enter the required Share % for the Policy. Verify user is able to add corresponding Deductions to the Policy. Verify user is able to add corresponding taxes to the Policy. Verify user is able to select the Respective category required for the Policy. Verify user is able to select the applicable coverages required for the Policy. Verify the Premium Total is calculated by considering the Share , Deductions and Taxes. Verify the respective error messages for mandatory fields in case the user kept the fields blank. Verify the Policy."
5,Copy Policy,Verify user is navigated to the application home page. Open any existing policy. Verify if copy option is available for the user to copy the policy. Click on copy policy. Validation of popup message for confirmation. Validation of the fields getting copied to the policy.
6,Terror Policy,Login to the application with valid credentials. Verify user is navigated to the application home page. Open any existing policy. Verify if Terror option is available for the user. Click on terror line. Validation of popup message for confirmation. Validation of the fields getting copied to the policy.
7,Policy Cancellation,Pre Requisites: Sufficient Access to the Application. An Existing Policy should be available to make the cancellation. Open the Policy mentioned as per the Pre requisite 2. Verify the Policy is in Verified Status and user is not able to edit any changes. Verify the option for Policy Cancellation is present. Cancel the Policy by Providing the Cancellation Effective date and Cancellation Reason. Verify the Refund Premium calculation in case the Policy is cancelled before the End Date of the existing Policy and the Premium is paid. Verify the Premium Due calculation in case the Policy is cancelled after the End Date of the existing Policy and the Premium is due. Verify the Cancelled status is reflected in the Policy including the Premium Refund or Due status whichever is applicable.
8,Policy Deletion,Pre Requisites: Sufficient Access to the Application. An Existing Policy should be available to delete. Open the Policy mentioned as per the Pre requisite 2. Verify the option for Policy delete is present. Click on Delete option. Validation of popup message for confirmation. Verify the policy is deleted after clicking on OK.
9,Policy Endorsements,Pre Requisites: Sufficient Access to the Application. An Existing Policy should be available to make the changes. Open the Policy mentioned as per the Pre requisite 2. Verify the Policy is in Verified Status and user is not able to edit any changes. Verify the option for Policy Endorsement is Present. Endorse the Policy by making changes and Finish. Verify the changes are reflecting correctly in the Policy. Verify the Endorsement Status is reflected in the Policy.
10,Policy Renewal,Pre Requisites: Sufficient Access to the Application. An Expired Policy should be available to make the Renewal. Open the Policy mentioned as per the Pre requisite 2. Verify the Policy Status is expired. Verify the option for Policy Renewal is present. Renew the Policy by providing new Start date and End date. Verify the Premium Calculations are based on the new dates provided. Verify the Policy status is updated after Renewal.
11,Document Generation,Pre Requisites: Sufficient Access to the Application. Open a policy. Click on the document screen. Select the document to be generated. Click on generate button.
12,Document Validation,"Open the generated document either in word or PDF. Verify the document that to be in the format of specification document given by business. Validate the document for the static content. Validate the format, spacing, spelling, font size, data displayed to be correct as expected. Validate the dynamic data flown from policy. Verify the dynamic values entered is flown same into the document. If special characters, numbers, alphabets and email formats are given then also the document should the business standards."
13,Add Form,Open a package. Click on Add form button. Select the applicable form to be added. Click on add button.
14,Add Manuscript,Open a package. Click on Add manuscript button. Enter the description. Click on add button.
15,Upload attachment,Open a package. Click on upload attachment button. Enter the description value. Click on chose file and select file from local. Click on add.
16,Finalize Document,Open a package. Select all the forms. Click on generate. Click on merge. Click on finalize.
17,Deactivate Package,Open a package. Click on Deactivate package button. Select a reason and click on deactivate.
18,WCAG 1.1.1: Non text content should have a text alternative that serves the equivalent purpose.,"Open the web application in the browser. Check the web application for non-text content, such as images. Ensure each piece of non-text content has an associated text alternative. Verify Decorative Images."
19,"WCAG  1.2.1:For all pre-recorded audio-only and video-only content, provide a text transcript for audio-only presentations, and a text transcript or audio track for video-only presentations.",Launch the web application in the browser. Verify that captions and or text transcripts is available for audio only content of pre-recorded audio-only and video-only content. Verify that audio track is available for video only presentations.
20,WCAG 1.2.2:Provide captions for all pre-recorded media content.,"Open the application in the browser. Verify if the web application contains live or recorded video content, ensure this content is captioned."
21,"WCAG 1.2.4:Provide captions for all synchronized media containing live (real time) audio (e.g. teleconferences, gameplay). Synchronized media content that is also made available under general license to other companies (for example, television shows, sports events) is not covered by this requirement unless the content comes accompanied with captions under the terms of the license.","Launch the web application in the browser. Verify if the web application streams synchronized media containing live (real time) audio (e.g., live product announcements or teleconferences), Ensure that captions are available."
22,WCAG 1.2.5:Provide audio descriptions for all new pre-recorded media content.,"Open the web application in the browser. If the web application contains live or recorded video content, ensure video description/descriptive narration/audio tracks is available as an alternative."
23,"WCAG 1.3.1:Ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For any product, service, tool or content, functionality and navigation of the content and user interface (UI) components must be programmatically exposed and operable.","Open the web application in the browser. Ensure that any visual information on the page can be obtained through auditory means, or by reading the text present on the page. Ensure all audible information on the page is also available in a visual format. Verify if the web application contains tables, ensure all table row/column headers use the <th> tag. Row headers require the scope=""row"" attribute, and column headers require the scope=""col"" attribute. To verify table properties take help of JAWS and verify table specific keystrokes provided for screen reader."
24,WCAG 1.3.2:Ensure content is rendered in the proper order. ,"Open the web application in the browser. Check the web application for sections of content whose meaning is affected by the order materials are rendered in (i.e., a paragraph of text, a table or an ordered list). Use a screen reader  to navigate the page. Ensure that the order-dependent sections of data are presented in an order which does not change or confuse their meaning. (i.e., a table or numbered list which reads items out of order or a section of text which is interrupted by the screen reader reading unrelated content partway through)."
25,"WCAG 1.3.3:Ensure instructions do not rely solely on sensory characteristics.  Sensory characteristics include shape, location, size, orientation, and sound.","Open the web application in the browser. Verify any instructions presented in the web application do not rely solely on sensory characteristics, including sound and the shape, location, size, and orientation of objects. (i.e., do not  use phrases like 'click the link below' , or distinguish between two links by the shape of their graphics). Verify that text alternative should be provided to the element which convey information only through shape and layout. Ex: floppy icon used for save functionality does not provide complete information, text alternative such as 'Save' tool tip, or text embedded inside the floppy element would resolve the issue."
26,"WCAG 1.4.1:Do not use color in a way that requires the user to discriminate between hues as the only means to convey information, indicate an action, prompt a response, or distinguish a visual element.","Open the web application in the browser. Verify color is never used as the sole means to indicate an action, distinguish a page element or convey a piece of information. (i.e., do not use green and red text to indicate good vs. bad practices, or distinguish links from one another by color alone)."
27,"WCAG 1.4.2:When audio plays automatically (not initiated by the user) for more than 3 seconds, provide a way for users to pause or stop the audio, or to adjust the volume.","Open the web application in the browser. Check for audio elements that play for at least 3 seconds without user input. For each such element, Verify the user can pause/stop the video or adjust the volume. These controls must be reachable and usable via keyboard."
28,"WCAG 1.4.3:By default, visible text must have a minimum luminosity contrast ratio of 4.5:1 against the background.",Open the web application in the browser. Verify all small scale visible text (below 18 point regular/14 point bold) has a brightness ratio of at least 4.5:1 a with its background. Verify all large scale text (18 point/14 point bold) has a text/background brightness ratio of at least 3:1.
29,WCAG 1.4.4:Ensure text can be resized.,"Open the web application in the browser. Verify that text can be resized up to 200% of its default size without the use of assistive technology. Use Zoom option in IE browser settings/ can be done by Control ++ through keyboard. Verify resizing text does not interfere with the content visibility or functionality (i.e., elements enlarging so they overlap each other, elements getting pushed out of frame). Verify scrollbars are provided wherever text size is increased to accommodate zoom% and they are accessible through keyboard and also ensure focus indicator is also visible in increased zoom mode."
30,"WCAG 1.4.5:Ensure text is used instead of images of text when technology allows, unless it is essential. Logotypes (text that is part of a logo or brand name) are considered essential and thus can remain images.","Open the web application in the browser. Verify all text on the page is real text, as opposed to images of text. An exception can be made if an image of text is used in a logo or brand name. Verify any logo/brand name images of text have alt text which provides all information the image of text contains."
31,WCAG 2.1.2:Ensure that users can move focus out of a control by using a method consistent with the method used to move focus into the control. Ensure keyboard focus is not trapped.,"Verify the browser focus does not become trapped in any element or jump to unexpected page areas during this navigation. Try all the below before confirming it is a keyboard Trap Forward Navigation, Backward Navigation, Esc."
32,"WCAG 2.2.1:For any feature that requires users to complete an action within a set period of time, provide a way for people to disable or adjust the time limit (e.g., by increasing the time limit by a minimum of 10 times the default limit). Exceptions include activities where time limits are essential for security or real-time activities, such as gameplay or a live auction.","Open the web application in the browser. Check for elements that require the user to complete an action within a set time limit (i.e., an exam with a 2 hours time limit, or a script which logs users out after 5 idle minutes). Verify that the user can turn off the time limits or extend them to at least ten times their default duration. This includes the ability to extend duration mid activity. (i.e., a warning modal should appear if a secure session is nearing expiration, with a button that extends the session and closes the modal)."
33,"WCAG 2.2.2:Ensure that any auto updating content that starts automatically and is provided with other content provides a method for users to pause, stop, hide, or to control the frequency of the update.","Open the web application in the browser. Check for visual elements which update or refresh automatically without user input (i.e., auto scrolling carousels, auto play videos, chat windows which update when new messages come in). Verify that the user can stop or control update/refresh frequency with a pause button or similar control. These controls must be reachable and usable via keyboard."
34,"WCAG 2.3.1:Do not create hardware, content, products, services, or tools that are likely to cause seizures due to UI or content that flashes at a rate greater than 3 times per second.","Open the web application with a browser. Check the web application for videos or blinking/flashing content. Verify If any such content is found, use the Photosensitive Epilepsy Analysis Tool (PEAT) to ensure visual content blinks 3 or fewer times per second."
35,"WCAG 2.4.1:Expose visual groupings and the semantic structure of controls and content programmatically so that users can identify and navigate to, or through, them. Additionally, provide ways for users to activate, or navigate directly to, controls and content with as few interactions as possible (for example, they can bypass UI elements by using keyboard shortcuts or link to content links).",Open the web application in the browser. Identify repetitive elements on the page. Verify that user can bypass these repetitive blocks of content and controls using navigational elements.
36,"WCAG 2.4.2:Provide informative, context sensitive page title values. The title of a page or document must provide information specific to the currently viewed page or document.","Open the web application in the browser. Check these tags for each page, <title>Description of the page</title> OR Check the page title in the toolbar. Ensure the title adequately informs the user to what page they are visiting. Along with Page titles we also need to verify Alert/Dialog/Windows title as well iframes should also be verified for availability of name/title attribute with relative values."
37,"WCAG 2.4.3:Support a focus order that is aligned with the meaning or operation of the user interface (UI). If the navigation sequence is independent of meaning or operation, then align the focus order with the flow of the visual design.","Open the web application in the browser. Verify by pressing Tab repeatedly to move through the page interactive elements. Ensure all interactive elements (links and form fields)s receive Tab focus in a consistent, logical order (generally left to right, top to bottom). Verify non interactive elements (such as plain text) do not receive focus in this way."
38,"WCAG 2.4.4:Whenever possible, provide link text that identifies the purpose of the link without needing additional context.","Open the web application in the browser. Examine each link purpose (description) in the web application. Ensure each instance of link text (alt text, in the case of graphic links with no link text) identifies the purpose of the link without needing additional context. (Avoid link text such as See All, Click Here, Buy Now or Learn More)."
39,WCAG 2.4.5:Provide an opportunity to navigate in more than one manner.,"Open the web application in the browser. Verify the web application includes multiple elements which ease keyboard navigation through its pages and elements and also there are ways for users to activate, or navigate directly to, controls and content with as few interactions as possible. "
40,"WCAG 2.4.6:When headings and labels are used, they must describe the topic or purpose of the element or content that they pertain to.  Headings and labels must be unique unless there is sufficient context to allow users to differentiate between duplicated headings or labels. Ensure headings and labels are descriptive and unique.","Open the web application in the browser. Verify all headings contribute to a heading structure which forms a concise, hierarchical outline of the page contents. Avoid using headings to make text appear large or prominent (use CSS classes for presentational styling). Verify all headings and labels on the page are unique and accurately describe the content they pertain to."
41,"WCAG 2.4.7:Provide a visual focus indicator to ensure users can orient themselves and track their navigation through a task, scenario, or content.",Verify each focused item receives a dotted outline or other high contrast visible highlight to make it obvious where browser focus is. Verify Focus indicator is distinguishable by user.
42,"WCAG 3.1.1:Ensure that content developers provide information in the Web page that user agents need to present text and other linguistic content correctly. Additionally, expose the language for each passage or phrase that differs from the default language.","Open the web application in the browser. Access the web application source code.  (For web properties, right-click and select Inspect Source). For web properties, ensure the opening html tag includes a lang attribute matching its desired default language."
43,"WCAG 3.1.2:Ensure that user agents can correctly present content written in multiple languages. Additionally, expose the language for each passage or phrase that differs from the default language.",Open the web application in the browser. Verify if any localized language is used in web page that language element should have lang attribute with specific locale w.r.t that language.
44,WCAG 3.2.1:Avoid forced focus changes that are not initiated by the user. Ensure all focus changes that occur are a result of user action and that the user expects the change.,"Open the web application in the browser. For each interactive element, Verify that user can use the keyboard to navigate into it (usually with Tab and Shift+Tab), through all its contents (Tab and Shift+Tab or arrow keys), and out of it (Tab and Shift+Tab, Esc key). Ensure the web application does not refresh or open a new window as a result of this navigation."
45,"WCAG 3.2.2:Ensure that when a user enters data or information, there are predictable effects. Ensure an ATs default mode is not impacted.","Open the web application in the browser. Locate each element of the web application whose settings can be change or which can accept user input. Verify that setting changes to these elements do not automatic changes of context in the web application unless the user has been advised of the behavior before using the component in question. (i.e., the <label> element for a language selector drop-down should include the phrase Press up or down arrow to change page language)."
46,"WCAG 3.2.3:Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.","Open the web application in the browser. Check the web application for navigational components which recur across numerous pages/views of the web application. (i.e., a menu bar common to all pages in a site). Verify the contents of these components occur in the same order across all pages/views of the web application."
47,"WCAG 3.2.4:UI components that have the same functionality must visually appear, behave, and be identified programmatically in a consistent way within a product, service, or tool for a specific platform. Ensure consistent identification of functional components that appear repeatedly.","Open the web application in the browser. Identify each type of UI component present in the web application (i.e., links, buttons, text edit fields, combo boxes, etc.). Verify for each component, ensure all instances of that component look, function, and are programmatically identified in the same manner. (i.e., all links in a given page may be blue and have underline decoration, or all menus have the same styling and functionality.) Links, menus, menu items, buttons and plain text should all be styled to look different from one another."
48,"WCAG 3.3.1:If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. Make sure users are aware that an error has occurred and can determine what is wrong.","Open the web application in the browser. Check the web application for elements which include input validation. Verify each validation error message describes the error, tells the user where the error occurred ."
49,"WCAG 3.3.2: When user input is required, provide instructions or labels describing necessary input and expected data formats to prevent validation errors.  Simple instructions or cues for entering input must be provided.","Open the web application in the browser. Check for elements which require user input, such as form fields. Verify that each such field/element has text beside it or a <label> tag which conveys how to interact with the element. In the case of <label> tags, ensure that a for attribute is assigned with the correct ID of the form field in question. Labels is one way of mapping input field with its label."
50,WCAG 3.3.3:For all detected input errors after identifying the location where the error occurred and describing the error in text provide users with actionable suggestions for correcting it.,"Open the web application in the browser. Check the web application for elements which include input validation. Verify each validation error message describes the error, tells the user where the error occurred and offers a suggestion for fixing the error (i.e., Invalid email entered in the personal email field. Please check your email and try again)."
51,"WCAG 3.3.4:In services and applications, user input that results in a legal commitment, financial transaction or modification to user-controllable data in data storage systems must be able to be reversed, verified or confirmed.","Open the web application in the browser. Check the web application for input elements which can result in a legal commitment, financial transaction or modification of user controllable data in data storage systems. Ensure each element with this potential has a method for the user to  reverse, verify or confirm the change agreed to.  (i.e., a checkout verification page before a purchase is made on an ecommerce site or an unto option for changes just made to personal data)."
52,"WCAG 4.1.1:Ensure that user agents, including assistive technologies, can accurately interpret and parse content. For any product, service, tool or content, functionality and navigation of the content and user interface (UI) components must be programmatically exposed and operable.",Open the web application in the browser. Use a 3rd party screen reader to navigate the web application. Ensure every element on the page can be reached and parsed by the screen reader (all navigation must be possible via keyboard only).
53,"WCAG 4.1.2:Ensure that Assistive Technologies (AT) can gather information about, activate (or set) and keep up to date on the status of user interface controls in the content. For any product, service, tool or content, functionality and navigation of the content and user interface (UI) components must be programmatically exposed and operable.","Open the web application in the browser. Access the web application source code.  (For web properties, right-click and select Inspect Source). Verify each UI element has an accurate name and a role. For example, a Learn About WCAG link has the name Learn About WCAG and the role of  link. If want to change an element role, use the role attribute. For example, if a link is used as the root of a drop-down menu, you should give it role=menu. Verify that elements which have the potential for multiple states or values have these states/values defined. For example, a checkbox can have the checked or unchecked states, and the value of a text edit box is the text inside it. Ensure there are no duplicate attributes/duplicate id values for elements."
54,Verify the button functionality in Shipping method page.,Launch the URL. Login as a registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. Enter all the required details and click on Next:Payment. Reload the Shipping method page and Click on Back to Shipping Address.
55,To verify the Product details in Shipping Method as Registered user.,Launch the URL. Login as a registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. verify the location of the Product detail Table. verify whether the section is minimized or expanded. Click on the Product Name. Click on the Manufacturer Name. Hover on the information icon in Product detail table next to Product name. Verify the Unit Price Column. Verify the Quantity column. Try to edit the quantity. Verify the sub total column in Product detail table. verify the decimal values displayed. verify the schedules column. verify the shipping To section.
56,To verify the User Name and Shipping Address and Account information in Shipping Method as Registered user.,Launch the URL. Login as a Registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. verify the User name displayed. verify the Label in the page. verify the Account Information.
57,To verify the fields in Subtotal Section when coupon is/not applied in Shipping Method as Registered user.,Launch the URL. Register as a Registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. verify the location of the Subtotal section. verify the Header Line. verify the Line item subtotal. verify the Coupon Details. verify the Cart Subtotal. verify the Currency Converter. Select a Currency from the dropdown. verify the Tax and Shipping message.
58,Login,1. Verify the login functionality with valid login credentials. 2. Verify the Remember Me funtionality. 3.Verify the Session timeout. 4. Verify the logout functionality. 5.Verify the login functionality with Invalid User Name / Invalid password. 6. Verify the login functionality by leaving fields blank . 7. Verify the case sensitivity of User Name and Password fields.
59,Shopping Cart,1. Verify add to cart functionality by adding a profuct to the cart. 2. Verify add to cart functionality by adding multiple items to Cart. 3. Verify the View Cart button functionality. 4. Verify the update quantity functionality in Cart page. 5. Verfiy the remove product functionality in Cart page. 6. Verify the clear cart functionality in Cart Page. 7. Verify the total price calculated in the Cart Page
60,Shipping Address,"1. Verify if Shipping Address page has fields for name, address, city, state/province, zip/postal code, country, phone number, and optional fields like company name. 2. Verify if user is able to proceed to next step with valid address. 3. Verfiy the Edit Shipping address button functionality in Shipping Address page. 4. Verify if User is able to save Edited address. 5. Verify if User is able to cancel the editing shipping address. 6. Verify error messages by leaving all fields blank in Shipping Address page."
61,Shipping Method,1. Verify Shipping method options are displayed with corresponding costs and estimated delivery times. 2. Verify if user is able to select any shipping method and the cost is added to the total cost. 3. Verify is User is able to proceed to next page in checkout.
62,Payment,"1. Verify if Payment page has fields for entering payment information such as credit card number, expiration date, CVV, and billing address. 2. Verify if Credit card information is accepted without errors, and payment can proceed to confirmation. 3. Verify if User is redirected to PayPal, completes the transaction, and returns to the merchant's site with payment confirmed 4. Verify if Billing address fields validate correctly according to specified format and requirements (e.g., postal/ZIP code validation). 5. Verify if payment method is processed correctly, and payment information fields adjust accordingly. 6. Verify if Payment is processed successfully, and user is directed to the order confirmation page or receives a confirmation message."
63,Order Confirmation Page,"1. Verify if Order confirmation page loads correctly with details of the order, including order number, items purchased, shipping address, shipping method, and total amount paid. 2. Verify if Order number associated with the completed transaction is displayed prominently for user reference and tracking. 3. Verify if All items ordered are listed accurately, including quantities, prices, and any applicable discounts or promotions. 4. Verify if Shipping address matches the address provided during the checkout process, ensuring accurate delivery details 5. Verify if Selected shipping method is displayed correctly with associated costs and estimated delivery times. 6. Verify if Total amount paid matches the sum of item prices, shipping costs, and any applicable taxes or fees. 7. Verify if Order summary accurately reflects all financial aspects of the transaction, providing transparency to the user."
64,Search Results Page,"1. Verify if Search results page loads with relevant products, categories, or content matching the search query. 2. Verify if Results are relevant and accurate, matching the search query with appropriate products, categories, or content 3. Verify if Pagination controls (previous, next, page numbers) allow users to navigate through multiple pages of search results. 4. Verify if Search results reorganize according to the selected sorting criterion, displaying items in the desired order. 5. Verify if Search results update to reflect refined criteria, displaying only relevant items that match the applied filters. 6. Verify if Search results are cleared on clicking clear search, and the page returns to its default state, ready for a new search query."
65,Product Page,"1. Verify if Product page loads with complete details including product name, description, price, images, and specifications. 2. Verify if Product name and description accurately describe the features and benefits of the product. 3. Verify if Product images are clear, high-resolution, and accurately represent the product from different angles or perspectives. 4. Verify if Specifications such as dimensions, weight, materials, and other relevant details are clearly listed and accurate. 5. Verify if Product is successfully added to the shopping cart with default quantity on clicking Add to Cart button. 6. Verify if Product details and images update dynamically to reflect the selected variant. 7. Verify if Customer reviews and ratings are displayed accurately, providing insights into product quality and user satisfaction. 8. Verif if Navigation to related products or categories is smooth and intuitive, aiding user exploration and comparison"