I wasn’t 100% clear from the docs how to implement rollup rules in selenium ui-elements and searching the web didn’t return much - so here’s an example in case it’s helpful to others.
While playing around with selenium IDE I discovered a fantatsic tool that makes test (and results) more readable while making the suite of tests easier to adapt to layout changes.
What it does is to allow you to centrally define most of the xpath (and related) statements and give page elements meaningful names.
One of the nice things about selenium tests is that you get a clean browser session each time (so no problems with cookies etc left over from earlier)
But the way this is achieved is by using a new profile each time and this profile doesn’t know about your SSL exceptions for avoiding error messages with those self-signed certs on the dev server.
Hudson http://hudson-ci.org/ is a continuous integration server - it runs and monitors ‘jobs’ in a way that is useful to regularly build software and report on any errors.
Selenium http://seleniumhq.org/ is a suite of tools specifically for testing web
applications - it tests the full website by automating the running of one or more browsers (so you can test all that pointy clicky ajaxy stuff)
<?php$result=db_query("SELECT nid FROM node where type='mytype'");while($row=db_fetch_object($result)){node_delete($row->nid);}node_type_delete('mytype');?>
We had an old Drupal module which contained exported views, most of our sites uses features to manage view - so when they needed updating we wanted to use features.
So we deleted the old module and added a new one with the required views.
For those who haven’t read it, http://buytaert.net/8-steps-for-drupal-8 is worth a read. In it, step 6 is “Backport small changes to stable releases”. Drupal 7 is the first release we’ve been able to entertain the idea, since we have a testing framework with 25K tests and a version-specific dependency system. What the boundaries are of such changes isn’t quite defined yet, because Dries and I have kept pretty busy with, you know, getting Drupal 7 out the door. :P~