From my internal blog: Last changed: Dec 22, 2008 23:54
We have since implemented Selenium
NG changed the game for performance testing. As we work through browser performance issues, we have to be nimble and flexible to meet the demands of a client-rich architecture. We have to find new ways to performance test, which means we can’t be comfortable with just LoadRunner or even JUnitPerf. It just so happens that not only are there others out there like Bb who have these kinds of problems to solve, but there are developers who have already solved this problem through a software simulation package called Selenium.
Selenium is a portable software testing framework for web applications. The tests can be written as HTML tables or coded in a number of popular programming languages and can be run directly in most modern web browsers. Selenium can be deployed on Windows, Linux, and Macintosh.
Basically, Selenium is an IDE that records and plays-back via a plugin in Firefox. The output of the IDE can be manipulated via multiple programming languages. The tests can then be run via the Remote Control or the Grid. Below is a quick visual.
Well, I’m really not sure why or not. What I am sure is that this is a tool that would allow us to test multiple browsers (IE, Firefox and Safari). What’s even cooler is that we might even be able to test against Mac OS.
Take a look at this link for supported platforms.
We also have a video that talks about how to use Selenium.
I can’t tell you whether we will be able to work with Selenium or not. My first impression is that we will have issues dealing with our MD5 and session code. Until we give it a shot, it’s hard to say whether or not it will be a successful or not. We should attempt to prototype a few use cases besides logging in such as accessing a Course or working with the Grade Center.