Incomplete

Running Tests Through command-line

Command-line test execution - Linux

This section is for the those that have the desire and/or the need to run the test-suite by command-line. This is often needed when one wants to integrate 3rd-party continuous-build tools, for example. I am hoping this page will collect info and tips on the manual aspects of testing, when one is doing it small-scale and only wants to test one or a few modules.

For those looking for info on the gui way of running simpletest, head for the Simpletest tutorial, lower down in that tutorial you will some information for running tests through drupal interface. The two important links for command-line commandos accessing simple-test through Drupal interface are admin/config/development/testing/ and admin/config/development/testing/results/

Running the tests through the command line in Drupal is quite easy with the help of run-tests.sh, located in /scripts. One can easily get the test-suite running by going to the root of the site directory, as web-server user and typing php scripts/run-tests.sh.

If you don't feel like typing /scripts/run-tests.sh all the time, symlink the script to your ~/bin directory, assuming you have an existing bin directory that is in your path:

ln - s scripts/run-tests.sh ~/bin

Rules: Rules Executor

Last modified: November 28, 2009 - 08:54

This is a holding page for documentation about the Rules Executor module

Comparison of modules for dealing with troublesome users

Last modified: December 14, 2009 - 20:10

This article attempts to do a comparison between modules able to deal with troublesome users. This article should allow you to choose which module best suits your needs.

What is a troublesome users?

Comparison of email newsletter oriented modules

Last modified: November 28, 2009 - 00:31

Sending newsletters with site updates is a common task, as is sending out one off special notifications. Which module is the best choice?

User friendly paths

Last modified: November 25, 2009 - 22:10

Publications do not have a URL setting. You have to define a URL alias. epublish/1 becomes d-theme_da_newsletter. You can hand out http://d-theme.com/d-theme_da_newsletter as a link people can use to see your newsletters. Perhaps publication could be changed to a node type so that URL aliases will be standard.

The breadcrumb incorrectly shows you at Home » D-theme Da Newsletter » Volume 9. The only thing I can think of is that when you set an edition as current, you are sent to the current edition. If I turn off current edition, the breadcrumb does not change. There are issues posted for breadcrumbs.

Editions have URL aliases. You can add a URL path settings when creating or editing an edition. The alias was not used in my one test.

I have not tested sections and topics. Please add your experience.

Section and topic content is added as normal content nodes. Those nodes can have their own URL. When referred to in an edition, there should be a named anchor for each session and topic. Using the example of a section New themes in the example newsletter d-theme_da_newsletter and december_2009, we should be able to refer to:
http://d-theme.com/d-theme_da_newsletter/december_2009#new_themes
or

E-publish

Last modified: November 25, 2009 - 06:51

Download E-publish from http://drupal.org/project/epublish. You will also need http://drupal.org/project/select_publication. You can now assign nodes to publications with editions and sections within editions and topics within sections.

Syndicate content
 
 

Drupal is a registered trademark of Dries Buytaert.