Go to file
Ingo Schommer e143204ae6 Regression on field labels
Auto-conversion was a bit too overzealous, and I failed at reviewing the diff properly.
2016-09-14 16:34:31 +12:00
_config Compat with SS4 namespaces 2016-09-07 17:10:55 +12:00
code Regression on field labels 2016-09-14 16:34:31 +12:00
css ENHANCEMENT Migrated Stig's GridfieldTest module into here 2012-02-29 15:10:34 +01:00
images MINOR: added sample sifr sample page image 2010-02-18 21:31:39 +00:00
templates/Layout Fixed deprecated template usage 2013-03-19 11:36:06 +01:00
_config.php Compat with SS4 namespaces 2016-09-07 17:10:55 +12:00
.editorconfig Added standard .editorconfig file 2015-12-17 10:58:06 +13:00
.scrutinizer.yml Added standard Scrutinizer config 2016-02-17 05:27:53 +13:00
.upgrade.yml Namespaced model to get more 4.x test coverage 2016-07-01 14:37:50 +12:00
code-of-conduct.md Added standard code of conduct file 2016-02-16 11:37:34 +13:00
composer.json 4.x compat 2016-04-19 09:27:29 +12:00
README.md BUGFIX Moved db switching to separate module which is included later in the manifest, which means it doesn't get overwritten by ConfigureFromEnv.php in mysite 2012-05-01 14:57:34 +02:00

Framework Test Module

Introduction

Aids core and module developers in testing their code against a set of sample data and behaviour.

  • Shows all core form fields, including their disabled and readonly state
  • Shows sample GridField instance including data
  • Creates sample members (to efficiently test SecurityAdmin)
  • Creates a sample ModelAdmin instance (available at admin/test)
  • (Optional) Three-step process for the multiform module
  • (Optional) Sample page for the tagfield module
  • (Optional) Sample page for the recaptcha module

Usage

Simply running dev/build will take care of most sample data setup.

In order to use any of the optional test behaviour targeted at modules, install the module and remove the _manifest_exclude file from the relevant folder. For example, to test the tagfield module, remove the frameworktest/code/tagfield/_manifest_exclude file.

More sample data

The module creates some default pages for different CMS behaviours. The CMS is intended to be perform well with a couple of thousand pages. If you want to test the CMS behaviour for a large and nested tree, the module includes a simple generator task: dev/tasks/FTPageMakerTask. It will create 3^5 pages by default, so takes a while to run through.

Requirements

The module is intended to run against the latest core codebase, but also includes branches matching earlier core releases for backwards compatibility.