Testing and Quality Assurance

Here are the results of running our whole test suite on PostgreSQL 8.3.

• Actions configuration 30 passes, 8 fails, 0 exceptions
  See http://drupal.org/node/261859
• Block functionality 57 passes, 1 fail, 0 exceptions
  No known issue (yet!)
• Blog API functionality 45 passes, 2 fails, 1 exception
  No known issue (yet!)
• Search engine ranking 21 passes, 5 fails, 20 exceptions
  See http://drupal.org/node/296624
• Module list functionality 53 passes, 4 fails, 0 exceptions
  No known issue (yet!)

Splitting the discussion from here:

http://lists.drupal.org/pipermail/development/2008-August/030879.html

afaik, the steps to get this running are:

1. Abstract comment creation functionality in project_issue.module - http://drupal.org/node/271216
2. Allow testing.drupal.org to post back to issues and mark as code needs work when patches don't apply.
3. Get all known failures cleared
4. Allow testing.drupal.org to post back to issues and mark as code needs work when core tests fail
5. Extend this to Drupal 6

I'm working on a project that does some fairly crazy extensions to drupal core functionality (biggest single item right now: $user goes from a stdClass object into an actual classed object, and I use OO fun to make a seven-way distinction between different user 'types'), and have resolved to basically take a TDD approach to driving the site forward, given the complexity and breadth of these changes.

1. Too heavy to write simple test

if I changed code in blog_link to remove author's blog link, how can I write a small code to ensure it? logic as

testnode = new node;
node->type = blog;
testlink = blog_link('node', testnode);
assertNotContains('tom's blog', testlink);

2. Not IDE friendly, even for simpletest series.

Using simpletest eclipse plugin, you can't run test file because of the .test extention, have to rename to .php. After renaming, it still can be run because of complex file including.

Any thoughts?

If you're looking for current status, look at the most recent comment

Since we've still got core test failures, and no automated patch testing, I thought it'd be worth doing a snapshot of tests that pass week by week (or more frequently if there's lots of commits). This allows us to keep a historical overview of where bugs have been introduced into either core code, simpletest.module or tests themselves. It should also hopefully help to reduce duplicate issues about broken tests (since a test failure can be down to any one of those conditions).

Now that SimpleTest is apart of Drupal core issues related to the 7.x development have been moved to the core issue queue. If you would like to be involved I have included two links which will filter the issues to only display SimpleTest related issue. You can obviously used the advanced search feature to narrow your results to the SimpleTest related components instead of using the links.

Hello everyone!

I'm having problems when trying to add tags to the story/page creation form using simpletest.

I have a vocabulary which uses FREE TAGGING, and I want create a new page with the tag "cat". The vid of the vocabulary is stored in the class attribute 'free_tagging_voc'. What I've been trying to do is the following:

First, for those that don't want to read the full post, here's the "30-second elevator speech":
This post to to discuss using Seleinum with Drupal. Specifically using Maven to run the selenium tests and writing the Selenium tests in Java.
The example code be downloaded from the Workhabit Inc. public repository here: https://svn.workhabit.com/svn/public/drupal/selenium/trunk
One must have the following installed to run:
1. Firefox
2. Java 1.5+
3. Maven
All 3 are easy to install and aquire. Once you download the code from the repository, you can just navigate to the directory and run: