Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-1014

Packaging Processor phase is skipped when the deployment is not testable

    XMLWordPrintable

Details

    Description

      Documentation of Deployment.testable() says: "Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.". However when it's set to false it also disables all application archive processors (see code), so Jacoco instrumentation is not processed.

      I think this behaviour should be at least well documented, but it would be better to rename testable() or change behaviour of deployment generator.

      Attachments

        Issue Links

          duplicates

          Feature Request - Feature requests from customers and/or users ARQ-560 Support for collection of code coverage data of locally executed tests against remote deployments

          • 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
          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ARQ-918 Pick a better name for testable attribute on @Deployment annotation

          • 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.
          • Pull Request Sent
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ARQ-1018 Remote extensions are not loaded when the deployment method is inside the test class annotated by @RunAsClient annotation

          • 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

              Unassigned Unassigned
              jpapouse Jan Papousek (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: