Testing and Quality Assurance

We've been working on implementing continuous integration for our projects to improve code quality. In the process we've built two templates which should make it easy to setup CI for new projects and want to share these with the community. Hopefully you'll find it useful!

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,

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.

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.