From 768d1b13bef0f27a00d169b9de479e29b843998b Mon Sep 17 00:00:00 2001 From: Zoltan Varga Date: Sat, 26 Jan 2008 21:46:05 +0000 Subject: [PATCH] 2008-01-26 Zoltan Varga * docs/mini-porting.txt: Add some info about the order the JIT regression tests should be run. svn path=/trunk/mono/; revision=94026 --- ChangeLog | 5 +++++ docs/mini-porting.txt | 17 +++++++++++++++++ 2 files changed, 22 insertions(+) diff --git a/ChangeLog b/ChangeLog index a06cae445be..7005b4a5a14 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2008-01-26 Zoltan Varga + + * docs/mini-porting.txt: Add some info about the order the JIT regression + tests should be run. + 2008-01-26 Daniel Nauck * scripts/mono-service.in: fix compability with the dash shell, diff --git a/docs/mini-porting.txt b/docs/mini-porting.txt index acca411cdbb..cdb967d3d9e 100644 --- a/docs/mini-porting.txt +++ b/docs/mini-porting.txt @@ -415,6 +415,23 @@ *) mono_arch_instrument_epilog () Functions needed to implement the profiling interface. +* Testing the port + + The JIT has a set of regression tests in *.cs files inside the mini directory. + The usual method of testing a port is by compiling these tests on another machine + with a working runtime by typing 'make rcheck', then copying TestDriver.dll and + *.exe to the mini directory. The tests can be run by typing: + ./mono --regression + The suggested order for working through these tests is the following: + - basic.exe + - basic-long.exe + - basic-float.exe + - basic-calls.exe + - objects.exe + - arrays.exe + - exceptions.exe + - iltests.exe + - generics.exe * Writing regression tests -- 2.25.1