<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:02:02 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[INFRAUTILS-12] New integration test utilities</title>
                <link>https://jira.opendaylight.org/browse/INFRAUTILS-12</link>
                <project id="10129" key="INFRAUTILS">infrautils</project>
                    <description>&lt;p&gt;As-is currently, it takes too much copy/paste-ing, of both POM XML as well as Java code, to correctly create Pax Exam Integration Tests which in Karaf in ODL.&lt;/p&gt;

&lt;p&gt;Caveat emptor: ITs should &lt;b&gt;ONLY&lt;/b&gt; be written if what you need test coverage for cannot be done with a &quot;Component Test&quot;, see &lt;a href=&quot;https://wiki-archive.opendaylight.org/view/BestPractices/Component_Tests&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki-archive.opendaylight.org/view/BestPractices/Component_Tests&lt;/a&gt;; but sometimes they are useful...&lt;/p&gt;

&lt;p&gt;The org.opendaylight.controller.config.it.base.AbstractConfigTestBase is a previous attempt at something similar (and there may be others that I&apos;m not aware of?), but it has limitations (incl. its use of CSS, and only 1 feature; also no base POM), so I&apos;ll propose a new one in infrautils.&lt;/p&gt;

&lt;p&gt;It will attempt to enforce a much cleaner classpath than most of our current ITs have; it&apos;s just wrong to have an entire Karaf and the features themselves on the test&apos;s CP; all that is loaded dynamically, that&apos;s the whole point of Pax Exam; only the IT itself, a small API surface of what you want to test, but not impls, and some Pax utils should be on the CP...&lt;/p&gt;

&lt;p&gt;If I can, I may even make the new one able to automatically support running the same IT under both Karaf 3 as well as Karaf 4, that would be cool.&lt;/p&gt;

&lt;p&gt;It may have other built-in goodies in the future; e.g. something to deal with PITA of referencing utility classes from tests, such as something like say the infrautils LogRule or Google Truth, etc.  (Due to the Pax Exam classloading, that&apos;s a real PITA.)&lt;/p&gt;

&lt;p&gt;I&apos;m also missing a utility to be able to easily test Karaf CLI commands; I&apos;ll probably eventually add that as part of this as well.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="19501">INFRAUTILS-12</key>
            <summary>New integration test utilities</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="vorburger">Michael Vorburger</reporter>
                        <labels>
                    </labels>
                <created>Mon, 15 May 2017 09:03:35 +0000</created>
                <updated>Tue, 5 Oct 2021 23:12:34 +0000</updated>
                            <resolved>Tue, 5 Oct 2021 23:12:34 +0000</resolved>
                                    <version>Nitrogen</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="35407" author="vorburger" created="Mon, 15 May 2017 09:06:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/56898/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/56898/&lt;/a&gt; has first iteration (more later)&lt;/p&gt;</comment>
                            <comment id="69705" author="rovarga" created="Tue, 5 Oct 2021 23:12:34 +0000"  >&lt;p&gt;I do not believe we should be going the Guice route this way. We have &lt;a href=&quot;https://jira.opendaylight.org/browse/ODLPARENT-262&quot; title=&quot;SingleFeatureTest needs to be safe to execute in parallel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;ODLPARENT-262&quot;&gt;ODLPARENT-262&lt;/a&gt;, which should allow us to easily package up a feature.xml and test that. A test can be written as a normal OSGi DS application and launched either in a dynamic or static container.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="34485">ODLPARENT-262</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8438</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=8438]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10312"><![CDATA[High]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01mi7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>