Nice. And that's coming from someone who has been thinking about an app like this for quite some time.
One minor thing: On the "Welcome to Go Test It!" page (/welcome), you have "I have existing Selenium scripts that I want to upload." and "I do not yet have any test scripts." I bristled at that slightly. I _do_ have a bunch of test scripts (that I worked pretty hard to create), but they are not in a ruby, python or selenese form. Maybe something in the gray text for the second option that acknowledges something like "or I don't have scripts in a Selenium format" would create less of a false dichotomy and help me feel better about myself than selecting "I do not have test scripts" does. Maybe I'm overly sensitive.
One bigger thing: I like the options for the "New Test Script" (projects/*/scripts/new) page. I'll probably go back and install the Firefox plugin when I have more time, but I wanted to see how it works quickly, so I backed up and went to the "Write a new script in a text editor" option. Now I'm presented with a blank text editor, with little or no clue as to what I'm supposed to do there. At the very least you should have links to samples or documentation for the scripting language, but you could do better than that. You know my app's URL at this point. You could pre-populate this script (for new users) with a basic "Is it up?" script, maybe checking the title and some H1 text on the page, just to give me a working example to modify. I think for new users you should minimize the number of steps to a running test. As it stands I either need to install a firefox plugin (a pretty big hurdle, imo, although it is right to offer that) or (I'm guessing) go off and research how to write Selenium scripts and then come back and create one on your site. As a random user looking to solve my functional testing problem, I'm not that motivated to do either. Once I'm off writing Selenium code I'm likely to forget about GoTestIt. I'd suggest that you either auto-populate a basic script for new users, so that I can click "Run Test" right away and see what happens or find a way to record basic scripts directly in the browser without installing a plugin (or both).
(Also, personally I find the "Feedback" tab on the left to be a little distracting, but I'm on a netbook so my monitor is smaller than most. Of course, it looks a little funny when glued to the scroll bar too. I wish UserVoice would let you attach that to the top or bottom of the screen.)
I have a bit of history with writing automated functional tests and testing frameworks. I've used a large number of tools, most frequently HttpUnit, custom scripts built on top of Apache's HttpClient, a Jakarta Commons subproject called Latka that sort of died on the vine (although I think it may have replaced Apache's watchdog servlet engine compatiblity test for a time), custom Ruby scripts based on Hpricot, and others.
My current project is Drupal based so I'm using a php unit testing framework called SimpleTest. I've found it pleasantly easy to work with for basic HTTP and HTML level testing but it doesn't have any JavaScript or browser-driving capablities, so I'm probably in your target market (i.e. I have unmet needs).
One minor thing: On the "Welcome to Go Test It!" page (/welcome), you have "I have existing Selenium scripts that I want to upload." and "I do not yet have any test scripts." I bristled at that slightly. I _do_ have a bunch of test scripts (that I worked pretty hard to create), but they are not in a ruby, python or selenese form. Maybe something in the gray text for the second option that acknowledges something like "or I don't have scripts in a Selenium format" would create less of a false dichotomy and help me feel better about myself than selecting "I do not have test scripts" does. Maybe I'm overly sensitive.
One bigger thing: I like the options for the "New Test Script" (projects/*/scripts/new) page. I'll probably go back and install the Firefox plugin when I have more time, but I wanted to see how it works quickly, so I backed up and went to the "Write a new script in a text editor" option. Now I'm presented with a blank text editor, with little or no clue as to what I'm supposed to do there. At the very least you should have links to samples or documentation for the scripting language, but you could do better than that. You know my app's URL at this point. You could pre-populate this script (for new users) with a basic "Is it up?" script, maybe checking the title and some H1 text on the page, just to give me a working example to modify. I think for new users you should minimize the number of steps to a running test. As it stands I either need to install a firefox plugin (a pretty big hurdle, imo, although it is right to offer that) or (I'm guessing) go off and research how to write Selenium scripts and then come back and create one on your site. As a random user looking to solve my functional testing problem, I'm not that motivated to do either. Once I'm off writing Selenium code I'm likely to forget about GoTestIt. I'd suggest that you either auto-populate a basic script for new users, so that I can click "Run Test" right away and see what happens or find a way to record basic scripts directly in the browser without installing a plugin (or both).
(Also, personally I find the "Feedback" tab on the left to be a little distracting, but I'm on a netbook so my monitor is smaller than most. Of course, it looks a little funny when glued to the scroll bar too. I wish UserVoice would let you attach that to the top or bottom of the screen.)