CM6: Further fixes/improvements after testing

[bookstack] / dev / docs / development.md

diff --git a/dev/docs/development.md b/dev/docs/development.md
index 6d11443b63705b70858c55c3b7465dfb56b6c62b..b68f2664aa38762df7743f8628e4dc474bcf3c6e 100644 (file)
--- a/dev/docs/development.md
+++ b/dev/docs/development.md
@@ -5,6 +5,8 @@ When it's time for a release the `development` branch is merged into release wit
 
 * [Node.js](https://nodejs.org/en/) v16.0+
 
+## Building CSS & JavaScript Assets
+
 This project uses SASS for CSS development and this is built, along with the JavaScript, using a range of npm scripts. The below npm commands can be used to install the dependencies & run the build tasks:
 
 ``` bash
@@ -27,6 +29,8 @@ The testing database will also need migrating and seeding beforehand. This can b
 
 Once done you can run `composer test` in the application root directory to run all tests. Tests can be ran in parallel by running them via `composer t`. This will use Laravel's built-in parallel testing functionality, and attempt to create and seed a database instance for each testing thread. If required these parallel testing instances can be reset, before testing again, by running `composer t-reset`.
 
+If the codebase needs to be tested with deprecations, this can be done via uncommenting the relevant line within the TestCase@setUp function. 
+
 ## Code Standards
 
 PHP code standards are managed by [using PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer).