public static void deleteResultFilesOnStartup() {
		deleteResultFilesOnStartup = true;
	}
<code>ProcessorEmulatorTestAdapter</code> provides an abstract JUnit test implementation
for processor-specific test cases.  All test cases which extend this class must have a
class name which ends with 'EmulatorTest' and starts with the processor designator which
will be used to identify associated test binaries within either the processor module's
data/pcodetests/ directory or the Ghidra/Test/TestResources/data/pcodetests/ directory generally 
contained within the binary repository (e.g., ghidra.bin).
<p>
Within the pcodetests directory all files and folders which start with the prefix
{@literal <processor-designator>_pcodetest*} will be processed.  All files contained within a matching
subdirectory will be treated as related binaries and imported.  Any *.gzf file will be
imported but assumed to be pre-analyzed.  Binary files to be imported and analyzed must
utilize the *.out file extension.
<p>
JUnit X86EmulatorTest could utilize the following binary file naming strategy:
<pre>
pcodetests/X86_PCodeTests
- binary1.o
- binary2.o
- binary3.gzf
pcodetests/X86_PCodeTests/data (could be used for any associated files not to be imported)
- binary3.o
- binary3.d

or, a single binary file could suffice:
- pcodetests/X86_PCodeTest.out
</pre>

Any *.out binary found will be imported and analyzed.  The resulting program will
be stored as a gzf in the test-output cache directory.  These cached files will be used
instead of a test resource binary if that binary's md5 checksum has not changed since its cached
gzf was created.  This use of cache files will allow the tests to run quickly on subsequent
executions.  If re-analysis is required, the cache will need to be cleared manually.

NOTES:
1. Dummy Test Methods must be added for all known test groups.  See bottom of this file.  This
   all allows for the single test trace mode execution to work within Eclipse.
2. Trace logging disabled by default when all test groups are run (see buildEmulatorTestSuite method).
   Specific traceLevel and traceLog file controlled via environment properties
   EmuTestTraceLevel and EmuTestTraceFile.
3. The TestInfo structure must be properly maintained within the datatype archive EmuTesting.gdt
   and field naming consistent with use in PCodeTestControlBlock.java
4. The {@link #initializeState(EmulatorTestRunner, Program)} may be overriden to initialize the
   register values if needed.  This should be based upon symbols or other program information
   if possible since hardcoded constants may not track future builds of a test binaries.  
   An attempt is made to initialize the stack pointer automatically based upon well known
   stack initialization symbols.
Ghidra/Features/Base/src/main/java/ghidra/test/processors/support/ProcessorEmulatorTestAdapter.java