Test infrastructure

Jump to bottom

KochynVolodymyr edited this page Nov 28, 2023 · 3 revisions

Tests
GTest	Unittest

Integration tests

Using GTests for TCL interpreter classes.

|

Identify files that can be unit-tested.
How do we bootstrap the GUI ?
- To

| | TCL |

Integration tests

|

Missing test harnesses,
- TCL commands equivalent of GUI user actions.

| | TCL journal logs replay | |

Missing TCL commands for user interactions with each GUI screen.
What we need to capture from GUI interactions?
Every GUI action needs to be piped into journal logs.

| | User interaction testing (without the knowledge of code) | | | | | | |

We can write tcl test just to target a sub-gui,

FOEDAG/projnavigator_main.cpp at main · os-fpga/FOEDAG (github.com)

We can instantiate FOEDAG/newfilemodel.h at main · os-fpga/FOEDAG (github.com) and test createNewFile for e.g.. (Totally different topic of tests: Missing tcl commands to execute)

We can verify if a signal was emitted FOEDAG/new_file_dialog.cpp at main · os-fpga/FOEDAG (github.com)

Notes:

Why this pattern?

C code to TCL code to C code?