Skip to content

Testing! #11

@dkfellows

Description

@dkfellows

You have no tests. How can you know whether your code works right without testing it? (There are a few cases where it's possible, but your code is definitely not in one of them.)

Now, manually testing everything admittedly gets really boring, especially when you can test many things automatically once you set them up. (Since you're already using CMake, adding in CTest is pretty simple.)

The advantage with having defined tests set up (that you can run with cmake --test) is that the tests remember things that should work so that you don't have to spend so much effort on checking whether things work yourself. I recommend testing whether the code does what it should when presented with (small pieces of) input data that it should receive, and, for bonus points, that it also does something somewhat sensible when it receives input data that it shouldn't.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions