49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
# TDD Dublin demo module
|
|
|
|
A demo module to accompany my [TDD - Test Driven Drupal][0] talk at DrupalCamp
|
|
Dublin 2017.
|
|
|
|
In order to see my workflow of writing comments first, converting them into
|
|
failing tests, and then writing the implementation code to make them pass, you
|
|
can see the [list of previous commits][1] and see each step taken, as well as
|
|
[the tags][2] that identify the commits when each failing test is added and
|
|
then subsequently passes.
|
|
|
|
## Acceptance Criteria
|
|
|
|
This module will be used to demonstrate how to take a test-driven approach to
|
|
develop a module to the following acceptance criteria:
|
|
|
|
- As a site visitor
|
|
- I want to see a list of all published pages at `/pages`
|
|
- Ordered alphabetically by title
|
|
|
|
## Running the Tests
|
|
|
|
These tests are functional tests based on the `BrowserTestBase` class so need
|
|
to be executed with PHPUnit (which is required in core's `composer.json` file).
|
|
The path to your `vendor` directory may be different depending on your setup.
|
|
|
|
Because of autoloading, you will need to be inside Drupal's `core` subdirectory
|
|
when running the tests for them to execute successfully.
|
|
|
|
This also assumes that the module is within a `modules/custom` directory and
|
|
named `tdd_dublin` as per the repository name.
|
|
|
|
```
|
|
cd core
|
|
|
|
../vendor/bin/phpunit ../modules/custom/tdd_dublin
|
|
```
|
|
|
|
You can use PHPUnit's `--filter` option to specify a single test method to run,
|
|
rather than all of the tests within the module. For example:
|
|
|
|
```
|
|
../vendor/bin/phpunit ../modules/custom/tdd_dublin --filter=testOnlyPublishedPagesAreShown
|
|
```
|
|
|
|
[0]: https://www.oliverdavies.uk/talks/tdd-test-driven-drupal
|
|
[1]: https://github.com/opdavies/tdd_dublin/commits/HEAD
|
|
[2]: https://github.com/opdavies/tdd_dublin/tags
|