izaya/collapseos
1
0
Fork 0
mirror of https://github.com/hsoft/collapseos.git synced 2024-11-09 08:08:06 +11:00
Code Issues Releases Wiki Activity
289037a3dd
collapseos/tools/tests/unit/test_lib_parse.asm

86 lines
976 B
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
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11:00
.inc "core.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"
.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
zasm: add support for "$" symbol Allows for the ".fill x-$" pattern.
2019-05-20 23:17:50 +10:00
zasmGetPC:
ret
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
testNum: .db 1
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
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
; success
xor a
halt
testParseHex:
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
ld a, '8'
call parseHex
jp c, fail
cp 8
jp nz, fail
call nexttest
ld a, 'e'
call parseHex
jp c, fail
cp 0xe
jp nz, fail
call nexttest
ld a, 'x'
call parseHex
jp nc, fail
call nexttest
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
ret
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
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
testParseHexadecimal:
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
ld hl, .s99
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 parseHexadecimal
jp nz, fail
ld a, e
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
cp 0x99
jp nz, fail
call nexttest
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
ld hl, .saB
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 parseHexadecimal
jp nz, fail
ld a, e
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
cp 0xab
jp nz, fail
call nexttest
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
; The string "Foo" will not cause a failure. We will parse up to "o"
; and then stop.
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
ld hl, .sFoo
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 parseHexadecimal
jp nz, fail
ld a, e
cp 0xf
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 nexttest
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
ret
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
.sFoo: .db "Foo", 0
.saB: .db "aB", 0
.s99: .db "99", 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
nexttest:
ld a, (testNum)
inc a
ld (testNum), a
ret
fail:
ld a, (testNum)
halt
Add tests for parseArgs
2019-11-09 02:18:54 +11:00
; used as RAM
sandbox:
Reference in New Issue Copy Permalink