Difference between revisions of "Compiler test suite"
From Lazarus wiki
Jump to navigationJump to search (Info on what it does) |
m |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Compiler_test_suite}} | ||
| + | |||
== Overview == | == Overview == | ||
The "compiler test suite" contains tests that exercise the compiler, but also several core packages and bug reports to test against regressions. | The "compiler test suite" contains tests that exercise the compiler, but also several core packages and bug reports to test against regressions. | ||
| Line 8: | Line 10: | ||
It can output results to text file as well as to database according to that file. | It can output results to text file as well as to database according to that file. | ||
| − | The compiler test suite is a good candidate for running in an automated fashion. One way to get this done is to set up [[ | + | The compiler test suite is a good candidate for running in an automated fashion. One way to get this done is to set up [[Jenkins]]. |
== Results == | == Results == | ||
| Line 14: | Line 16: | ||
http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi | http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi | ||
| − | |||
| − | |||
Latest revision as of 09:48, 19 October 2017
│
English (en) │
français (fr) │
Overview
The "compiler test suite" contains tests that exercise the compiler, but also several core packages and bug reports to test against regressions. They are located in the tests directory in the FPC source code.
Running the tests
Please see tests/readme.txt for details on how to run the compiler test suite.
It can output results to text file as well as to database according to that file.
The compiler test suite is a good candidate for running in an automated fashion. One way to get this done is to set up Jenkins.
Results
The compiler test suite is run regularly on developer machines and the results documented here:
