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

Break Kogito Apps Integration and Unit tests in separate profiles and run unit tests in parallel

    XMLWordPrintable

Details

    • Task
    • Resolution: Won't Do
    • Major
    • None
    • 1.4.0.Final
    • Core Engine
    • None

    Description

      Following up KOGITO-4839 plan, this JIRA is for a POC/Proposal for creating a separate profile to run Integration Tests in kogito-runtimes modules. There are dedicated modules to run such tests and also tests with integrationtests namespaces or IT suffix. Those should run separately since they take more time and require infra (such as Docker).

      Another thing to consider is parallelizing the remaining unit tests, at least at the class level.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. KOGITO-4933 Separate unit tests and integration tests for Kogito Apps PR checks

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          clones

          Task - Represents a small unit of work that is not end-user facing. KOGITO-4889 Proposal to break Kogito Runtimes Integration and Unit tests in separate profiles and run unit tests in parallel

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. KOGITO-4931 Break Kogito Examples Integration and Unit tests in separate profiles and run unit tests in parallel

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-zanini Ricardo Zanini Fernandes
              tradisso@redhat.com Tristan Radisson
              Tristan Radisson Tristan Radisson
              Tristan Radisson Tristan Radisson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: