Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
I am writing a script in Selenium and TestNG to automate Add User profile pages.
Now, when I land on every new page, then do I need to write Assert.equals("add user profile", driver.gettitle()); on every page. Is it a bad design if I don't do this?
Have one test that you have reached the correct page.
Other tests should navigate to the page and then perform additional actions which are tested. If navigating to the page actually fails the tests that do that in order to reach their pages or elements will fail.
Ideally whatever pre-conditions are required are set up in the test itself to avoid needing to navigate and perform other actions to set up the test. However this kind of setup ('grey box testing') is usually much harder than just navigating to the page and takes a much more mature testing model
Another example is authentication. Hundreds of tests may require authentication, but if auth fails you don't want to have hundreds of failures. This is usualky the place when grey box testing starts, for example coming up witha method to provide an dummy auth token that can be used for the test.
I think the right way is to create a constructor which verifies page title automatically on each page object initiation.
This approach will be DRY as you will be creating constructor function in base class only once therefore you don't need a separate function in each page object class to verify title and page load .
