Skip to main content

"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:

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 to be recognized so, don't forget to use this attribute.


Then, Driver class containing the required code for test.




In this example, one test class is created under UITests project and in this test class one test is written with required steps that I would need to run for this example test.

Further, there is a Driver class created in TestFramework project which handles all the required things for tests.

In this way we are separating tests from our framework. We will be discussing about project structure in more details in my later posts.


Test execution:

Step 1: Driver.GoTo("http://www.google.com")  will call GoTo() method of Driver class which in turn will execute Driver.Navigate().GoToUrl(). It will make us navigate to "http://www.google.com" on browser.

Step 2: Driver.EnterText("Hello Selenium")  will call EnterText() method of Driver class which in turn will execute code shown in above snippet. First it will make our driver to wait for 5 whenever it tries to find any web element. Then it will find a web element with name as "lst-ib" and finally it will enter "Hello Selenium" text to search box.

Step 3: Driver.ClickSearchButton()  will call ClickSearchButton() method of Driver class which in turn will execute the code shown in above snippet. It will find a button with name "btnG" and then click on this button.

In my next post I will be writing about page object model used to design our framework.



Thanks for reading this post and see you in next post. Cya!






Comments

Popular posts from this blog

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...

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...