Skip to content

Revive some unit testing framework #568

Open

Description

@oocube

Allow Oolite to be automatically tested on every build. This allows to start modifying the code and ensure it does not break.

Activity

  1. mcarans commented on Apr 7, 2026

    @mcarans
    Contributor

    See #591

  2. oocube commented on Apr 7, 2026

    @oocube
    ContributorAuthor

    #591 is a nice gadget going into the right direction of automated tests, although some purists might call this a system integration test.

    What unit testing frameworks can we actually use for Oolite? Does it have to be some Objective C unit test, or can we run C/C++ unit tests as well? Or do we need both?

  3. oocube commented on Jun 4, 2026

    @oocube
    ContributorAuthor

    As #591 is merged meanwhile, could we extend the concept towards system integration testing?

    I like the idea we can invoke Oolite such that it gets controlled via a script file. The commands should allow to use all the Oolite's javascript internals plus load/save specific savegames. And it should be possible to check specific game conditions and communicate the result back to the outside world as check successful/failed/unexpected result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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