martinkl

Both Red Gate and the angel investor were asked for permission before these articles were published.

Go Test It is much more focussed on the browser automation and functional testing; BrowserCam is more about checking that the design looks right.

Just think of the amount of time you'd spend testing all of those manually, and what your time is worth. Go Test It costs hardly anything in comparison.

It is actually based on Selenium internally. The main advantages are:

* Go Test It provides a hosted infrastructure, so you don't have to spend lots of time configuring and maintaining various VMs with different browser versions;

* Go Test It has a lovely test recorder which is much nicer to use and works better than Selenium IDE;

* Many little tweaks and improvements, like automatic screenshots etc.

Sadly, we cannot yet easily interact with Flash or Flex apps. It's something we want to do, but not right now unfortunately.

Thanks, those are some very good points. We've tried to make it easy to get started, but clearly we can do better still.

In what language are your test scripts currently?

Thanks for your comments -- I know we need more work on the user experience. We'll also look into those IE failures.

That's something we're definitely thinking about. For the time being you can just sign up for a month, then cancel it again -- there's no minimum contract.

Google Maps is actually one of the sites which we use internally for testing Go Test It -- many features of it can be automated quite nicely. Particularly with such complex JavaScript, you don't really have a choice but to test in every browser you want to support!

If your objects have a wide variety of attributes, either you need lots of columns with many of them empty, or you need some sort of attribute table with object-key-value triples. Both are bad relational design, but the structure is inherent in the data. If you're having to use a fixed DB schema, I can't see any way around bad design.

When you mention object databases, can you name any examples? As far as I know object databases where talked about a lot some years ago, but never really gained significant widespread adoption.

Also, the article makes the point that non-relational databases are not just about scalability. In fact, in the case of graph databases, scaling problems are just as pronounced as with relational databases. The different data models can enable you to make good database designs, even if the structure of your data is against you.