Add another type of tests: testing that WLA's/WLALINK's verbose mode's output contains a string

[vhelin]

This is something we'd need in "tests/z80/ram_sections_2".

Currently the output is:

-------------------------------------------------
---                   ROM                     ---
-------------------------------------------------
ROM bank 0 (16384 bytes (100.00%) free)
  - Free space at $0000-$3fff (16384 bytes)
ROM bank 1 (16384 bytes (100.00%) free)
  - Free space at $0000-$3fff (16384 bytes)
ROM bank 2 (16384 bytes (100.00%) free)
  - Free space at $0000-$3fff (16384 bytes)
ROM bank 3 (16384 bytes (100.00%) free)
  - Free space at $0000-$3fff (16384 bytes)
-------------------------------------------------
---                   RAM                     ---
-------------------------------------------------
RAM slot 4 bank 1 (4096 bytes (50.00%) free)
  - Free space at $1000-$1fff (4096 bytes)
-------------------------------------------------
---           HEADERS AND FOOTERS             ---
-------------------------------------------------
No headers or footers found.
-------------------------------------------------
---                 SUMMARY                   ---
-------------------------------------------------
ROM: 65536 bytes (100.00%) free of total 65536.
RAM: 4096 bytes (50.00%) free of total 8192.

What in this test is important that the last line reads:

RAM: 4096 bytes (50.00%) free of total 8192.

It'd be great if we could create a test that'd verify this.

[jeffythedragonslayer]

We can tail the output and then grep for that line. It would be helpful if CONTRIBUTING.md contained instructions on how to add tests.

[vhelin]

Quick note about adding tests:

a) Clone an existing test directory and modify it
or
b) Insert tests into existing test source files / makefiles

No need to list the new tests anywhere, a directory inside tests is considered one test directory

But sure, CONTRIBUTING.md should be updated about this...

[jeffythedragonslayer]

Does the test harness require us to create makefiles for tests though? I feel like this test can be done in a bash script.

[vhelin]

Yep, every test folder needs to have a makefile that runs the test. Just make a makefile to run the bash script…

…

On Tue, 21 Feb 2023 at 20:06, Jeff Linahan ***@***.***> wrote: Does the test harness require us to create makefiles for tests though? I feel like this test can be done in a bash script. — Reply to this email directly, view it on GitHub <#485 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ62UWPRD3R3M354XMC74LWYT723ANCNFSM5PLPS2JA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jeffythedragonslayer]

FYI, those contributing instructions we added got squashed onto a single line when viewed with the github markdown viewer:

perhaps we should stick with bullet points

[vhelin]

Maybe, but I can live with this