Explore

Evaluation

FTTEM01S1_2510

Task 1: Create a Mindmap for Testing Types

Task:

Use MindMeister, Draw.io, Lucidchart, or a hand-drawn sketch to create a mindmap covering:

Functional Testing (Unit, Integration, System, Acceptance)

Non-Functional Testing (Performance, Security, Usability)

Automated vs. Manual Testing

Submission Guidelines: Export the mindmap as a PNG, PDF, or JPG file.

Task 2: Test Plan

Scenario:

You are a Software Test Engineer working on an e-commerce website that allows users to browse products, add them to the cart, make payments, and track their orders.

Website for Reference (For Testing Scope & Functionalities):

👉

Automation Exercise – E-Commerce Site⁠

⁠

Task:

Develop a Comprehensive Test Plan that includes the following sections:

Test Plan Identifier: Assign a unique ID to the test plan.

Introduction: Provide an overview of the e-commerce application and the scope of testing.

Test Objectives: Define the purpose of testing and key testing goals.

Scope of Testing: Specify features to be tested (e.g., login, product search, checkout) and features NOT to be tested.

Test Strategy:

Identify SDLC & STLC model used.

Define the levels of testing (Unit, Integration, System, Acceptance).

Identify the types of testing (Functional, Non-Functional, Security, Regression, Smoke, Sanity).

Test Automation Strategy (if applicable): Specify which tests will be automated (e.g., login functionality, checkout process).

Exit Criteria: Define conditions for stopping testing.

Submission Guidelines: Submit a well-structured test plan document in DOCX or PDF format.

Task 3: Build a Responsive Web Form

Scenario: You need to create a User Registration Form.

Task:

Implement an HTML form with fields for:

Full Name

Password

Gender (Radio buttons)

Submit Button

Apply CSS styling for:

Proper alignment

Responsive design

Basic form validation (e.g., required fields)

Task 4: Create a Responsive Grid Layout Using CSS

Scenario: Design a three-section webpage layout.

Task:

Implement HTML & CSS for a responsive layout using CSS Grid/Flexbox with:

A header (full width)

A sidebar (30% width)

A main content area (remaining width)

A footer (full width)

Ensure it is responsive on mobile and desktop screens.

⁠

FTTEM02S2_2510

Task 1: Validate Login Page Elements Using Cypress Assertions

Scenario:

You are testing the login functionality of an application. You need to verify that the login page has the correct elements and error messages using Cypress assertions.

Website for Testing:

👉

Practice Test Automation – Login⁠

⁠

Your Task:

Write a Cypress test script that:

Visits the login page.

Validates that username & password fields exist (.should('exist')).

Verifies the placeholder text (.should('have.attr', 'placeholder', 'Enter your username')).

Checks that the login button is visible and enabled (.should('be.visible').should('not.be.disabled')).

Extend the test to:

Enter wrong credentials, submit, and verify the error message.

Validate that the error message matches expected text (.should('have.text', 'Invalid Username or Password')).

⁠

Task 2: Explicit Assertions for Contact Form Submission

Scenario:

You need to test the contact form submission on a web application and validate the form responses using explicit assertions.

Website for Testing:

👉

Practice Test Automation – Contact Form⁠

⁠

Your Task:

Create a Cypress test script that:

Fills in the Name, Email, and Message fields.

Clicks the Submit button.

Captures the success message and asserts its text and visibility.

Use explicit assertions (expect()) to:

Validate that the form is cleared after submission.

Ensure the message contains the expected confirmation text.

⁠

Task 3: Validate Dynamic Elements and Visibility

Scenario:

You need to verify visibility changes of elements on a webpage when triggered by a user action.

Website for Testing:

👉

Automation Practice – Visibility Test⁠

⁠

Your Task:

Create a Cypress test script that:

Visits the webpage and checks if a hidden element exists but is not visible (.should('exist').should('not.be.visible')).

Clicks a button that makes the hidden element appear.

Asserts that the element becomes visible (.should('be.visible')).

Bonus: Add a test that waits for an element to disappear and asserts it is removed.

⁠

Task 4: Validate Checkbox, Dropdown, and Radio Button Interactions

Scenario:

You need to verify the functionality of checkboxes, dropdowns, and radio buttons in a form.

Website for Testing:

👉

Practice Automation – Form Testing⁠

⁠

Your Task:

Write a Cypress test script that:

Checks a checkbox and verifies it is selected (.should('be.checked')).

Unchecks the checkbox and ensures it is not checked.

Selects an option from a dropdown and validates the selection (.should('have.value', 'Option 2')).

Clicks a radio button and ensures it is selected.

⁠

Task 5: Extract and Validate Text from Web Elements

Scenario:

You need to extract and validate text dynamically displayed on a webpage.

Website for Testing:

👉

Ultimate QA – Web Elements for Automation⁠

⁠

Your Task:

Create a Cypress test script that:

Extracts text from a paragraph (.invoke('text')).

Uses .should('have.text', 'Expected Text') to validate it.

Uses .include('Expected') for partial text validation.

Compare Cypress commands (cy.get()) with jQuery methods (.text()).

⁠

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.