Skip to main content

SELENIUM: Creating a Basic Test


By now you must be pretty confident of what actually selenium is, how we can set up an environment to build an automation framework and what kind of things we should have in our mind before we start building a framework. Also, you know few of the basic concepts too.

 I think now it's a good time to start building our framework. The approach I will be using to build the framework is that I will be just creating a basic test first. After that by the course of time I will be adding more tests in it and in this way our framework will start growing in size with each test added.

 I will be doing lots of refactoring as and when required so that the framework remains well structured and easy to use.

 As to build a framework we need an application, I will be using WordPress for this purpose. You can use any application but if you need to get a start on WordPress too you can download and setup from this link.

 Instead of adding all the required things in the framework what I will be doing is I will be creating tests and then adding the required things to execute this test in the framework. Hence, we are choosing the test driven framework rather then framework driven tests.

First Basic Test

 As a first basic test, lets create the below test and then corresponding framework.
  • User can login to application
  • Verify it
For this,  Add a class e.g. "LoginTests" in UITests project. Create a test method as shown below



 Here you can see that I have created a test "User_Can_Login_Successfully" and in this test I have added required steps to check login.

 It is a good practice not to declare variables in tests. Rather all these kind of things should be kept in framework which makes much easier to understand and use.

 In test there should be a logical flow which a tester need to perform while executing particular test rest should be handled by the framework itself.

 Driver class is already known to you as shown in my "Hello Selenium" post.

 Create LoginPage and HomePage classes in "TestFramework" project as shown below

 LoginPage class:



 HomePage class:

Execution of test:

 This test has below steps
  • Driver.GoTo(@"http://localhost:26382/wp-login.php");
  • LoginPage.Login("testuser", "testpasword");
  • Assert.IsTrue(HomePage.IsAt,"Login not successful"); 
When you run this test, first it will navigate to  "http://localhost:26382/wp-login.php" i.e. login page of wordpress.

 After this it will call Login method of LoginPage and pass username and password as parameters. Further,  login method calls the private methods i.e. EnterUser(), EnterPassword() and then ClickLogin().

 After login step, there is one assert step that basically verifies whether user is on home page or not. If it is not on home page then tests fails with assert message as "Login not successful".

 That's it....you have just setup your framework and added first test to it. Great...!!!!

 In this example, I located the web elements in the methods itself which can be refactored so that we don't have to bother for this in methods. In my later posts we will be refactoring our framework more and more until it becomes easier, less complex and well structured.Also, I will be writing about locators in brief for those who don't have much idea about it. We will also learn about selenium's PageFactory in details too.
Thanks for reading this post and see you in the next post very soon. 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