Testing and Quality Assurance

Hi all,

Say I have a module A, which has some features which work with module B, but module B is not a dependency.

To test said features, I create a whole new "Test A B" module whose sole purpose is to have module A and module B as a dependency, and run tests against features which require both. "Test A B" module is stored in the "tests" subfolder of module A.

Wondering if that's the best approach, and if you are using any others.

Thanks,

Albert.

Hi there, testing team! :)

Back at DrupalCon Chicago, Dries outlined a strategy for Drupal 8 involving a series of "gates" that would help ensure core code quality in a number of different categories: Documentation, Performance, Accessibility, Usability, and Testing. The purpose of gates is to define essentially a set of "checkboxes" which outline the most important aspects to each category, and does so in a way that is both not overwhelming to core developers (list of hoops to jump through is kept as small as possible) and also creates very little additional burden on the team in question (contains sample links to documentation/resources so developers/reviewers can help themselves).

Since we have already traditionally had requirements around documentation, it made sense to start there. Jennifer Hodgdon and some other folks from the documentation team have put together the Documentation gate, which is available at http://drupal.org/node/1203498. What we need is a similar table for each of the other gate areas. And that's where you come in! :D

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.

The steps involved in taking forward the Selenium test for Drupal.org initiative:

Link to drupal.org issue queue: http://drupal.org/node/991040

• Identifying a groups of people interested in building Selenium test-cases
• Working on Identifying critical tests
• Writing tests
• Working with the infrastructure team to run these tests

If you are interested in building Selenium tests and supporting the same, please add you name and the area of support.

Implementers:

Hi all,

We have a client that is looking for a company to provide stress testing services for a web application. Any recommendations would be passed on directly to the client.

Experience working with and tuning LAMP/Drupal would be a big plus as they have limited staff experience in this area.

Please contact me through the contact form. Thanks!

Ezra Wolfe
DLC Solutions LLC

Why should you read this article?

• Developer, Team Leader, Admin:
• You will find out how to use build script that will save your time, spend on configuration of your project on dev, test, stage and production servers, on local computers of managers and testers. 
• Build script will allow you to make CI system and get all profits it gaves you.
• Manager:
• You have a lot of project in same time, and want to install in on local comp easily.
• You will get standart way to install projects on some machine in one click. To install new project you have to run $ant in console. Do this on local machine.
• You can demo machine with Husdon and build script. It will allow you allways have actual version of project to test and to show to client.
• Tester, QA manager:
• You have a lot of project in same time, and want to install in on local comp easily.
• You will get standart way to install projects on some machine in one click. To install new project you have to run $ant in console. Do this on local machine.
• You can make CI, add there tests and have regression testing easily.

Project page

ci-drupal

i am using simpletest with a multilingual drupal 6 site. whenever simpletest executes a link, by using clickLink or drupalLogin for example, the url gets corrupted.

this is because the language code always appears twice in the url. for example: http://example.com/de/de/node.

i was wondering if someone else ran into this issue when testing a multilingual site with simpletest? do you know of any workarrounds / fixes to this issue? (http://drupal.org/node/944066)

thanks a lot,
josef

Is there any site or group where it is appropriate to post questions about using SimpleTest? I'm currently struggling with SimpleTest performance on Windows. A DrupalWebTestCase takes many minutes to execute and I can't figure out if this is expected or what to start changing. I'd like to find somewhere that people have described how they've setup their Drupal environment to do TDD.

I am freakin' excited!

I got tired of switching between tabs and firebug when trying to figure out what the hell was going on with my Ajax requests.

So I wrote a jQuery Plug-in. You attach it to your page and it will monitor all your Ajax requests[1].