Introducing Navigation API for WebDriver tests

If you are working with selenium then probably you have used Page Object to make your tests more maintainable. In a gist, Page Object extracts the business logic away from test hence any future change in application would affect only one place - Page Object. When using page object we end up writing page / element level APIs which represent services offered by page. These APIs could be chained together to result in an array of operations, like -

Screenshot from 2016-04-05 12:24:54.png

Here in various page level methods are chained together to reach TeamsAndUsersPage (or any other page object). But this may not be only instance when you need to reach TeamsAndUserPage. Hence you would end up repeating/duplicating these operation through out your test methods. This is when we can create navigation package and add navigation class to facilitate navigation -

Also if you find that navigation is common in all test methods then you can add navigation as setup in test class -

What do you think of this approach? How do you get rid of duplicating page level navigation in your tests?

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos . Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Capture network traffic using WebDriver

We often come across testing requirements when we need to analyze the network traffic to find - HTTP status of page Analyze header information to find if right information is passed Validating parameters related to ajax requests etc Selenium 1 has had a way to capture n/w traffic but the feature does not always work as expected. At times Selenium 1 does not capture all n/w traffic, And given that Selenium 1 APIs are almost dead it is

No Automated Testing

Search This Blog