Skip to main content

Assignment of Menu and Submenu

Menu and Submenu Testing

 Manual test cases for the Menu and Submenu Testing applied specifically to the Features menu on the PHPTravels demo website     https://phptravels.com/demo/

Menu and Submenu Testing  

Test Case ID Test Scenario Test Steps Expected Result Status
TC_01 Verify navigation to the "Features" menu 1. Open the PHPTravels demo website
 2. Hover over the "Features" menu on the top navigation bar		 Submenu should appear, displaying various module options like "Car Modules"
TC_02 Verify hover state for "Features" menu 1. Open the website
 2. Move the mouse pointer over the "Features" menu		 The "Features" menu should visually indicate hover with a different style (color or background change)
TC_03 Verify navigation to "Car Modules" submenu 1. Hover over the "Features" menu
 2. Click on "Car Modules" submenu option		 The user should be redirected to the "Car Modules" page displaying module features
TC_04 Verify submenu accessibility from the menu 1. Open the website
 2. Try accessing submenus under the "Features" menu without hovering		 Submenus should not be accessible unless hovered or clicked
 

 


Comments

Post a Comment

Popular posts from this blog

Understand browser, context, and page in Playwright

🎥 Playwright: Browser, Context & Page - Real-time Demo and Multi-User Testing  . 🎯 Goal: Understand browser , context , and page in Playwright 🧠 1. What is a browser ? ✅ Definition: A browser in Playwright is a launched instance of a real browser (Chromium, Firefox, WebKit) that can be used for automated testing. ✅ Purpose: It starts and controls the browser process. It is the root of your test execution. Required to create contexts and pages . ✅ Code Example: ts Copy Edit import { chromium } from 'playwright' ; const browser = await chromium. launch ({ headless : false }); 🧠 2. What is a context (browser context)? ✅ Definition: A context is like a separate browser profile (or incognito tab) inside the browser. Each context is isolated — no cookies, local storage, or sessions are shared. ✅ Purpose: Simulates multiple users or sessions. Enables parallel and isolated testing. Allows setting user-specific prefer...
Post a Comment
Read more

How to Maximize a Browser window using Playwright Java

  Playwright itself does not have a direct maximize () method like some other browser automation tools, but you can achieve the effect by setting the viewport to the screen size of your display. Below are ways to handle Maximize a browser in Playwright Java  Ø   Setting the viewport to the screen size  o    setViewportSize(1920, 1080): This sets the browser window to a full HD resolution, effectively maximizing it. o    setHeadless(false): Ensures the browser runs in a visible mode so you can see the window being maximized.  Code Snapshot  Playwright playwright = Playwright. create ()   ;   Browser browser = playwright.chromium().launch(new BrowserType.LaunchOptions().setHeadless(false));     // Create a new browser context   BrowserContext context = browser.newContext(new Browser.NewContextOptions()          .setViewportSize(1920, 1080));     ...
Post a Comment
Read more

Playwright Locators in JavaScript (Complete Guide)

🎯 Playwright Locators in JavaScript (Complete Guide) This guide explains each Playwright locator with: ✅ What it is 🕐 When to use ⚙️ How to use it 🎯 Benefits 🧪 Code Examples 🔹 1. Locator by ID ✅ What: Selects an element with a unique id . 🕐 When: Element has a unique id . ⚙️ How: page.locator('#username') 🎯 Benefit: Fast and reliable. <input id="username" /> await page.locator('#username').fill('John'); 🔹 2. Locator by Class ✅ What: Selects by class . 🕐 When: Repeated or styled elements. ⚙️ How: page.locator('.password') 🎯 Benefit: Useful for shared styling. <input class="password" /> await page.locator('.password').fill('12345'); 🔹 3. Locator by Text ✅ What: Matches visible element text. 🕐 When: For buttons, links, etc. ⚙️ How: page.getByText('Login') 🎯 Benefit: Human-readable. <button>Login...
Post a Comment
Read more