© 2026 Hashnode
Welcome back to the fourth installment of our Selenium Framework Design! So far we have built a standalone Selenium test for an e-commerce application, adopted the Page Object Model (POM), introduced a BaseTest class, TestNG for test management, and ...

Welcome back to the second part of our Selenium Framework Design! In Part 1, we set up a Maven project, added dependencies, and created a standalone Selenium test to automate an end-to-end e-commerce flow. Now, in Part 2, we’ll take that test and tra...

When working with a website, you'll often come across multiple pages—like a home page, login page, product page and checkout page. Now, imagine trying to write all your automated test scripts for these pages in one big file. It can quickly become ove...

When automating web testing, it's not just about finding elements on a page — it's about interacting with them and verifying that they behave as expected. In this blog, we’ll explore how Playwright helps you handle user interactions and assert condit...

Introduction This article explains a nice way to make Page Object more meaningful and to reduce code duplication to validate the page load behaviour.I would recommend first reading about the Page Object Model in Test automation if you are not familia...

In this article, we'll discuss the advantages of using the Page Object Model (POM) for automated testing with Selenium, Java, and JUnit 5. First, we'll explain what POM is and then try writing tests without it. During this process, we'll note any dif...
