testing

A collection of resources to learn how to write tests for Drupal.

A collection of resources to learn how to write tests for Drupal.

The Drupal Association staff just gave a demo to a few of the core committers of the new MVP of the DrupalCI project. Here are some screenshots I took along the way to show how it will work!

The Drupal Association staff just gave a demo to a few of the core committers of the new MVP of the DrupalCI project. Here are some screenshots I took along the way to show how it will work!

The main goal for Karma is to bring a productive testing environment to developers. The environment being one where they don't have to set up loads of configurations, but rather a place where developers can just write the code and get instant feedback from their tests. Because getting quick feedback is what makes you productive and creative.

The padlock module is designed to limit the functionality of Drupal forms by setting a validation error unless the form is allowed to be submitted in the module configuration. The module also provides a permission to bypass the padlock validation for roles with the elevated permission. Use Cases: Integration / Staging Sites / Training Sites Testing deployment scripts and processes. Allow the review of a form without the submission of the form. Locking specific forms without removing the entire permission set for that role.

Drupal 8 ready: drupal_ti supports both Drupal 7 and 8 modules. Use DRUPAL_TI_ENVIRONMENT="drupal-8" for your Drupal 8 modules. Tested: drupal_ti tests its own code base for both Drupal 7 and Drupal 8 modules. Modular architecture: drupal_ti has so called 'runners' and you can combine either e.g. "phpunit simpletest" or run them as separate workers by specifying a matrix. Environment aware: drupal_ti has a file for each environment, which makes the code generic for both Drupal 7 and 8.

Test versions of IE using Virtual Machines that you download and manage in your own development environment.

We organized the usability issues into four different layers: conceptual, flow, terminology, and interface. In this document we explain what each of these means, and provide key examples and quotes from users. We also propose a quick and concise up-to-speed aid that welcomes users on a new Drupal installation.

see also: http://drupal.org/node/1427940