npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

zat

v0.1.10

Published

Z80 Automated Testing =====================

Downloads

21

Readme

Z80 Automated Testing

This is the beginnings of a project to enable Test Driven Development for Z80 programmes.

WARNING: This is a work in progress, and the API is likely to change.

The idea is that you can do something like this:

it('should work', function() {
    zat.compile(`
    start:
        ld a,0
        halt
        org 20
    newstart:
        ld a,$12
        nop
        nop
    breakhere:
        ld a,$ff
        halt
    `)
    zat.setBreakpoint('breakhere');
    zat.run('newstart');
    expect(zat.z80.a).toBe(0x12);
});

This compiles a block of Z80 code, and then runs it up to the breakpoint, and then checks that a register is correct. I'm using it in Jasmine; I imagine it would also work just fine in Mocha.

You can also load data directly into memory:

zat.load([0x3e, 0x12, 0xd3, 0x56, 0x76], 0x100);

And you can compile an external file:

zat.compileFile('spec/test.z80');

You can write functions to handle memory and io reads and writes.

beforeEach(function() {
    zat = new Zat();
    zat.onMemRead = (addr) => {
        console.log(`read ${addr.toString(16)}`);
        return undefined;
    }
    zat.onIoWrite = (port, value) => {
        console.log(`OUT ${port.toString(16)}, ${value.toString(16)}`);
    }
    zat.onIoRead = (port) => {
        console.log(`IN ${port.toString(16)}`);
        return 0x00;
    }
});

I am working on improving this part of the system so that you can read back the io activity automatically after running a test. You can use an IoSpy to respond to IN instructions:

it('should read a character', function() {
    zat.compileFile('spec/test.z80');

    let ioSpy = new IoSpy().returnValues([[9, 0xff], [9, 0xff], [9, 0xff], [9, 0], [8, 65]]);
    zat.onIoRead = ioSpy.readSpy();
    zat.z80.sp = 0xFF00;
    zat.call('read_char');
    expect(zat.z80.a).toEqual(65);
    expect(ioSpy).toBeComplete();
});

I'm using ASM80 (https://github.com/maly/asm80-node) to compile the code, and a modified version of Z80.js (https://github.com/DrGoldfire/Z80.js) to run the code.

This is licensed under the MIT licence.

Use

To use this in a project, you need to install these npm packages as dev-dependencies:

  • zat
  • typescript
  • jasmine
  • jasmine-ts
  • @types/jasmine

Example:

mkdir my-project
cd my-project
npm init
npm i -D zat typescript jasmine jasmine-ts @types/jasmine
./node_modules/.bin/jasmine init

Then add this into your package.json:

"scripts": {
    "test": "jasmine-ts 'spec/**/*.spec.ts'"
}

Now you can create a test spec in the spec directory. Something like this:

import { Zat, IoSpy, StepMock, customMatchers, stringToBytes, hex16, Compiler, CompiledProg, Z80 } from 'zat';

describe('things', function() {
    let zat: Zat;
    let prog: CompiledProg;

    beforeEach(function() {
        jasmine.addMatchers(customMatchers as any);

        zat = new Zat();
    });

    it('should do something', function() {
        zat.compileFile('test.z80');
        zat.run(0);
        expect(zat.z80.a).toBe(5);
    })
});