6502/erc-c
1
0
Fork 0
mirror of https://github.com/pevans/erc-c.git synced 2024-12-22 14:30:45 +00:00
Code Issues Projects Releases Wiki Activity
7da3c2ec20
erc-c/tests/mos6502.addr.c

160 lines
4.2 KiB
C
Raw Normal View History

Adding all of the instruction files
2017-12-02 19:05:53 +00:00
#include <criterion/criterion.h>
#include "mos6502.h"
#include "mos6502.enums.h"
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
#include "mos6502.tests.h"
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
TestSuite(mos6502_addr, .init = setup, .fini = teardown);
Test(mos6502_addr, addr_mode)
Add functions for instructions, cycles, and address modes. This also adds a new table for cycles, and adds unit test functions for the work as well.
2017-12-05 05:30:18 +00:00
{
cr_assert_eq(mos6502_addr_mode(0xEA), IMP);
cr_assert_eq(mos6502_addr_mode(0xD6), ZPX);
cr_assert_eq(mos6502_addr_mode(0xF0), REL);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, get_address_resolver)
{
Change address resolver test to use new approach
2017-12-06 02:15:22 +00:00
cr_assert_eq(mos6502_get_address_resolver(0x0A), mos6502_resolve_acc);
cr_assert_eq(mos6502_get_address_resolver(0x20), mos6502_resolve_abs);
cr_assert_eq(mos6502_get_address_resolver(0xBC), mos6502_resolve_abx);
cr_assert_eq(mos6502_get_address_resolver(0x19), mos6502_resolve_aby);
cr_assert_eq(mos6502_get_address_resolver(0xA0), mos6502_resolve_imm);
cr_assert_eq(mos6502_get_address_resolver(0x6C), mos6502_resolve_ind);
cr_assert_eq(mos6502_get_address_resolver(0x01), mos6502_resolve_idx);
cr_assert_eq(mos6502_get_address_resolver(0x11), mos6502_resolve_idy);
cr_assert_eq(mos6502_get_address_resolver(0x10), mos6502_resolve_rel);
cr_assert_eq(mos6502_get_address_resolver(0x05), mos6502_resolve_zpg);
cr_assert_eq(mos6502_get_address_resolver(0x15), mos6502_resolve_zpx);
cr_assert_eq(mos6502_get_address_resolver(0x96), mos6502_resolve_zpy);
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_acc)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
cpu->A = 123;
cr_assert_eq(mos6502_resolve_acc(cpu), 123);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_abs)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x1234, 111);
SET_PC_BYTE(cpu, 0, 0x12);
SET_PC_BYTE(cpu, 1, 0x34);
cr_assert_eq(mos6502_resolve_abs(cpu), 111);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_abx_carry0)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x1234, 111);
SET_PC_BYTE(cpu, 0, 0x12);
SET_PC_BYTE(cpu, 1, 0x30);
cpu->X = 4;
cr_assert_eq(mos6502_resolve_abx(cpu), 111);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_abx_carry1)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x1234, 111);
SET_PC_BYTE(cpu, 0, 0x12);
SET_PC_BYTE(cpu, 1, 0x30);
cpu->X = 3;
cpu->P = cpu->P | CARRY;
cr_assert_eq(mos6502_resolve_abx(cpu), 111);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_aby_carry0)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x1234, 111);
SET_PC_BYTE(cpu, 0, 0x12);
SET_PC_BYTE(cpu, 1, 0x30);
cpu->Y = 4;
cr_assert_eq(mos6502_resolve_aby(cpu), 111);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_aby_carry1)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x1234, 111);
SET_PC_BYTE(cpu, 0, 0x12);
SET_PC_BYTE(cpu, 1, 0x30);
cpu->Y = 3;
cpu->P = cpu->P | CARRY;
cr_assert_eq(mos6502_resolve_aby(cpu), 111);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_imm)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
SET_PC_BYTE(cpu, 0, 0x12);
cr_assert_eq(mos6502_resolve_imm(cpu), 0x12);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_idx)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x17, 0x23);
vm_segment_set(cpu->memory, 0x23, 123);
SET_PC_BYTE(cpu, 0, 0x12);
cpu->X = 5;
cr_assert_eq(mos6502_resolve_idx(cpu), 123);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_idy)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x12, 0x23);
vm_segment_set(cpu->memory, 0x28, 123);
SET_PC_BYTE(cpu, 0, 0x12);
cpu->Y = 5;
cr_assert_eq(mos6502_resolve_idy(cpu), 123);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_ind)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x1234, 0x23);
vm_segment_set(cpu->memory, 0x1235, 0x45);
vm_segment_set(cpu->memory, 0x2345, 123);
SET_PC_BYTE(cpu, 0, 0x12);
SET_PC_BYTE(cpu, 1, 0x34);
cr_assert_eq(mos6502_resolve_ind(cpu), 123);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_rel_positive)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
cpu->PC = 123;
SET_PC_BYTE(cpu, 0, 88);
cr_assert_eq(mos6502_resolve_rel(cpu), 0);
cr_assert_eq(cpu->last_addr, 211);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_rel_negative)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
cpu->PC = 123;
SET_PC_BYTE(cpu, 0, 216);
cr_assert_eq(mos6502_resolve_rel(cpu), 0);
cr_assert_eq(cpu->last_addr, 34);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_zpg)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x0034, 222);
SET_PC_BYTE(cpu, 0, 0x34);
cr_assert_eq(mos6502_resolve_zpg(cpu), 222);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_zpx)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x0034, 222);
SET_PC_BYTE(cpu, 0, 0x30);
cpu->X = 4;
cr_assert_eq(mos6502_resolve_zpx(cpu), 222);
}
Vastly simplify unit tests for mos6502 Criterion's init and fini config options allow us to register setup and teardown functions. We now use this to register the common cpu variable for the mos6502 tests, albeit through the use of a global variable. Doing so necessitated that each of the different test files have their own suites, due to some implementation details in Criterion, but this is No Big Deal.
2017-12-06 21:57:15 +00:00
Test(mos6502_addr, addr_mode_zpy)
{
Adding all of the instruction files
2017-12-02 19:05:53 +00:00
vm_segment_set(cpu->memory, 0x0034, 222);
SET_PC_BYTE(cpu, 0, 0x2F);
cpu->Y = 5;
cr_assert_eq(mos6502_resolve_zpy(cpu), 222);
}
Reference in New Issue Copy Permalink