Skip to main content

SELENIUM: Using Common Methods in Different Tests

As I mentioned in my previous post that we will create few more tests which will make use of the nested navigation class and common menu selector class to see how we can make use of these.

 So, let create one more test to check some other navigation e.g. navigating to "Add New" page and to implement this we will make use of the same navigation class and menu selector class.

About test:

In this test we will write code to implement below steps:
  • Navigate to login page
  • Login to application
  • Navigate to Posts->Add New post page
  • Confirm that we are on right page
Again, we are already familiar with step 1 and 2 so, we will be focusing step 3 and 4 only.

 Before we start writing code for this test let's go through some of the refactoring that is needed MenuSelector class's select methods created in previous post.

 MenuSelector class created in previous past:
We will be refactoring below areas in this class:

 #1: Used WebDriverWait
#2: Removed browser.Wait(1)
#3: Used CssSelector locator to find subMenu instead of using LinkText locator
#1: Used WebDriverWait
As you can see that we have used below line of code to e.g. find topLevelMenu item

 var topLevelM = browser.Driver.FindElement(By.Id(topLevelMenu));

 Now, this might fail sometimes if e.g. this element is not visible yet during execution of this statement as it takes some time to load this.

So, it is always a good practice to make use of wait while doing these kind of stuffs as it might be possible that when this line is executed the required web element is not visible yet as it is still loading otherwise it throws an exception.
I will be covering different kind of waits that we can use during my later posts. So, we won't be focusing more on working of wait here.

 So, let's just focus on this particular code for now.

 Here we first made the driver to wait for at max 15 seconds to check the visibility of element. If it finds the element within this time span it will move to next sentence otherwise keep on checking for 15 seconds before saying that the element is not found.

 This way we are making sure that application won't throw exception if it does not find the web element immediately and hence our framework becomes more robust.

 #2: Removed browser.Wait(1)
As we are now using WebDriverWait so we don't have to use this. Further, it is always not recommended to use thread.sleep method. See below the complete Select() method:


 #3: Used CssSelector locator to find subMenu instead of using LinkText locator
Finally, this is one more refactoring need in this class. This is needed as using LinkText locator will fail when we try to implement our next test due to the fact that there are more than one web elements with LinkText as "Add New" so, our web driver cannot find the required web element and our test will fail.

 To overcome this I have used CssSelector locator so that instead of passing link text information as parameter during MenuSelector.Select() method call we will pass it's css value.

Now, as we have done the required refactoring, let move to to implement our test.

Test execution:

After login to application using login method at step 2, next sentence starts executing i.e.

 LeftNavigation.Posts.AddNew.Select(browser);

 As you can see here that after LeftNavigation.Posts there is new nested class created i.e. AddNew for new navigation. And under this class a Select() method is created like we created in previous post with only difference that of css value for subMenu item. As in this case too topLevelMenu is same so only difference will be in subMenu hence the css value is different.

This will further call the common select method of MenuSelector.

 As last step we need to confirm whether we are actually on add new post page or not. So, this is done using below sentence:

 Assert.IsTrue(addNewPostPage.IsCurrentPage(),"Not the expected page"); 

 Similar to our previous post where we checked whether we are on "All Posts" page or not, here I have created a new class i.e. "AddNewPostPage" with "IsCurrentPage()" method inside.


 "IsCurrentPage()"is the method which does the confirmation whether this page is currently opened or not.

 With this we are also making things consistent i.e. whenever we need to check whether current page is opened or not we will create a method named "IsCurrentPage()" which will make our framework easy to understand and use.

 This is it.

 In this post we did few refactoring which was needed in our framework and then created one more test to support our thought of making things common as mentioned in previous post.
Thanks for reading this post. See you in next post. Cya.

Comments

Post a Comment

Popular posts from this blog

"Hello Selenium"

Now, as we have already setup the required environment, let's just start with a hello world test with selenium. In this let's just write a basic test to make sure that our environment is working properly. For this hello selenium test we will be automating below test: Navigate to " https:// www.google.com  " Write "Hello selenium" in search box Press search button Below are the code snippets: Test class UnitTest1 containing required test. Here in this class, at the top I have used two statements i.e.     using Microsoft.VisualStudio.TestTools.UnitTesting;     using TestFramework; First using statement is required in for writing unit tests and second using statement is required so that we can access methods from class under TestFramework namespace. There is [TestClass] attribute used with this class. This is required so that tests written in this class can be recognized. If you miss this attribute then your tests are not going ...
Post a Comment
Read more

SELENIUM: Using Nested Classes

In this post I will be using nested class pattern to make few things easier. e.g. If you see in our test application there is a navigation bar on left side containing various menus i.e. Posts, Pages etc. Further each main menu contains sub-menu e.g. Posts menu contains sub-menues as "All Posts", "Add New", "Categories" and "Tags". In this type of situations, it is good to use nested classes to make things more readable and easy to use. E.g. Suppose I want to access "All Posts" navigation then I would want this to be done like this. " LeftNavigation.Posts.AllPosts.Select(); " i.e. I would want that there would be a class called "LeftNavigation" and when I press '.' (dot) it shows all the main menues in this navigation e.g. "All Posts", "Pages" etc. then I choose " LeftNavigation.Posts " and again when press '.' it shows all the sub-menues inside this Posts menu...
Post a Comment
Read more

SELENIUM: Adding Next Test With Proper Test Structure-1

As I mentioned in my previous post that now its time to refactor our tests a little bit so that each test is written with proper test structure as required. After refactoring tests we will add one more test to our framework with proper test structure. So, lets do it now. Refactoring tests Till now we have added two tests to our framework i.e.         And Let's refactor these tests first before adding more tests to this framework.  In each method let's log some message so that we come to know how the execution was done. # AssemblyInitialize method:     In this method let's put code to initialize the log so that it can be used throughout the assembly. Before moving to next method let's talk about other refactoring made in this test project. #1: All static classes are made non-static so that we can created instances of page objects instead of directly using them. So, now on we cannot use class directly. Instead we will...
Post a Comment
Read more