Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3950

Improve testing strategy and coverage for Processes

    XMLWordPrintable

Details

    • 2021 Week 43-45 (from Oct 25), 2021 Week 46-48 (from Nov 15), 2021 Week 49-51 (from Dec 6th), 2022 Week 02-04 (from Jan 10), 2022 Week 05-07 (from Jan 31), 2022 Week 08-10 (from Feb 21), 2022 Week 11-13 (from Mar 14), 2022 Week 14-16 (from Apr 4), 2022 Week 17-19 (from Apr 25), 2022 Week 20-22 (from May 16), 2022 Week 23-25 (from Jun 6), 2022 Week 26-28 (from Jun 27), 2022 Week 29-31 (from Jul 18), 2022 Week 32-34 (from Aug 8), 2022 Week 35-37 (from Aug 29), 2022 Week 38-40 (from Sept 19), 2022 Week 41-43 (from Oct 10), 2022 Week 44-46 (from Oct 31), 2022 Week 47-49 (from Nov 21), 2022 Week 50-02 (from Dec 12), 2023 Week 03-05 (from Jan 16), 2023 Week 06-08 (from Feb 6), 2023 Week 09-11 (from Feb 27), 2023 Week 12-14 (from Mar 20), 2023 Week 15-17 (from Apr 10), 2023 Week 18-20 (from May 1), 2023 Week 21-23 (from May 22)

    Description

      Right now we have tests in jbpm module in kogito that tests basically the engine and parser but this not guarantee that this works integrated in kogito, most of the tests were ported from v7 and just adjused with the kogito APIs.

      There are other tests in codegen module that try test the integration of kogito generated code with the engine, this is more reliable but we don't have tests for all features and basically we need to analyse the best way and place to put these kind of tests.

      The goal is to have tests that really guarante the features we already have implemented in kogito for processes are properly tested.

      solution

      1. junit 5 support
      2. plugable system for different runtimes (so far only java, but I think is doable for sb or quarkus)
      3. plugable system for different persistence (so far only file system)

      Attachments

        Issue Links

          clones

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. KOGITO-4593 Improve testing strategy and coverage for Processes

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. KOGITO-5940 Review kogito-codegen-integration-tests module

          • 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.
          • Open

          Activity

            People

              kverlaen@redhat.com Kris Verlaenen
              rhn-support-alazarot Alessandro Lazarotti
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: