Screenshot here: http://skitch.com/miketaylr/b7yae/test-swarm-miketaylr

In Firefox 3.5, Safari 4.0, and Opera 10b3 (all on Mac), the "connected" information overflows (partially, or completely) out of its containing list item, when looking at a Windows OS and IE client.

Hi,

As seen in the discussion group, short open tags are used in php scripts.
As this property is now deprecated in php, it would be nice to avoid using it.

Thanks

from logic/tinder.php
$search_user = preg_replace("/[^a-zA-Z0-9]/", "", $_REQUEST['user']); only allows alphanumeric usernames, but signup does not prevent this.

The badge for Chrome says 3b1 when I am using dev channel 4.0.203.2.

When running testswarm and only having one test-module the browser icons does not appear above the results-table. Adding an empty dummy-module makes them appear.

The test overview page (where it shows all the commits on a grid) displays incorrectly after adding a new entry.

I activated firefox 2.0 testing which added an extra column on the page. However, the old tests did not have extra entries for ff 2.0, which made all the cells be one off after where ff 2.0 should have been.

Hopefully that makes sense.

Tests that were run prior to the inclusion of the new test had a missing cell in the row, causing test cells to be displayed under the wrong column.

While fixing MySQL and optimizing the code is more important, when the site can't connect to MySQL it needs to display an error message instead of attempting to load the page. When MySQL is down, I get the message that my browser is not supported for testing, and all the browsers listed on the home page are missing.

With the local build Im running, the testswarm.sql doesn't have a default value for request in the users table, and the logic/signup.php insert statement doesnt pass in a request parameter.

The user ends up thinking their account is created successfully because they are redirected accordingly, but the insert never occurs. The return result of mysql_queryf needs to be checked.

If I run the insert statement manually (from line 23 of signup.php) I get the following error: ERROR 1364 (HY000): Field 'request' doesn't have a default value

There are more useragents in the table than the auto_increment. You aren't inserting into the table yet, so this isn't a problem, but will be if you add an administration interface. It should be updated to 70 at the time of this writing and kept up to date when adding more useragents. I'd suggest a comment line on line #176 to remind people to do it, or better yet, a test.

I hate the idea of turning away someone who is willing to run the tests. And sometimes I don't have the specific browser/os combo that the test wants.

I'd like to come up with something a bit more flexible.
Track & report all the data people are willing to collect for us.

Allow the test creator to, instead of specifying which are the only browsers they're interested in, specify which browsers are required in order for the whole suite to pass.

Then in the report view, only show boxes for the few required browsers plus whatever other browsers have actually run the tests.

Sometimes when adding a job I want to also delete the previous job for the same project or whatever.
e.g. I don't need 5 jobs for mootools trunk, when I add a new one, I want to delete the old one.

Google Chrome 3.0.195.32 is being recognized as Safari 4.0 as shown in images below:

http://i71.photobucket.com/albums/i157/mikecanfield/GoogleAquiresApple_1.png
http://i71.photobucket.com/albums/i157/mikecanfield/GoogleAquiresApple.png

When an row is added to "useragents," jobs don't detect it because of the way that run_useragents works, which is reasonable. However, whenever I want test a new version of a browser, I have to rewrite the job, which can be a more work. I would recommend either having browsers automatically added to run_useragents if they fit under the criteria for a run, or create a clone button that creates a new copy of the job with the new user agent added, or create an update job button that adds the new user agent to the job without creating a new job or deleting an old.

I am most in favor of the last option.