testing

Much of our front end testing effort has gone into the TestSwarm module (the platform) and the Frontend Automated Tests module (the tests).

Having written several tests now, I've come to the following conclusions:

<

ul>

Registration is now open for DrupalCamp Twin Cities, July 18-21st, held at the University of St. Thomas in Minneapolis, MN. http://2013.tcdrupal.org

We're very excited about this year's DrupalCamp. We have a record number of sessions submissions, some really excellent keynote speakers, and the best DrupalCamp parties in the country. Before camp the University of MN is hosting a weeklong Accessibility testing of Drupal 8 and we have Accessibility, Twig, Media and Core sprints happening after the camp.

Background

I try to create an automated test for my drupal 7 site to test my rather complex access logic. I am using features, git and drush and a couple of shell scripts for staging. Works great.

My site involves a node access control based on several facts. I wrote a custom module (actually a feature) to create the workflow rules (other workflow module were not fitting my needs)

• workflow_state (custom field)
• workflow history
• global roles
• organic group roles

Tools like ab or siege are inadequate for testing sites served by Nginx (or Lighttpd). They both use threads instead of multiple processes. ab is based on the Apache Portable Runtime, hence it uses the same type of request handling at the OS level that Apache uses.

I'm hoping to find a company in the Boulder/Denver area that can help us with website usability testing. Wondering if the group can send me some referrals.

Several efforts have been made to create a workable way of PHPUnit testing into drupal development. It goes back several years, but it's still actual.

Information is heavily distributed on d.o and other sites.
Here's a list (not exhausting) of discussions, projects, etc about PHPUnit and Drupal.

Purpose of this list is to have a reference of what has been done, tried, etc before.

• http://drupal.org/project/drunit
• http://drupal.org/project/phpunit
• http://drupal.org/node/483940
• http://patshaughnessy.net/tags/drupal

Hi there,

I'm coming back to Drupal after a brief hiatus, and although I've looked around, I can't seem to find any up to date information about how best to unit test Drupal (I'm using D6 for now, but I haven't found anything for D7 either).

I'm asking about Unit testing, because my [previous experiments with Integration Testing seemed unusably slow][1], and although there is this [article here on lullabot][2], it's about 4 years old now, and it seems somewhat out of date.

While converting my exercises from Drupal 6 to 7 I've tried to stay loyal to the new DB-abstraction layer. One of the exercises has some advanced mysql. In an attempt to make this query work, I've encountered several issues that make me question if I've discovered some incompleteness in the DB-abstraction layer or if I'm incompetent and do not understanding the DB-abstraction layer.

I am just starting to look at the OpenPublic beta. I have installed it on a test server where I also have the stock Drupal 7 installed. Working with the Drupal 7 Testing module, all of the test cases pass with the stock Drupal 7 install. However, many of those same tests fail with the OpenPublic install. Just curious whether anyone else has run into this? Before spending time trying to figure out why the tests fail, I wanted to find out whether they are passing for others, or whether there is perhaps some known reason why they fail in the Beta.

Anyone have any good usability resources? Ideally, I'd like to take a course to brush up on my skills but any information would do!