Focus Intelligence Inc.

BLOG | FOCUS INTELLIGENCE

Atteignez vos objectifs.

Integrating Bromine into QA automation

In its beta version, but still great. OpenQA has integrated the Bromine Project into its suite of excellent solutions, from which the “fabulous” Selenium. The project allows mainly saving all of your Selenium tests results in a very detailed and intuitive manner. As mentioned, the project is still in beta, so it still lacks some refinement, especially when we know that the project was characterized as “it works, but it’s a mess” : ) by OpenQA itself. So whoever is using Selenium as an automated functional test tool, Bromine is a must.

Let me present the modification required to integrate Bromine, in an automated Microsoft Windows IIS web development project environment (pretty specific, but common : ) ). Allow me first, to describe the already in-place environment:

- An already existing web application running on IIS (ASP.NET)

- You already have multiple Selenium suites

First of all, Bromine relies on an AMP infrastructure, so start by getting WAMP running on a separate port than IIS. So, the Bromine generated URLs need to be modified to post the results into a separate web server with the corresponding PORT number. After setting up the project and everything related, it is time to run all the test suites in an automated fashion, with the corresponding generated URL in respect to the test suites and the WAMP server port number for the results page.

Once that is done, how to figure out, in an automated fashion, that a test suite has finished running! Our solution was to modify the “parser.php”, to include a external script call to close the browser. The “parser.php” page is called once the results are posted to bromine and inserted into its database, so once that is done, the test suite is also done and it’s time to pass on to the next test suite! In addition to closing the browser, in integration with CruiseControl.NET, you can also include a success or failure publishing mechanism upon every test suite at the same time!

And that’s it, pretty simple and VERY efficient! From now on, you benefit from having all of your QA running hours freely upon every build if it suits you; it’s up to you, in addition to having all the detailed results of every Selenium command!

Enjoy your no-regression insurance free of charge!

Fri, August 29 2008 » /Georges Saad, Agile, Functional testing, assurance qualité

One Response

  1. David Thibault September 2 2008 @ 10:01 am

    Why is this post in english alors que les autres articles sont en français ?

Leave a Reply