From 230230819eb8a10be5eda01ee646acd8ce57c796 Mon Sep 17 00:00:00 2001 From: bbbradsmith Date: Fri, 24 Feb 2023 19:35:38 -0500 Subject: [PATCH] document the undocumented test/asm/listing behaviours --- test/asm/listing/readme.txt | 30 +++++++++++++++++++++++------- 1 file changed, 23 insertions(+), 7 deletions(-) diff --git a/test/asm/listing/readme.txt b/test/asm/listing/readme.txt index e43f2008a..d6280b954 100644 --- a/test/asm/listing/readme.txt +++ b/test/asm/listing/readme.txt @@ -6,22 +6,38 @@ The name of a test is everything in the form .s. The following reference files can be added: -- .bin-ref: +- ref/.bin-ref: This is a reference for the resulting binary. The binary as binary tested against this file. If they are not equal, the test fails. -- .list-ref +- ref/.list-ref This is a reference for the resulting listing output This file *must* have the first line of the listing removed, as that contains a ca65 version string, and almost always this will be changed! +- ref/.err-ref + This is a reference for the resulting ca65 stdout (>) output. + +- ref/.err2-ref + This is a reference for the resulting ca65 stderr (2>) output. + +- ref/.ld65err-ref + This is a reference for the resutling ld65 stdout (>) output. + +- ref/.ld65err2-ref + This is a reference for the resulting ld65 stderr (2>) output. + +The following control files can be added to control the tests. +These files are empty (contents ignored), and only the filename is used: + +- control/.err + Test is expected to produce an error. + +- control/.no-ld65 + Skip the ld65 step. + Note that the resulting .bin file is generated twice: Once with no listing file, and once with listing file. This way, one can find out if the listing file generation changes anything with the resulting binary output. - - -TODO: -- add the possibility to test for specific error output that are to be - expected