Index	Manual	Download	Source	Macros	Embedded word Case ins.
	Sitemap	Links	Forum	Tests	Projects

€ASM tests
Anatomy of tests
HTML markers
Metainformation
Test management
Test Manager
Categories
Test list
Blocks
Strings
Numbers
Symbols
Symbol attributes
Literal symbols
Pseudoinstructions
Addressing modes
Machine instructions
OutputFile
Macros
Variables
Realmode segmentation
Linking
End of Test list
Linker combinations

Files in eatests directory are designed for semiautomatic testing of EuroAssembler itself. Test file names look like tNNNN.htm where NNNN are four decimal digits. All tests shipped with EuroAssembler are listed below.

↑ Anatomy of tests

Test is a HTML file which contains chunk with source code of a small program written in EuroAssembler, together with metainformation necessary for evaluation whether the test was assembled and linked as expected.
All files necessary to create the desired output file are parsed from the test HTML file, or they are assembled on the fly from auxilliary PROGRAM blocks in the beginning of the test source, and then they are linked to the final program.

Description of the test, the tested source code itself, auxilliary helper code, template of expected results, each piece of information required for testnig a particular EuroAssembler feature or function is encapsulated in a single HTML file. And if your home web server allows execution of local programs, the test can be edited and run directly from the browser. From security reason it is not a good idea to allow editing and launching of arbitrary code when the web server is accessible from internet.

↑ HTML markers

Each physical line of the test file is identified by its first nonwhite character.

• When the line starts with < and it is recognized as a HTML comment marker from the table below, it contributes to the corresponding metainformation division. Otherwise the line is ignored.
• Lines which do not start with an HTML tag < are treated as expected listing line, so they should start with machine comment character |.

↑ Divisions of metainformation

Divisions T,D,P,S are used as documentation in the test header and they are not required for testing.
Divisions A,I,J,K are present only in tests which check the performance of INCLUDE* statements.
Divisions E,B are used when the output object file should be compared with the expected contents.
Obtained listing and message output is always compared with the expected contents, so divisions L and M are mandatory. The other divisions may be omitted.

Ordinary tests of €ASM instructions are prescribed in the form of listing (division marker none), in this case the physical lines begin with machine comment | and the listing file serves simultaneously both as the test source and the expected listing template.

Most tests do not inspect the generated output file; checking of the listing file is sufficient for many assembly tasks, so divisions E,B are often omitted. Output file is checked only in tests of output file formating and linking.

Many of generated output files are executable, the test may be checked by running them. They usually write some information to console, make a beep and then terminate with errorlevel 0.

↑ Test management

Testing is controlled by test manager which will parse the test file, retrieve all metainformation and create temporary source files from divisions I,J,K,A. Then it executes the test.
Messages are captured from standard console output and compared with expected output M. Generated listing file is compared with expected listing L. If the test contains metainformation divisions E,B, the obtained output object file is converted to a hexadecimal dump and compared with expected dump B.

Test is declared passed if the obtained

1. standard console output
2. listing
3. output linked file (only when division E,B are present)

match the expected values. Test manager in this case deletes all temporary files of the test.
When the test failed, temporary files are not deleted and they should be optically inspected and either accepted as correct, or the bug in EuroAssembler fixed.

Tests can be performed with three methods:

Manually

This ad hoc method works only with tests which don't use divisions A,I,J,K, so the actual tested source is the test file itself. Otherwise you would have to create the corresponding temporary files t1234.asm, t1234.i.asm, t1234.j.asm t1234.k.asm manually, removing markers <!--A--> <!--I--> <!--J--> <!--K--> and all other lines from the test source.
Open the console window, change to eatests directory and execute for instance euroasm t1234.htm Then you should manually compare the obtained messages with those which are introduced in the test source with markers <!--M-->.
Similary, compare the obtained listing file t1234.htm.lst or t1234.asm.lst with expected listing lines which begin with vertical bar | in the test source file.
Finally, if the marker <!--B--> is present in test, dump the output binary file produced by the test, e.g. t1234.obj, t1234.exe etc., and compare with the expected dump.

Executable test manager

File testman.exe is 32bit console application for MS Windows. It is not shipped in EuroAssembler distribution, so you will have to compile it first from its source. Change to subdirectory prowin32 and perform the command euroasm testman.htm This will create an executable manager ../eatests/testman.exe.
In order to test EuroAssembler functions with this executable test manager, change to the subdirectory eatests and launch testman.exe with the name(s) of desired tests. File extension .htm as well as the leading letter t may be omitted from the test name, for instance testman.exe t1234.htm, t1235, 1236 Wildcard characters ? and * will be resolved, for instance testman * will perform all tests from the eatests folder.

Script test manager

This method requires to have PHP and webserver installed on your developement localhost computer. PHP test manager manager.php can be launched from the button [Manage] when the test is viewed in browser.
Although it is slower than executable testman.exe, this is the recomended and most comfortable method, because it allows to run, create, validate the results and edit the test directly from intranet browser.

Typical command for launching the test assembly looks like ..\easource\euroasm.exe tNNNN.htm, TIMESTAMP=0, NOWARN=0010..0170,NOWARN=0980,NOWARN=1160 Notice that the checked version of euroasm.exe is from easource directory rather then from system %PATH% — subject of testing is the just updated | rebuilt version of EuroAssembler rather then the stable "factory" release downloaded from EuroAssembler web.
Parameter TIMESTAMP=0 provides forged system time 1.1.1970 0:0:0, because some output file formats incorporate the system time into the object file. Thanks to this fixed faked time is the object file always the same.
Parameters NOWARN= will suppress informative messages such as I0020 Current directory is "!1$". or I0980 Peak memory allocation !1D KB. !2D statements assembled in !3D s. which depend on current install directory and computer performance, and could trigger false differences. This is one of the rare cases when EUROASM parameters need to be specified on command line instead of euroasm.ini configuration file or in the source file.

Tests expect that the configuration provided by global and local euroasm.ini corresponds to factory defaults. That is why both executable test manager and script test manager erase the configuration files easource/euroasm.ini and eatests/euroasm.ini.

↑ The complete list of EuroAssembler tests

↑ Blocks

↑ Strings

↑ Numbers

↑ Symbols

↑ Symbol attributes

↑ Literal symbols

↑ Pseudoinstructions

↑ Addressing modes

↑ Machine instructions

↑ OutputFile

↑ Macros

↑ Variables

↑ Realmode segmentation

↑ Linking

↑ Linker combinations

All tests of linker combinations (t8000 .. t9999) define three procedures for testing the linker:
Write.platform,
Beep.platform,
Exit.platform,
where .platform is .B16, .D16, .L32, .L64, .W32, .W64.

Those tests, which create executable formats, may be run in their operating system (or emulator) and they will
1) write a message identifying the test,
2) write a string "Beeping..."
3) produce a beep sound,
4) write a string "End"
5) terminate with errorlevel=0.

Procedure Beep.platform intentionally defines literal string "Beeping..." in the segment [.rodata], procedure Exit.platform dynamically defines the string "End" in the segment [.bss], thus all types of segments are occupied.