Right. This is where the real voodo goes down. If you figure out how this works without reading this page you have a divine connection or something.

Basically alot of the designs of Bromine is to be able to do automatic requirement analysis, so it should make clear some otherwise mysterious choices of design.

Automatic requirement works like this:

• A requirement has:
  • Many OS/Browser combinations it should work in (Add these under 'Projects' -> 'Projects')
  • Many testcases which cover the requirement (Add these under 'Test lab' -> 'Test plan')

This gives: number of testcases times number of OS/brows combinations that should all pass before the requirement has been passed.
Example:

• Requirement: Google frontpage
  • Testcases:
    • 1: search for google get google.com as first hit
    • 2: always show google banner
    • 3: Automatically redirect to language specific google
  • OS/browser combination:
    • Vista / IE7
    • Vista / FF2
    • OSX / Safari

Now what bromine needs to determine the requirement status, are test result from the following combinations:

Bromine can get these testresults in 3 ways:

1. Selenium Core
2. Selenium RC
3. Bromine's manual runner

This is where we had to make some solutions that might not be so transparent. For core and RC the actual testresults are linked to testcases by their name. In the 'Test Result Manager' -> 'Analysis' click a suite to see it's details. The text in bold just beside the 'Properties' image is the test name. Bromine will link this testresult to the testcase of the same name.
This means:

• Core: You'll have to name core tests exactly the same as the testcase they refer to. Remember all testcase names are forced lowercase
• RC: You'll have to use the 'Test lab' -> 'Edit node tests' (not the advanced FTP functionality) to upload your tests. Select the testcase the test is paired to when uploading. It should work it's magic.
• Manual runner: Should be easy. Just run the manual tests.

Now move your testresults to 'analysis' Only testresults in 'analysis' are used for determing requirement status
Now navigate to 'Home' and see the requirement status or navigate to 'Test Result Manager' -> 'Show requirements' to see the per-testcase-per-browser/OS results.

Note: Bromine will look at the newest testresults to determine requirement status
Note: 'Failed' (red) wins over 'not run' (yellow) wins over passed (green). Meaning that if a single testcase is failed in a single OS/brows combination the requirement will be shown as failed (red). If everything is passed expect a single testcase which have not been run the requirement will be shown as not run (yellow). If every testcase is passed in every OS/brows combi then the requirement will be shown as passed (green)

Try making this work with the manual runner and understand how testcases are linked to testresults and how this links to requirements before having a go at RC/Core.