Setting up TeamMentor Browser Automation Project

In this post I’ll walk you through the steps required to set up the browser automation project for TeamMentor.

The first step is to have a specific folder with TeamMentor and The browser Automation project at the same level. The following image shows the specific  folder structure:

Image

From a GitHub perspective you can clone the browser automation project from here, then in the same folder you should clone TeamMentor 3.3

Once you have performed the Clone, you need to open the TeamMentor.WebAutomation.sln  solution file with Visual Studio and compile them (we need to add a new bat compilation file :)).

Feel free to use NuGet to install any missing reference.

You can run the Test Project from Visual Studio if you have Resharper already installed. If you haven’t it, then you need to install the latest version of Nunit.

Running the Test project with Nnuit GUI

Running the Test project from Nunit is simple once the automation project was compiled. So from the Nunit GUI, please  File-> Open Project…

Image

Then navigate to your target folder (which is the folder you created to put the TeamMentor 3.3 and the Browser Automation Project). You need to find and select the TeamMentor.UnitTests.Automation.dll, this dll can be found in the bin folder,please see the following image :

Image

 

 

Click Open and then all the test should be displayed in the Nunit GUI:

Image

You can either run all the Test or just select the test you would like to run.

Dealing with WebDriver servers

In order to run all the test with Chrome and IE, you need a server for that (Don’t worry, the Automation project will take care of that). We still need to define a default path to put the servers,so you probably will see some downloads, that is normal.

When you run the Test, then a daemon or a background console is displayed, that is the server listening.

Image

 

 

What about Cassini and the user accounts creation?

You don’t actually need to start the Cassini process that host TeamMentor, the browser automation project is designed to start that process and kill it just after the last test has run (even when any test has failed).

Regarding the user creations, the Automation project will consume the WebServices API to create the following roles (if they have not been created already in your environment).

  • Admin
  • Reader
  • Editor.

Currently this automation project is just running the test with Chrome, but the framework is designed to run them in Internet Explorer, Firefox and Chrome.

 

Advertisements

About Michael Hidalgo

Michael is a Software Developer Engineer based on San José, Costa Rica. He leads the OWASP Chapter from Costa Rica. You can take a look at my blog at http://blog.michaelhidalgo.info/
This entry was posted in Uncategorized and tagged , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s