Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-576

Testsuite tasks (tracking)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • Test Suite
    • None

    Description

      Post-7.1.1 jiras: AS7-4067

      Arquillian tasks affecting the testsuite: https://docspace.corp.redhat.com/docs/DOC-71831

      Maven wishes for summer:

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users AS7-4179 Ability to easily change AS7 log levels when running the tests

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

          Feature Request - Feature requests from customers and/or users AS7-4140 Change distribution of -Dmcast through testsuite

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. AS7-3786 Some non-Arquillian TestCases are run against hard-coded 127.0.0.1

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. AS7-2847 TS: Clustering tests cannot be run for single test with -Dtest=X

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

          Bug - A problem that impairs or prevents the functions of the product. AS7-2909 AS7 testsuite - maven.test.failure.ignore vs. surefire.test.failure.ignore

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

          Task - Represents a small unit of work that is not end-user facing. WFLY-418 TS: Move resources to source packages.

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Quality Risk - A potential bug. AS7-3696 TS: Replace hardcoded URLs and IP adresses with @ArquillianResource-s. [TRACKING]

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Tracker - Issue tracking a bug fix or improvement in another component AS7-4080 @Ignored tests (tracking)

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

          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) AS7-3987 Replace jboss.dist with jboss.home for testsuite and other usage

          • 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

          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) WFLY-228 TS: Migrate from Surefire to Failsafe maven plugin.

          • 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

          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) WFLY-1057 TS: "Big app" using many features, to serve for :restart test

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users AS7-2203 Add Arquillian Container support for AS 7 domain controller

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

          Feature Request - Feature requests from customers and/or users AS7-3727 Arq: Make mgmt address and port available in the @Deployment method.

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

          Feature Request - Feature requests from customers and/or users AS7-2616 Allow AS7 Arquillian container to pass credentials/securely authenticate

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users ARQ-645 @ArquillianResource @OperatesOnDeployment("foo") URL; for multiple containers

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-1182 @RestoreASConfigAfterTest to make a snapshot before test and reload it after.

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-1198 Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run.

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-277 TS: Integrate JUnitDiff

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Feature Request - Feature requests from customers and/or users ARQ-647 Implement a convenient way to pass system properties to managed container's JVM.

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Feature Request - Feature requests from customers and/or users ARQ-648 Implement @ArquillianResource Map<URL> for multi-container configuration.

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Feature Request - Feature requests from customers and/or users ARQ-689 Implement @BeforeDeploy (possibly as an extension)

          • 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

          Feature Request - Feature requests from customers and/or users ARQ-690 Verify ability to run under a security manager (evt. create a policy file)

          • 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

          Feature Request - Feature requests from customers and/or users ARQ-710 Separated per-test and per-container log files.

          • 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

          Feature Request - Feature requests from customers and/or users ARQ-746 Run tests on different containers, stopping and starting them between tests (with automatic grouping).

          • 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

          Bug - A problem that impairs or prevents the functions of the product. AS7-4070 CLONE - Arquillian should wait until a port is free after AS JVM process ends to prevent "port in use".

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

          Bug - A problem that impairs or prevents the functions of the product. AS7-3111 @ArquillianResource InitialContext injection does not work in @RunAsClient annotated tests (remote JNDI)

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

          Bug - A problem that impairs or prevents the functions of the product. ARQ-696 Last test's standard output is not saved - probably missing flush() ?

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          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-697 Exception "Could not deploy to container" should report the real exception why the managed server is failing

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          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) AS7-3718 Copy cause exception message to DeploymentException: "Could not deploy to container".

          • 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

          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-742 Print the name of the container in the "Could not deploy to container" exception.

          • 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 related to

          Sub-task - The sub-task of the issue AS7-581 Identify all public APIs

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-698 Intermitent testsuite failures (tracking)

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. AS7-650 Create POM and Assembly for AS7 Public APIs

          • 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.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue WFLY-765 Allow Arquillian tests to monitor server and deployment status explicitly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users ARQ-797 Should support measuring deployment, test, undeployment times separately

          • 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

          Feature Request - Feature requests from customers and/or users ARQ-638 Option to "clean" the container before running tests

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Pull Request Sent

          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-803 Mark the skipped tests somehow in JUnit reports when the container failed to boot.

          • 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
          There are no Sub-Tasks for this issue.

          Activity

            People

              ozizka_jira Ondrej Zizka (Inactive)
              ozizka_jira Ondrej Zizka (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 weeks, 1 day, 7 hours Original Estimate - 4 weeks, 1 day, 7 hours
                  4w 1d 7h
                  Remaining:
                  Time Spent - 1 week, 3 days, 2 hours Remaining Estimate - 2 weeks, 4 days, 5 hours
                  2w 4d 5h
                  Logged:
                  Time Spent - 1 week, 3 days, 2 hours Remaining Estimate - 2 weeks, 4 days, 5 hours
                  1w 3d 2h