Skip to content

Unit tests and integration tests distinction #80

@bva

Description

@bva

With gradle plugin, we have three tasks for tests, one for integration tests (systemtest) and two others for unit testing of perl and java (GWT) code (unittest & test).

Solely purpose of unit tests is to make them run as fast as possible, and independent from working environment (Flow Server & Agent).

For integration testing (which use EF & Agent), we have separate tests, which are based on ntest framework, and which we are actively using in our CI procedures.

I've made modifications to support java-based system tests in or new CI system, but please, note, that system tests is more preferred way for us to do integration testing. So, in future, please, use ntest framework. Ask me, if you have any questions on how to setup CI tests with ntest.

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