Accueil / Taxonomy term

testing

What is Capgemini doing to contribute to Drupal?

Jacob Singh's picture

Drupal's massive growth has attracted some true global giants to our community. Capgemini is a 100k+ person consulting firm with over 35k employees in India. Apart from Capgemini's established reputation as a leader in large scale Drupal implementations and a preferred Acquia partner, they are now also actively contributing to the community through drupal.org testing efforts.

The Capgemini drupal.org contribution team consists of three developers with Drupal and PHP backgrounds, an architect and a manager. My email interview with them follows

How we test Acquia Cloud

Barry Jaspan's picture

Continuous Integration (CI) is powerful approach for improving software development and release engineering. Acquia Cloud provides a turn-key CI environment for our customers web applications. One important component of the CI process is automated tested, and Acquia Cloud makes it easy for our customers to run automated tests on their sites.

How Acquia Tests Software (via uTest)

Stellina McKinney's picture

I started at Acquia 6 months ago, having previously worked for larger, process-heavy corporations that sold packaged proprietary, software with long release cycles. Our QA teams consisted of over 50 people (sometimes a lot more), and were always the long pole in the process, whether it was Agile or Waterfall.

Not so at Acquia.

At Acquia, I manage a lean QA team of 4 people (we have another team that tests usability), and we support 5 products. We work in an Agile environment, release every 3 weeks, and meet our quality goals for each sprint.

Part 1: Drop everything and Help module maintainers fulfill their d7cx pledge

Heather James's picture

Drupal 7 RC 1 needs testers. And now more than ever, your favorite modules need testing too. As Moshe wrote yesterday, they're here to collect on the D7CX pledge. This is a great way that a new Drupal user can make a significant contribution, and make some friends in the process :)

I was amazed at the most recent DrupalCamp in Ireland that some people I spoke to weren't trying out Drupal 7 yet. I've been using Gardens so much, I adore D7 and get all itchy when I use D6. Come in, the water's fine!

Well, except that many of your favorite modules aren't quite ready yet. Many module maintainers took the D7CX pledge to be ready for the release of Drupal 7. That looks to be in about 7-10 days! There's a mad rush on and even as a non-coder, or a new user to Drupal you can help.

Download Drupal 7, and test your favorite modules. Report bugs and submit patches! It's easy, right? I'll be making a few posts this week to take "the scary" out of testing patches, and show you exactly how I do it. In this post, we'll get D7 up and running, and determine the best way to locate modules which need help, and the specific issues which need testing.

Calculating test coverage

d hubler's picture

Here's how you can determine test coverage of your tests by generating a report like this one:
http://acquia.com/files/test-results/index.html

Step 1: Install xdebug php extension. On ubuntu I run
apt-get install php5-xdebug

Step 2: Checkout simpletest trunk anywhere on your disk. In this example I will choose /usr/local/simpletest
svn co \  https://simpletest.svn.sourceforge.net/svnroot/simpletest/simpletest/trunk \ /usr/local/simpletest

Step 3: Add simpletest to the php.ini loaded by apache.

Drupal CLI utils

d hubler's picture

I put together a few scripts that I needed to configure and manage drupal from CLI.

They include the following scripts:
- Installer (install.php D6 & D7)
- Updater (update.php)
- Code Coverage (working example: http://acquia.com/latest-drupal-test-results)
- Unit Test Runner (run-tests.sh)
- Module enabler

and the following library code:
- CLI arg parser
- Drupal Web Form User Agent (uses php-curl)

additional points:
- Much of the code has unit tests (simpletest, php-mock-functions w/o runkit)
- Code was designed to be extended for custom purposes.

Minnesota Search Sprint: Your top-five feature requests

Robert Douglass's picture

In the same way that the Internet itself would not have achieved greatness without the ability to search it easily and efficiently, Drupal's greatness will always be tied directly to the effectiveness of its core search solution. Improving core search for Drupal 7 will be no small task, however. The current implementation is both elegant but complex, robust yet inflexible. The seven coders participating in the Minnesota Search Sprint this weekend have a great challenge as well as a great opportunity. Here are some of the things we hope to achieve:

- Identify the most important weaknesses in Drupal search and create a project plan for fixing them.
- Identify the most important new features currently missing from Drupal search and clear the roadblocks for implementing them.
- Increase the test coverage for Drupal search.
- Increase general developer awareness and knowledge of search.

A large part of what we will be doing is evaluating and planning. Without a roadmap and common understanding of what search is to become, little progress will be made in the Drupal 7 development cycle. However, a coding sprint is all about code, and we'll be writing some of that, too. Specifically I'm hoping that we'll be able to fix one of the top-five bugs, increase search module's test coverage, and come up with a first attempt at one of the top-five new features.

That's a lot! No matter what we manage to code during the three days together, we'll walk away with a high level of agreement about our goals for the next months, and plenty of homework to do.

We'll post regular updates that you can follow on Planet Drupal, as well as in the search group, and we're all ears if you have suggestions or wishes. For anyone wanting to catch up on their search related reading, here are some links: