From ad2094676d7223d455dd19dc5da569158c3f929c Mon Sep 17 00:00:00 2001 From: David Persson Date: Thu, 14 Jul 2016 14:55:32 +0200 Subject: [PATCH] Move Security below Quality; reword Quality README. --- .../01_security.md | 0 .../{01_testing.md => 02_testing.md} | 0 .../{02_analysis.md => 03_analysis.md} | 0 08_quality_code/README.md | 18 +++++++++++++----- 4 files changed, 13 insertions(+), 5 deletions(-) rename 10_security.md => 08_quality_code/01_security.md (100%) rename 08_quality_code/{01_testing.md => 02_testing.md} (100%) rename 08_quality_code/{02_analysis.md => 03_analysis.md} (100%) diff --git a/10_security.md b/08_quality_code/01_security.md similarity index 100% rename from 10_security.md rename to 08_quality_code/01_security.md diff --git a/08_quality_code/01_testing.md b/08_quality_code/02_testing.md similarity index 100% rename from 08_quality_code/01_testing.md rename to 08_quality_code/02_testing.md diff --git a/08_quality_code/02_analysis.md b/08_quality_code/03_analysis.md similarity index 100% rename from 08_quality_code/02_analysis.md rename to 08_quality_code/03_analysis.md diff --git a/08_quality_code/README.md b/08_quality_code/README.md index 84a2126..ebe7ffd 100644 --- a/08_quality_code/README.md +++ b/08_quality_code/README.md @@ -1,12 +1,20 @@ # Quality Code -Clean, quality and well tested code are a fundamental goals of li3. +Clean, roboust and well tested code are fundamental goals of the framework. -Li3 adheres to coding, testing and documentation standards which can be found inside the -dedicated [specs documentation repository](/docs/specs/latest:1.x). [Static analysis](analysis) -tools are used to detect standards violations. +li₃ adheres to +[coding](/docs/book/specs/latest:1.x/accepted/LSR-0-coding), +[testing](/docs/book/specs/latest:1.x/accepted/LSR-2-testing), +and [documentation](/docs/book/specs/latest:1.x/accepted/LSR-1-documenting) +standards which can be found inside the +[specs documentation repository](/docs/book/specs/latest:1.x). -Learn more about testing in li3 in the [Unit Testing](testing) chapter. +[Static code analysis](analysis) tools are used to detect standards violations. + +Learn how to write unit, integration and functional tests in the [Testing](testing) chapter. + +To make you application as robost to potential security threads as possible, follow the +[Securing Applications](security) guide.