Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5940

Review kogito-codegen-integration-tests module

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • False

      Review/migrate/remove kogito-codegen-integration-tests module: this module contains sort of integration tests using codegen and in memory compilation in a setup that is not reproducing any real world scenario. In particular it triggers the codepath of Kogito running outside Quarkus/Springboot like a plain Java application without dependency injection (context().hasDI() = false). This use case exists only in this module and it can only execute a very limited set of actions (mainly standalone resources without events/persistences or any other "integration"). There are many different alternatives to consider:

      • Migrate all of them to proper integration tests
      • Move each test in the specific engine (i.e. move process tests to something similar to this existing suite)
      • Wait KOGITO-4593 to be done and use this approach/API to migrate all tests

      My suggestion is to wait KOGITO-4593 because most probably it will help to review this other module

              Unassigned Unassigned
              dzonca@redhat.com Daniele Zonca
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: