Tmail web ‐ Step at homepage

I am on Twake Mail home page

When I am on Twake Mail home page

The purpose of this step is to:

• Log the action: Track that the test is navigating to the Twake Mail home page and logging that action.
• Navigate to the home page: Ensure the test navigates to the correct starting point (the Twake Mail home page).
• Verify page load: Check that a critical element (the search input field) is visible, confirming the page has loaded properly.

This step is particularly useful for scenarios where tests need to verify the correct loading and functionality of a web page before further interactions. It ensures the user is on the right page and can proceed with other actions in the test.

I see Search Input

(TBD)

I see Compose Button of Tmail Dashboard

Then I see Compose Button of Tmail Dashboard

The purpose of this step is to:

• Log the action: Track that the test is checking for the "Compose" button on the Tmail Dashboard.
• Locate the Compose button: Find the "Compose" button element on the page to ensure it exists.
• Verify the button is visible: Confirm that the "Compose" button is visible and interactable, ensuring the page is fully loaded.

This step is useful for validating that the essential elements of the Tmail Dashboard are present and visible before the user can interact with them. It's particularly important for scenarios where the "Compose" button must be clicked or interacted with in subsequent steps.

I see dialog {string} with content is {string}

Then I see dialog "Warning" with content is "Are you sure you want to delete this?"

The purpose of this step is to:

• Log the action: Track the verification of the dialog's title and content in the test report.
• Verify the dialog title: Ensure that the dialog title matches the expected value provided in the feature file.
• Verify the dialog content: Ensure that the dialog content/message matches the expected value provided in the feature file.

This step is particularly useful for validating dialogs or pop-ups in a web application to ensure they appear with the correct text before proceeding with further actions in the test.

I see dialog confirm button has text is {string}

Then I see dialog confirm button has text is "OK"

The purpose of this step is to:

• Log the action: Record the verification of the confirm button's text for transparency in the test report.
• Locate the confirm button: Find the button on the dialog to ensure it exists and can be interacted with.
• Verify the button text: Ensure that the text displayed on the confirm button matches the expected value.

This step is important for validating user interface elements, particularly when confirmation dialogs are involved. It ensures that the confirm button has the correct label before any further actions (such as clicking) are performed.

I see dialog cancel button has text is {string}

Then I see dialog cancel button has text is "Cancel"

The purpose of this step is to:

• Log the action: Record the verification of the cancel button’s text in the test report for transparency and tracking.
• Locate the cancel button: Find the button on the dialog to ensure it exists and can be interacted with.
• Verify the button text: Ensure that the text displayed on the cancel button matches the expected value provided in the feature file.

This step is important for validating the user interface elements of dialogs, particularly the cancel button, to ensure the dialog behaves as expected before any additional interactions or assertions are made.