Recent changes to Test

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 18 May 2021 10:32:01 -0000

--- v7
+++ v8
@@ -17,7 +17,7 @@
 These tests live in sim/ucsim/\*.src/test; their purpose is to spot regressions in the uCsim simulator.

 ** historygraphs **
-These live in ../sdcc-extra/historygraphs. Four benchmarks (Whetstone, Dhrystone, Coremark, stdcbench) can be compiled for and executed for three targets (mcs51, stm8, r3ka). The graphs produced show score and code size over time.
+These live in ../sdcc-extra/historygraphs. Four benchmarks (Whetstone, Dhrystone, Coremark, stdcbench) can be compiled for and executed for three targets (mcs51, stm8, r3ka). The graphs produced show benchmark score and code size over time. They can help spot performance and code size regressions.

 ** Limited regression tests **
 These tests live in src/regression; these few tests have much lower coverage than the real regression tests, and are only used for the pic14 and pic16 ports. This infrastructure could be removed when pic14 and pic16 pass the real regression tests.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 18 May 2021 10:31:20 -0000

--- v6
+++ v7
@@ -14,7 +14,7 @@
 The [Distributed Compile Farm] executes these tests nightly on various host systems. Results can be seen on the [Snapshots page](http://sdcc.sourceforge.net/snap.php) via the green (all tests passed, including regression tests) or red (some tests failed) dot.

 ** uCsim regression test **
-These tests live in sim/ucsim/\*.src/test; their purpose is to sport regressions in the uCsim simulator.
+These tests live in sim/ucsim/\*.src/test; their purpose is to spot regressions in the uCsim simulator.

 ** historygraphs **
 These live in ../sdcc-extra/historygraphs. Four benchmarks (Whetstone, Dhrystone, Coremark, stdcbench) can be compiled for and executed for three targets (mcs51, stm8, r3ka). The graphs produced show score and code size over time.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Wed, 21 Apr 2021 20:28:09 -0000

--- v5
+++ v6
@@ -16,6 +16,9 @@
 ** uCsim regression test **
 These tests live in sim/ucsim/\*.src/test; their purpose is to sport regressions in the uCsim simulator.

+** historygraphs **
+These live in ../sdcc-extra/historygraphs. Four benchmarks (Whetstone, Dhrystone, Coremark, stdcbench) can be compiled for and executed for three targets (mcs51, stm8, r3ka). The graphs produced show score and code size over time.
+
 ** Limited regression tests **
 These tests live in src/regression; these few tests have much lower coverage than the real regression tests, and are only used for the pic14 and pic16 ports. This infrastructure could be removed when pic14 and pic16 pass the real regression tests.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 20 Apr 2021 15:24:52 -0000

--- v4
+++ v5
@@ -1,8 +1,9 @@
-There is various infrastructure for testing sdcc and its components:
 #Test

+There is various infrastructure for testing sdcc and its components:
+
 ** Regression tests **
-The most important aspect is [Regression Testing]: This infrastructure, which lives in sdcc/support/regression is used to compile and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets. 
+The most important aspect is [Regression Testing]: This infrastructure, which lives in sdcc/support/regression is used to compile, assemble and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets. 
 The purpose of these tests is to ensure that sdcc compiles all the tests into correct code. Individual tests are usually derived from fixed bugs, new features or tests from other projects.

 The [Distributed Compile Farm] executes these tests nightly on various host systems. Results can be seen on the [Snapshots page](http://sdcc.sourceforge.net/snap.php) via the green (all tests passed, including valdiag) or red (some tests failed) dot.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 20 Apr 2021 15:24:09 -0000

--- v3
+++ v4
@@ -5,12 +5,12 @@
 The most important aspect is [Regression Testing]: This infrastructure, which lives in sdcc/support/regression is used to compile and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets. 
 The purpose of these tests is to ensure that sdcc compiles all the tests into correct code. Individual tests are usually derived from fixed bugs, new features or tests from other projects.

-The [Distributed Compile Farm] executes these tests nightly on various host systems.
+The [Distributed Compile Farm] executes these tests nightly on various host systems. Results can be seen on the [Snapshots page](http://sdcc.sourceforge.net/snap.php) via the green (all tests passed, including valdiag) or red (some tests failed) dot.

 ** valdiag tests **
 This infrastructure, which lives in support/valdiag compiles some tests and checks that diagnostics (errors and warnings) are emitted correctly.

-The [Distributed Compile Farm] executes these tests nightly on various host systems.
+The [Distributed Compile Farm] executes these tests nightly on various host systems. Results can be seen on the [Snapshots page](http://sdcc.sourceforge.net/snap.php) via the green (all tests passed, including regression tests) or red (some tests failed) dot.

 ** uCsim regression test **
 These tests live in sim/ucsim/\*.src/test; their purpose is to sport regressions in the uCsim simulator.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 20 Apr 2021 15:22:22 -0000

--- v2
+++ v3
@@ -5,12 +5,12 @@
 The most important aspect is [Regression Testing]: This infrastructure, which lives in sdcc/support/regression is used to compile and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets. 
 The purpose of these tests is to ensure that sdcc compiles all the tests into correct code. Individual tests are usually derived from fixed bugs, new features or tests from other projects.

-The [Distributed Compile farm] executes these tests nightly on various host systems.
+The [Distributed Compile Farm] executes these tests nightly on various host systems.

 ** valdiag tests **
 This infrastructure, which lives in support/valdiag compiles some tests and checks that diagnostics (errors and warnings) are emitted correctly.

-The [Distributed Compile farm] executes these tests nightly on various host systems.
+The [Distributed Compile Farm] executes these tests nightly on various host systems.

 ** uCsim regression test **
 These tests live in sim/ucsim/\*.src/test; their purpose is to sport regressions in the uCsim simulator.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 20 Apr 2021 15:22:02 -0000

--- v1
+++ v2
@@ -1,15 +1,16 @@
 There is various infrastructure for testing sdcc and its components:
+#Test

 ** Regression tests **
-The most important aspect is [[Regression Testing]]: This infrastructure, which lives in sdcc/support/regression is used to compile and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets. 
+The most important aspect is [Regression Testing]: This infrastructure, which lives in sdcc/support/regression is used to compile and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets. 
 The purpose of these tests is to ensure that sdcc compiles all the tests into correct code. Individual tests are usually derived from fixed bugs, new features or tests from other projects.

-The [[Distributed Compile farm]] executes these tests nightly on various host systems.
+The [Distributed Compile farm] executes these tests nightly on various host systems.

 ** valdiag tests **
 This infrastructure, which lives in support/valdiag compiles some tests and checks that diagnostics (errors and warnings) are emitted correctly.

-The [[Distributed Compile farm]] executes these tests nightly on various host systems.
+The [Distributed Compile farm] executes these tests nightly on various host systems.

 ** uCsim regression test **
 These tests live in sim/ucsim/\*.src/test; their purpose is to sport regressions in the uCsim simulator.

Test modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 20 Apr 2021 15:21:17 -0000

There is various infrastructure for testing sdcc and its components:

Regression tests
The most important aspect is [[Regression Testing]]: This infrastructure, which lives in sdcc/support/regression is used to compile and execute (via simulators, mostly uCsim) a large number of tests, for all stable targets.
The purpose of these tests is to ensure that sdcc compiles all the tests into correct code. Individual tests are usually derived from fixed bugs, new features or tests from other projects.

The [[Distributed Compile farm]] executes these tests nightly on various host systems.

valdiag tests
This infrastructure, which lives in support/valdiag compiles some tests and checks that diagnostics (errors and warnings) are emitted correctly.

The [[Distributed Compile farm]] executes these tests nightly on various host systems.

uCsim regression test
These tests live in sim/ucsim/*.src/test; their purpose is to sport regressions in the uCsim simulator.

Limited regression tests
These tests live in src/regression; these few tests have much lower coverage than the real regression tests, and are only used for the pic14 and pic16 ports. This infrastructure could be removed when pic14 and pic16 pass the real regression tests.