7. Step 4: Convert Your Existing Test Cases Into Automation

This is probably the best strategy for manual testers.

Don’t create random automation projects.

Take the test cases you already understand.

For example:

Manual Test Case

Test Case: Verify successful login

Steps:

  1. Open application
  2. Enter valid username
  3. Enter valid password
  4. Click Login
  5. Verify dashboard

Now convert the same test case into automation.

Conceptually:

await page.goto("https://example.com");

await page.getByLabel("Username").fill("testuser");

await page.getByLabel("Password").fill("password");

await page.getByRole("button", { name: "Login" }).click();

await expect(page.getByText("Dashboard")).toBeVisible();

Notice something important.

You already knew the testing scenario.

You only learned how to express the scenario using code.

That’s the bridge between manual testing and automation testing.


8. Step 5: Start With Simple Scenarios

Don’t start with complicated automation frameworks.

Start with:

Day 1

Open browser.

Day 2

Navigate to website.

Day 3

Locate an element.

Day 4

Enter text.

Day 5

Click a button.

Day 6

Verify a message.

Day 7

Create a complete login test.

Small wins build confidence.

For example:

Open Application
       ↓
Find Element
       ↓
Perform Action
       ↓
Verify Result

Once you understand this flow, automation becomes much less scary.


9. Step 6: Learn Locators

Locators are one of the most important concepts in UI automation.

The automation tool needs to know:

“Which element should I interact with?”

For example:

<input id="username">

You may locate it using:

#username

Or using an accessible label, role, text, etc., depending on the tool.

With Playwright, for example:

page.getByLabel("Username")

The goal is simple:

Find the correct element → perform the required action.

As a manual tester, you already know which field or button you need.

Now you are learning how to identify it programmatically.


10. Step 7: Learn Assertions

Automation should not only perform actions.

It should also verify the result.

Suppose your test performs:

Enter username
Enter password
Click Login

How will automation know whether login succeeded?

You need an assertion.

For example:

await expect(page.getByText("Dashboard")).toBeVisible();

This means:

Verify that Dashboard is visible.

This is exactly the same concept as your manual expected result.

Manual testing

Expected: Dashboard should be displayed.

Automation

Assertion: Dashboard should be visible.

Again, your testing knowledge is already there.


Pages: 1 2 3 4 5 6

Leave a Reply

Your email address will not be published. Required fields are marked *