Open perrygeo opened 12 years ago
Google Code Info: Author: will.mcc...@gmail.com Created On: 2010-04-07T20:30:19.000Z
See dev call agenda. We have some time to go over how to use this system once it's in place.
Google Code Info: Author: underbluewaters Created On: 2010-05-17T22:13:14.000Z
waiting on new server
Google Code Info: Author: ColinMEb...@gmail.com Created On: 2010-07-01T16:43:34.000Z
For this ticket to be closed, we need:
Google Code Info: Author: underbluewaters Created On: 2010-10-06T22:55:42.000Z
Google Code Info: Author: underbluewaters Created On: 2010-10-06T23:27:21.000Z
Google Code Info: Author: ColinMEb...@gmail.com Created On: 2010-12-08T20:30:41.000Z
Google Code Info: Author: perrygeo...@gmail.com Created On: 2011-09-20T19:45:21.000Z
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: