Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-11077

Provide tests as reusable components for external testing

    XMLWordPrintable

Details

    Description

      In order to make testing re-usable and to perform same tests on several environment without rebuilding them.

      Suggestion of implementation: Provide feature in component update-site and have an aggregated site for tests, the same way there is one for components (could be a nightly, a snapshot, a release...)

      Attachments

        Issue Links

          is duplicated by

          Sub-task - The sub-task of the issue JBIDE-9869 aggregate test.source features into a single site

          • 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

          Sub-task - The sub-task of the issue JBIDE-11390 publish JBT test plugins to aggregate site so SOA can use them downstream

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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-8838 add source feature to JBT components; generate source plugins w/ Tycho

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

          Feature Request - Feature requests from customers and/or users JBIDE-11284 Rename org.jboss.tools.openshift.test.source.feature to org.jboss.tools.openshift.express.test.source.feature

          • 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

          Activity

            People

              ldimaggi@redhat.com Len DiMaggio
              mistria@redhat.com Mickael Istria
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: