In my previous post we learnt about nested classes. So, now this is the time to make use of that in our framework. This is how we should always progress, learn about something and then implement it otherwise there is no use of learning new things.
So, let's now create a test where we can use nested class.
From above code snippet you can see that I have used nested class created in previous post i.e.
"LeftNavigation.Posts.AllPosts.Select(browser);"
As mentioned in previous post, this code will make user navigate to Posts->All Posts page and actual code which makes this happen is in "Select(browser)" method. See that we are passing browser instance as parameter to this method as we need this browser instance to be used.
Further as mentioned in previous post, we are not using code directly here in this method to navigate to a particular menu. Instead we are using another class i.e. "MenuSelector" for this as doing this will make code more readable, easy and reduce the redundancy.
Again, we are passing browser instance to MenuSelector class as we want it to use the same browser instance.
"var menuSelector = new MenuSelector(browser);"
After this we are calling "Select()" method of menu selector class which in turn will do the actual navigation.
"menuSelector.Select("menu-posts", "All Posts");"
In this Select() method we are passing id of top menu web element i.e. "Posts" in this case and link text of sub menu element i.e. "All Posts" in this case. This way every time when we need to navigate to a particular menu we just pass id of top menu element and link text of sub menu item calling the same method.
Once this step is executed in next step we are confirming whether it was successful or not using below line of code:
"Assert.IsTrue(allPostPage.IsCurrentPage(), "Not the expected page");"
To do this I have created one more class "AllPostsPage" and created a method i.e. "IsCurrentPage()" to check whether we are on this page or not.
In "IsCurrentPage()" method I am just checking whether there is "Add New" link displayed in <h1> tag or not. If it is showing then we are on right page otherwise not.
Further as we have created a new class so, make sure that we have included code to declare and instantiate it's object in our test class as mentioned in my earlier post. i.e.
"private static AllPostsPage allPostPage;" and
"allPostPage = new AllPostsPage(browser);" line of codes.
This is it.
So, in this post we added one more test to our framework and make use of nested class and common method. This is what we will do in our future posts too. Whenever there is a possibility of making something more easier to use or making something common in order to reduce redundancy we should do that as our main motive always is to build a framework that is easy to use otherwise we end up building a framework which is used by no one.
In my next few posts I will be adding more tests to our framework which makes use of the same nested class and common method to make it more clear how it benefits us.
Thanks for reading this post. See you in next post. Cya.
So, let's now create a test where we can use nested class.
About test
In this test we will try to perform below steps:- Navigate to login page
- Login to application
- Navigate to Posts->All Posts menu
- Confirm that we are on "All Posts" page
From above code snippet you can see that I have used nested class created in previous post i.e.
"LeftNavigation.Posts.AllPosts.Select(browser);"
As mentioned in previous post, this code will make user navigate to Posts->All Posts page and actual code which makes this happen is in "Select(browser)" method. See that we are passing browser instance as parameter to this method as we need this browser instance to be used.
Further as mentioned in previous post, we are not using code directly here in this method to navigate to a particular menu. Instead we are using another class i.e. "MenuSelector" for this as doing this will make code more readable, easy and reduce the redundancy.
Again, we are passing browser instance to MenuSelector class as we want it to use the same browser instance.
"var menuSelector = new MenuSelector(browser);"
After this we are calling "Select()" method of menu selector class which in turn will do the actual navigation.
"menuSelector.Select("menu-posts", "All Posts");"
In this Select() method we are passing id of top menu web element i.e. "Posts" in this case and link text of sub menu element i.e. "All Posts" in this case. This way every time when we need to navigate to a particular menu we just pass id of top menu element and link text of sub menu item calling the same method.
Once this step is executed in next step we are confirming whether it was successful or not using below line of code:
"Assert.IsTrue(allPostPage.IsCurrentPage(), "Not the expected page");"
To do this I have created one more class "AllPostsPage" and created a method i.e. "IsCurrentPage()" to check whether we are on this page or not.
In "IsCurrentPage()" method I am just checking whether there is "Add New" link displayed in <h1> tag or not. If it is showing then we are on right page otherwise not.
Further as we have created a new class so, make sure that we have included code to declare and instantiate it's object in our test class as mentioned in my earlier post. i.e.
"private static AllPostsPage allPostPage;" and
"allPostPage = new AllPostsPage(browser);" line of codes.
This is it.
So, in this post we added one more test to our framework and make use of nested class and common method. This is what we will do in our future posts too. Whenever there is a possibility of making something more easier to use or making something common in order to reduce redundancy we should do that as our main motive always is to build a framework that is easy to use otherwise we end up building a framework which is used by no one.
In my next few posts I will be adding more tests to our framework which makes use of the same nested class and common method to make it more clear how it benefits us.
Thanks for reading this post. See you in next post. Cya.
Comments
Post a Comment