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
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

Step-by-Step: Launch Browser, Context, and Page in Playwright and Run Test and Configuration (JavaScript)

🎥 Setup Browser, Context, Page & Run Config Test Scripts with package.json & playwright.config.js Step-by-Step: Launch Browser, Context, and Page in Playwright and Run Test and Configuration (JavaScript) 1. Install Playwright You can install Playwright using the following command: npm init playwright@latest 2. Create a Basic Test Script Understand the core Playwright architecture: Element Description browser Controls the browser instance (like Chrome, Firefox, etc.) context Acts like a separate browser profile (cookies, localStorage are isolated) page A single browser tab where interaction happens 3. Run the Test npx playwright test example.spec.js Ways to Run TypeScript Tests Way Command Notes 🟢 Via npx npx playwright test Uses built-in TypeScript support 🟢 With s...

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...

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)); ...

QA Shastra Online Training

Search This Blog