Skip to content

selenium (or windmill) tests #308

@perrygeo

Description

@perrygeo

As the last deployment clearly demonstrated, we need a better way to test how marinemap fits
together for a particular project.

Right now we have unit tests that handle individual components well. There are also unit tests for
some of the javascript widgets that cover how these widgets behave in a vacuum. Both of these
work well, and python unit tests can be run to pin down exactly which revision introduced a bug.
I'm working on this functionality for the client-side, but it won't test how widgets interact with
the server or each other well.

To fill that gap of "Integration Testing" we need something like Selenium or Windmill that
basically run through the application as a user would. I've put off working on something like this
because it's so hard to setup a test environment for each and every revision. I'm worried now
that we might never get integration testing done if we wait for the perfect solution though. It
should be enough to just start by running tests periodically on narwhal, and providing an
interface for developers to update that server and manually trigger the running of tests.

Colin, I'm wondering if this is the sort of thing that you would be interested in doing. It involves
setting up Selenium(or Windmill) to run both on the server and at least one client machine
running Firefox and hopefully some other browsers. Both these apps allow you to define tests
using a WYSIWYG-type environment, but there would also be situations that would call for some
DOM/javascript work.

Lets talk about this during the next dev call.

Google Code Info:
Issue #: 312
Author: underbluewaters
Created On: 2010-03-23T22:10:06.000Z
Closed On:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions