Skip to main content

SELENIUM: Next Test to Framework


Now, let's add one more test to our framework and see how it grows.

 In my previous post we created one basic test which tests that user can successfully login to the application. Let's add next test to same login tests category which will test that user cannot login to application with incorrect credentials and then develop corresponding needed framework.

Second test to Framework

For this we will create test and corresponding framework for below steps:
  • User tries to login with incorrect credentials
  • Verify that the login error message is visible
 As we have already created a LoginTests class under UITests project so, we don't need to add another class as category of this test is same. Just add below test method to this class.
Here, we have created one test method as "User_Cannot_Login_With_Invalid_Credentials". In this method again we have added required steps to test our scenario.

 First and second steps are similar to previous test. Here, third step is assert step which is testing whether error message is visible or not when user tries to login with invalid credentials. In this test I am passing password as invalid but you can try any combination which in whole makes credentials invalid.

 We have created one method in LoginPage class as "IsErrorMessageShowing" which will be checking whether error message is visible after invalid attempt.

 Below is the code snippet of this method.

 In this method we are just checking whether message is visible or not. But we can also check what actually the error message is i.e. whether error message is showing same as we are expecting or not. We can add a separate test for this.

 Again in this method you can see that I am locating the web element in the method itself which can be refactored later as I mentioned in my earlier post.

 Execution of test:

 When you execute this test, as a first step Driver.GoTo method will make us navigate to "http://localhost:26382/wp-login.php". After this in second step LoginPage.Login method will be called. In this method as we are passing invalid password, login won't be successful.

 And in third step, in assert we are calling IsErrorMessageShowing method of LoginPage class. It will be true if error message is visible otherwise it will return false. It error message does not show then test will fail with specified error message.
That's it. We have successfully added two tests with corresponding code to our framework.

 In next post I will be writing something about the test structure. Till now we are just having one method in our test class i.e. [TestMethod]. But there are some other methods too in unit testing framework which you should be aware of and should be used to make tests more powerful and easy.
Thanks for reading this post. See you in the next post very soon...!!!





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