Groups | Search | Server Info | Login | Register


Groups > comp.emulators.apple2 > #2250

Re: Clues tracking down an emulator bug (San inc crack of Airheart)

Newsgroups comp.emulators.apple2
Date 2017-02-21 10:00 -0800
References (1 earlier) <e029d0bd-4cd3-4104-ba2a-3b46659e0390@googlegroups.com> <bc36ba00-c65f-46ce-b961-e5fb8c8b04cd@googlegroups.com> <73b17e3e-c1cc-4512-9885-b8c5cef9fc62@googlegroups.com> <907fb263-d80c-4483-80cc-2b59cec96a05@googlegroups.com> <3f769e02-cb4e-41c6-a8d3-0a484e3d6f1f@googlegroups.com>
Message-ID <be1c40e1-01fb-43dd-a7db-b7a3def2c83d@googlegroups.com> (permalink)
Subject Re: Clues tracking down an emulator bug (San inc crack of Airheart)
From BLuRry <brendan.robert@gmail.com>

Show all headers | View raw


On Tuesday, February 21, 2017 at 10:11:51 AM UTC-6, Zellyn wrote:
> On Tuesday, February 21, 2017 at 10:56:07 AM UTC-5, Michael AppleWin Debugger Dev wrote:
> > i.e. We can add this to AppleWin as a test case to detect when/if the disk cycle timing emulation is fixed.
> 
> FYI, I'm working on a generic IIe emulator test suite. I already have the high-ram langcard-like functionality tests done (no emulators I've tested so far pass perfectly, although I'm MacOS so haven't tried AppleWin), aux-ram banking tests, softswitch-reading tests, and Cxxx-ROM banking tests. I've started in on graphics tests.
> 
> I don't yet have any disk tests -- in fact it's sort of an explicit non-goal at the moment -- but I could see adding them in the future (or accepting pull requests!). So if you can distill the problem down to a succinct description that I can implement as a read-and-then-write test, it might be a good thing to add in the future.
> 
> Later,
> 
> Zellyn

I added JUnit stubs in Jace for this kind of thing.  Curious to see what you've  come up with.  You can write unit tests in Jace which have actual assembler in them and it will use ACME to build the code and then run it.  On the java side after plugging the code into memory it will run for the specified number of machine cycles and then assert if the result is correct.

For example:
    @Test
    public void testAdditionNonDecimalWithCarry() {
        cpu.A = 0;
        cpu.D = false;
        cpu.C = 1;
        assemble(" adc #1");
        assertEquals("0+1 (c=1) = 2", 2, cpu.A);
        assertFalse("Result is not zero", cpu.Z);
    }

-B

Back to comp.emulators.apple2 | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-19 14:51 -0800
  Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-19 17:15 -0800
    Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-19 21:16 -0800
      Re: Clues tracking down an emulator bug (San inc crack of Airheart) Peter Ferrie <peter.ferrie@gmail.com> - 2017-02-20 10:19 -0800
        Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-20 13:59 -0800
          Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-20 14:42 -0800
        Re: Clues tracking down an emulator bug (San inc crack of Airheart) Michael AppleWin Debugger Dev <michael.pohoreski@gmail.com> - 2017-02-21 07:56 -0800
          Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-21 08:11 -0800
            Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-21 10:00 -0800
              Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-21 10:10 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) sicklittlemonkey <nick.westgate@gmail.com> - 2017-02-21 19:11 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) gids.rs@sasktel.net - 2017-02-22 09:28 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-22 09:33 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) sicklittlemonkey <nick.westgate@gmail.com> - 2017-02-23 01:46 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-23 06:19 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) gids.rs@sasktel.net - 2017-02-23 08:44 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Michael AppleWin Debugger Dev <michael.pohoreski@gmail.com> - 2017-02-23 21:03 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Steve Nickolas <usotsuki@buric.co> - 2017-02-24 07:14 -0500
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-24 06:07 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) John Brooks <jbrooks@blueshiftinc.com> - 2017-02-24 07:56 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-24 09:55 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-24 12:45 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) gids.rs@sasktel.net - 2017-02-24 14:56 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-24 18:37 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Richard Thiebaud <thiebauddick2@aol.com> - 2017-02-24 22:01 -0500
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-24 21:09 -0800
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Richard Thiebaud <thiebauddick2@aol.com> - 2017-02-25 19:42 -0500
                Re: Clues tracking down an emulator bug (San inc crack of Airheart) Richard Thiebaud <thiebauddick2@aol.com> - 2017-02-25 19:48 -0500
          Re: Clues tracking down an emulator bug (San inc crack of Airheart) Peter Ferrie <peter.ferrie@gmail.com> - 2017-02-21 08:24 -0800
          Re: Clues tracking down an emulator bug (San inc crack of Airheart) John Brooks <jbrooks@blueshiftinc.com> - 2017-02-23 18:29 -0800
        Re: Clues tracking down an emulator bug (San inc crack of Airheart) Peter Ferrie <peter.ferrie@gmail.com> - 2017-02-21 22:57 -0800

csiph-web