izaya/collapseos
1
0
Fork 0
mirror of https://github.com/hsoft/collapseos.git synced 2024-11-01 19:30:55 +11:00
Code Issues Releases Wiki Activity
08328b86a9
collapseos/tests/unit/test_lib_parse.asm

196 lines
2.3 KiB
NASM
Raw Normal View History

Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
jp test
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.inc "ascii.h"
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11:00
.inc "core.asm"
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.equ STDIO_RAMSTART RAMSTART
.inc "stdio.asm"
.inc "common.asm"
.inc "lib/ari.asm"
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-16 07:37:49 +11:00
.inc "lib/util.asm"
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.inc "lib/fmt.asm"
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-16 07:37:49 +11:00
.inc "lib/parse.asm"
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
test:
lib/args: remove
2019-12-30 13:05:09 +11:00
ld sp, 0xffff
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
call testParseHex
lib/parse: remove parseHexPair Also, make parseHexadecimal "tail" (HL). Soon, all routines in lib/parse will do that, making the life of lib/expr easier.
2019-12-30 13:39:51 +11:00
call testParseHexadecimal
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
call testParseDecimal
call testParseLiteral
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
; success
xor a
halt
testParseHex:
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
ld hl, .allGood
ld ix, .testGood
call testList
ld hl, .allBad
ld ix, .testBad
jp testList
.testGood:
ld a, (hl)
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
call parseHex
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
call assertNC
inc hl
ld b, (hl)
jp assertEQB
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.testBad:
ld a, (hl)
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
call parseHex
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
jp assertC
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.g1:
.db '8', 8
.g2:
.db 'e', 0xe
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.allGood:
.dw .g1, .g2, 0
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
.b1:
.db 'x'
.allBad:
.dw .b1, 0
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
Consolidate tests Also, removed leftover in runbin.c (what did it do there??) that could result in tests falsely passing.
2019-12-31 12:08:08 +11:00
testParseHexadecimal:
ld hl, .allGood
ld ix, .testGood
jp testList
.testGood:
ld c, (hl)
inc hl
ld b, (hl)
inc hl
call parseHexadecimal
call assertZ
ld l, c
ld h, b
jp assertEQW
.g1:
.dw 0x99
.db "99", 0
.g2:
.dw 0xab
.db "aB", 0
; The string "Foo" will not cause a failure. We will parse up to "o" and then
; stop.
.g3:
.dw 0xf
.db "Foo", 0
.allGood:
.dw .g1, .g2, .g3, 0
testParseDecimal:
ld hl, .allGood
ld ix, .testGood
call testList
ld hl, .allBad
ld ix, .testBad
jp testList
.testGood:
ld c, (hl)
inc hl
ld b, (hl)
inc hl
call parseDecimalC
call assertZ
ld l, c
ld h, b
jp assertEQW
.testBad:
call parseDecimalC
jp assertNZ
.g1:
.dw 99
.db "99", 0
.g2:
.dw 65535
.db "65535", 0
; Space is also accepted as a number "ender"
.g3:
.dw 42
.db "42 x", 0
; Tab too
.g4:
.dw 42
.db "42", 0x09, 'x', 0
; A simple "0" works too!
.g5:
.dw 0
.db '0', 0
.allGood:
.dw .g1, .g2, .g3, .g4, .g5, 0
; null string is invalid
.b1:
.db 0
; too big, 5 chars
.b2:
.db "65536", 0
.b3:
.db "99999", 0
.b4:
; too big, 6 chars with rightmost chars being within bound
.db "111111", 0
.allBad:
.dw .b1, .b2, .b3, .b4, 0
testParseLiteral:
ld hl, .allGood
ld ix, .testGood
call testList
ld hl, .allBad
ld ix, .testBad
jp testList
.testGood:
ld c, (hl)
inc hl
ld b, (hl)
inc hl
call parseLiteral
call assertZ
ld l, c
ld h, b
jp assertEQW
.testBad:
call parseLiteral
jp assertNZ
.g1:
.dw 99
.db "99", 0
.g2:
.dw 0x100
.db "0x100", 0
.g3:
.dw 0b0101
.db "0b0101", 0
.g4:
.dw 0b01010101
.db "0b01010101", 0
.allGood:
.dw .g1, .g2, .g3, .g4, 0
.b1:
.db "Foo", 0
.allBad:
.dw .b1, 0
RAMSTART:
Reference in New Issue Copy Permalink