Bromine for Selenium

From Wikipedia, the free encyclopedia

This article or section needs sources or references that appear in reliable, third-party publications.
Primary sources and sources affiliated with the subject of the article are generally not sufficient for a Wikipedia article. Please include more appropriate citations from reliable sources, or discuss the issue on the talk page.
This article has been tagged since April 2008.

This article may not meet the general notability guideline or one of the following specific guidelines for inclusion on Wikipedia: Biographies, Books, Companies, Fiction, Music, Neologisms, Numbers, Web content, or several proposals for new guidelines. If you are familiar with the subject matter, please expand or rewrite the article to establish its notability. The best way to address this concern is to reference published, third-party sources about the subject. If notability cannot be established, the article is more likely to be considered for redirection, merge or ultimately deletion, per Wikipedia:Guide to deletion.
This article has been tagged since April 2008.

This article or section needs to be wikified to meet Wikipedia's quality standards.
Please help improve this article with relevant internal links. (April 2008)

Bromine
Bromine showing testresults
Written in	PHP/MySQL
OS	OS Independent
Available in	Multilingual
Genre	Quality Assurance
License	Freeware
Website	http://bromine.openqa.org

Bromine is an open source quality assurance tool supporting selenium core/remote control built in php/mysql by Rasmus Berg Palm, Peter Visti Kløft, Jeppe Poss and Christian Nørlyng in 2007/2008

It was mainly built for running selenium tests and storing the results in a convenient way, but expanded into a full scale project oriented quality assurance tool. It lets users set up projects, demands for projects, tests for demands, and testcases for tests.

After having done that the user can upload the tests generated in selenium and run them in the selected operating system and browser of choice. If no tests are uploaded the user can choose to run the tests manually following the testcase associated with the test.

All results are stored in a central place, where they can be reviewed and sent to analysis.

The project demands status are determined by the testresults in the analysis module. Defects can be added either associated to test results or on their own.

Example: google.com

project 'google.com' is added by project leader.
demand 'normal search' in Vista/Firefox is added to project google.com by project leader. It reads:

I want to be able do do a search on the front page. It should return relevant results quickly. I also want commercials on the results page. - Cheers, Mr. project leader.

testcase 'normal_search' is added by tester. It reads:

step 1: Open google.com | google.com frontpage opens. It's minimalistic. There's a search button

step 2: Enter 'selenium' and press 'Search' | openqa.org is high on the results list. There's an ad for bergpalm.dk (if you live in denmark)

test 'normal_search' is created in selenium by tester
test 'normal_search' is uploaded to bromine server by tester
tester selects 'normal_search', Vista and firefox in dropdown menus and clicks run test.
testresults for 'normal_search' is reviewed by tester and sent to analysis
project leader logs in and his demand is colored green to indicate its successful status.