Decoupled components used by the Lightning distribution for Drupal.
Using the lightning_features module in your own install profile's is recommended.
FAQ
- If you are not using a module and no lightning_features modules inuse require it as a dependency, it could be deleted from your project with a patch for lightning_features.make
- You will not see any performance decrease on your delivery if you leave uninstalled modules in your profiles directory.
- We recommend evaluating each lightning_* module for your own usage and only using the things you deem necessary.
See lightning_features.make for a detailed list of dependent modules and libraries.
If you downloaded the Lightning Demo from http://drupal.org/project/lightning
cd profiles/lightning/modules/contrib
rm -rf lightning_features
git clone --branch 7.x-1.x http://git.drupal.org/project/lightning_features.git
Or download the latest package from http://drupal.org/project/lightning_features
cd lightning_features
sh update.sh
If you built your own profile using Lightning Features: you must keep lightning_features and the contrib it provides in profiles/[my-profile]/modules/contrib otherwise the update.sh script will not run correctly.
Replace the first step in updating using the appropriate profile directory.
cd profiles/[my-profile]/modules/contrib
Move the tests folder to your Drupal docroot.
mv lightning_features/tests docroot/tests
Install the drupal-extension for mink/behat from the tests folder.
cd tests && composer install
Set up the behat.local.yml file replacing BASE_URL
with your own url.
cp behat.local.example.yml behat.local.yml
Check that behat is installed and running under the dev profile.
bin/behat --help --profile=dev
Execute the Lightning Features scenarios using the "dev" Behat profile.
bin/behat --tags=lightning --profile=dev
- Article content type exists
- Creating an article as admin
- Article content type has fields provided by feature
- Checks to ensure breakpoints were created
- Checks to ensure Views Content Cache is enabled
- Text formats exist
- Text formats have appropriate feature-defined filters
- Webform type present
- Can create Webform
- Check basic Webform fields
- Checks for FPP types
- Checks for fields on FPP types
- Checks to ensure taxonomy exists
- Ensure landing page content type exists
- Create landing page content
- Landing Page fields
- Checks for letterbox breakpoints
- Ensure moderation steps are created
- Ensure page content type exists
- Create page content
- Page fields
- Role exists: curator
- Role exists: reviewer
- Role exists: marketer
- Checks for Article field collection
- Tags taxonomy vocabulary exists
- WYSIWYG Configuration sanity check