@Test
	public void testCLI_1b_mod_noE() throws Exception {
		mangled = "?name0@name1@name2@name3@@$$FSMP$01AEVname4@name5@@PE$AAVname6@5@1P$01AEHH@Z";
		msTruth = "public: static cli::array<unsigned char >^";
		mdTruth =
			"public: static cli::array<unsigned char >^ __clrcall name3::name2::name1::name0(class name5::name4,class name5::name6 ^ __ptr64,class name5::name6 ^ __ptr64,cli::array<unsigned char >^,int,int)";
		demangleAndTest();
	}
This class provides a core set of tests that have been discovered, created, and fuzzed--
 though many have been "genericized" with name components such as name0, name1,...  These
 tests are then run with different test configurations, though maybe not all of the time.
 For instance, only one configuration is currently envisioned for being run during nightly
 or continuous testing.  The other tests are intended to be exercised while the code is
 being modified.
As the developer of this demangler, I wanted to be able to have a demangler that could
 provide demangled interpretations based upon what Microsoft said was truth (which is wrong
 in many cases) and what I interpreted as truth (and it goes beyond this, as we have at
 least 6 different ways at this time for how to run the demangler).  But to use one
 set of tests without duplicating them across each configuration, I provide the test
 configuration, which creates the appropriate demangler (derived from MDMang) and then
 performs the appropriate tests (asserts) for the types of output that each demangler
 provides.
Note: While I believe there are bugs in some of Microsoft's interpretation, I find that
 it is very appropriate to try to model what Microsoft is doing--even trying to get its
 white spaces correct (including dangling white spaces)--as this provides insights into
 the Microsoft model and helps ups to "believe" that we are on the right track; moreover,
 it provides us with the ability to create large sets of data (millions of samples are
 available from Windows 7 and Windows 10 symbols) against which we can run our demangler
 and discover if we are doing better or worse with any given change.  As an example, I
 was able to make a change to this code base and run against the core set of tests below
 and found that I broke no tests, but when I ran against the Windows 10 symbols, I failed
 more than 1300 of these tests when the norm was to fail 73.  Note too, that I immediately
 throw away symbols from these sets that I can immediately say that Microsoft has gotten
 wrong (e.g., has "??" in the demangled string), but this approach gives general direction
 and it often (as in my example case) leads me to grab another symbol or two to put into
 the core set of tests to provide constraints around this living design.
The test configuration class names have the form MDMangFooTestConfiguration.  And the test
 suites for any of these configurations are in class names of the form MDMangFooTest (all
 derived from this class--MDMangBaseTest).  If someone needs to run just a single test
 method in this MDMangBaseTest with a different derived class from within Eclipse, then
 they can do so by making two line changes below in the constructor of this class--effectively
 transforming the class to look like one of its derived classes; at that point the developer
 can right-click on the specific test and run or debug that single test method (of course
 the constructor below should be changed back to its original form).
Note that there is also a test suite for performing nightly and continuous testing that
 makes use of junit Categories to annotate and eliminate currently failing test methods
 below from the test run.  This test suite is named MDMangBaseTestSuite.  Of course, the
 totality of tests can be run as normal by just running all tests in this file, as normal.
 This is the typical mode of testing I use.  But I also make use of the test classes
 derived from this one, including the (currently 2) Microsoft versions as well as the
 MDMangParseInfoTest (or substituting in MDMangParseInfoTestConfiguration in the constructor
 below) in order to get an console output of how the base core test is being parsed.
Ghidra/Features/MicrosoftDmang/src/test/java/mdemangler/MDMangBaseTest.java