re-test

Step 5

change kick-off message to “vsh”

change input to “arg” and wire through to 1t2

delete literalvsh component

update diagram

make dev

replace arg with input from port

re-test

Step 4

change kick-off message to “go”

add literalvsh

add literalgrep

output “literal”

input “go”

output “literal”

update user.odin

only one input “go”

input “go”

add literalvsh -> “vsh”

add literalgrep -> “grep ”

update diagram

str

create literal strings using Components

2

output should be “grep vsh”

1

make dev

Step 3

one output

run test

two inputs

add stringconcat Leaf

should see same correct order on output

delete one ?

output 2 -> “vsh”

modify user.odin

add stringconcat component

output 1 -> “grep ”

update diagram

see outputs on Terminal

change order of inputs

test stringconcat

re-run test

?

1t2

make dev

more testing

Step 2

false

? 2 output

? 1 output

run test

inject messages

leaf parts

1t2

logging

input2

input1

update user.odin

very low level, like “systems code” - users should not have to see this level of detail, only implementors should know about this

create diagram

? Component

Observe outputs

Inject inputs

incremental testing in small steps

inspired by a test case on another repo branch

demonstrates very basic usage of drawware & 0D

Bench test 1t2 Component

Step 1

simplistic