From 8e4e7026b4c3d8fc3b752d96740a36171e7ce935 Mon Sep 17 00:00:00 2001 From: Dennis Eichhorn Date: Tue, 30 Apr 2024 04:40:34 +0200 Subject: [PATCH] Update 01_Development.md Signed-off-by: Dennis Eichhorn --- Processes/01_Development.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Processes/01_Development.md b/Processes/01_Development.md index de47d19..5043f18 100644 --- a/Processes/01_Development.md +++ b/Processes/01_Development.md @@ -111,6 +111,15 @@ While UI tests can be part of unit, integration or system tests the `cssOMS` rep In the demo application it is possible to highlight html and css warnings (e.g. missing attributes, deprecated tags, inline styles, ...). In order to activate the live debugging add `&debug=true` to the end of your url. +In the demo application it is also possible to generate a list of html and css warnings by running a script which automatically traverses the application and searches for potentially bad html or css. + +1. Open the website in your browser +2. Log into the (demo) application +3. Copy the entire content of `tests/Web/Backend/Debug.js` +4. Paste the content into the console in your browser and press enter +5. Wait until the browser is done loading all the pages (see limit pageLimit) +6. At the end of the console output you should find a table with stats regarding potentially problematic html/css + #### Demo Some code changes may also require changes or extensions in the demo setup scripts. The demo setup script tries to simulate a "real world" use case by generating and modifying mostly random data. This is also a good way to setup and “manually” test the code changes in a larger picture. The demo setup script can be found in the [demoSetup](https://github.com/Karaka-Management/demoSetup) repository. The demo setup script takes a long time due to the large amount of user input simulated data which is generated. Therefore it is recommended to run this only sporadically. (**R9**)