Boombatower's Blog

I have released the second alpha of the Usability Testing Suite. The API is fully functional and there are two plug-ins implementing the API. The reason the module is still marked as alpha is due to the user flow issues and clean-up items.

For more detailed information on the status of the project please read the alpha 2 release notes.

I would like to get feedback on what people think of the module, as it is intended to be used to enhance Drupal's usability.

Make sure you read the INSTALL.txt file before installing.

It has come to our, SimpleTest module developers, attention that the tests are breaking at a rapid rate. Most of the tests that currently have issues passed when they were originally committed to the core. The list of tests that passed was used during the cleanup stages, but hasn't been changed since SimpleTest was added to core and stands as a record.

I previously posted "Core patches need to update tests as well" in preparation for SimpleTest becoming part of core. Sadly it doesn't appear it was heeded.

After a long process of trial and error rolling back commits, webchick found the patch that broke the translation test, and possibly others. This would have saved everyone involved a lot of time had those who reviewed and wrote the patch simply run the tests on the patch, or better yet if testing.drupal.org were finished and implemented on drupal.org so that it would happen automatically.

Regardless it is rather annoying to spend several weeks cleaning up the tests to see them broken by un-tested commits. Before marking a patch as "ready to be committed" ensure that someone has run the suite of tests on it. If that hasn't been done I would hope that the patch isn't committed.

Recently I have come across several creative Drupal related movies that I decided to share. If you have any others feel free to comment.

• Drupal
• The Drupal Song Music Video
• The Drupal Boys
• The Drupal Boys V2
• Drupal 30 Second Video - License Info
• The Drupal Reel
• Hard Work + Drupal

The Paris sprint went off without a hitch. We accomplished several goals that will move Drupal into its next stage of development. Among the things accomplished was the addition of the SimpleTest module to Drupal core. Inclusion of a common testing suite with Drupal core will provide a basis for complete testing coverage which was stated as one of the goals for Drupal 7. A necessary component of this initiative is a method for measuring the success of testing. This will be done with "code coverage" tools which measure the percentage of code that is being tested. To put all of this work to good use an automated testing farm is being created which will run the tests on all patches to core. Work on these three areas was unified and pushed forward at the sprint.

An enormous amount of preparation has been completed over the past month and a half in order to prepare SimpleTest for inclusion in the core. The work has included API cleanup and documentation, functional test writing, statistic collection, and unit test planning. The first three objectives were finalized at the sprint before SimpleTest was added to core. Major strides were made on the last objective at the sprint and was planned to become part of core within the next week or two. The whole idea of unit testing is still somewhat up in the air.

Without the sprint the final pieces necessary to bring SimpleTest into the core would have taken much longer to finalize. Thanks again to all those who sponsored my trip to the sprint.

The current plan is for SimpleTest to become part of core in the near future. Once this happens the tests will need to be updated with patches to core. However, at this point SimpleTest is not part of core and whenever core changes break the tests someone, usually me, has to go through and figure out why they broke, make sure that the code they test doesn't actually have a bug, and fix them.

As we draw nearer to the Unit Testing Sprint we are attempting to plan and prepare for the sprint. Having to go through and fix tests whenever the core is changed can be quite time consuming. It would be helpful if we could begin the practice of updating tests along with the core before SimpleTest is officially part of core. Any help in this department would be much appreciated.

Recently a number of the tests broke due to changes in the core. If you would like to help please see the list of tests that should pass and make sure that they still do. Specifically, it appears that commit #109998 has broken over four of the tests and it would be appreciated if others could take the initiative and fix those tests.

Thanks in advance.

Update

It appears that I have created some confusion about what exactly the sprint will be about. In my previous post I stated:

The sprint will take place April 19th - 21st. The sprint will coincide with DrupalCamp Paris in order to attract Drupal enthusiasts to help with the unit testing. Anyone interested should plan on attending the sprint at some point during their stay. There will be instructional time for those planning on contributing at the sprint.

The sprint has come together rather quickly over a very accelerated planning period matched by the accelerated development timeline. The idea of inviting other Drupal enthusiasts to come, learn, and help out in the unit testing sprint was based on some original ideas thrown around in the planning process, but will not be occurring due to logistical and time restrictions.

I realize that some people have made plans to attend the sprint based on the previous description. I am sorry for this miscommunication and thank you for your enthusiasm. If you are interested in coming to Paris to help write tests, contact the testing sprint organizer Kieran Lal.

Getting Involved

If you would still like to help there are several ways you can get involved.

• Read the SimpleTest issue queue
  • Code Standards
  • Unit Testing Plan
• Keep up to date on what needs to be done by reading groups.drupal.org/unit-testing
  • Functional SimpleTest Status - List of all tests
  • SimpleTest Roadmap for Drupal 7

If you have any other questions please feel free to contact me.

I will be attending the Paris Coding Sprint to work on unit testing for Drupal 7 thanks to those who generously supported me and Google. Leslie Hawthorn was able to secure funding from Google to sponsor both Charlie Gordon and Jimmy Berry (me). Another thanks to those who gave generously to help me get to the sprint.

• Greg Dunlap
• Josh Koenig
• Michael Anello
• Thomas Moseler
• Kent Bye
• Paul Chvostek
• Bonnie Bogle (Development Seed)

Thanks!

The sprint will attempt to get a jump start on unit testing in order to postpone the code freeze for Drupal 7. This is a crucial initiative in advancing Drupal as a whole.

For more information on the sprint see my previous post.

Background
An overview of the plan to get SimpleTest ready for core can be found at the SimpleTest Roadmap for Drupal 7 post which links to the specific discussion on unit testing. Over the weeks since Drupalcon Boston 2008 we have accomplished an enormous amount of cleanup and testing. The SimpleTest module has been transformed into the future of Drupal testing.

At the sprint we intend to continue this by moving into unit testing instead of functional testing which is almost complete. The accelerated development schedule is necessary in order to meet Dries' deadline, which is fast approaching, for complete coverage of Drupal core and extend the developement cycle. Testing will not only extend the cycle of development, but also make Drupal more stable by ensuring that changes to the core do not break Drupal. The tests will provide a wall of protection as illustrated below.

Due to my role in the SimpleTest area it is important that I make it to the sprint. The work that will be completed will not just help one area of Drupal, but Drupal as a whole since it will allow faulty patches to be much more easily recognized which will make reviewing core patches much easier.

I would like to attend the Drupalcon 2008 Conference in Boston. Check out my user page.

I will be staying in a Hostel and using a Taxi to get to and from the conference.

I have contributed a number of SimpleTests for Drupal and plan on continuing my work after GHOP is over.

http://drupal4hu.com/node/112