<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:01:20 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>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CXX-1079] Control integration tests via environment variables</title>
                <link>https://jira.mongodb.org/browse/CXX-1079</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;All integration tests assume a mongod (or mongos) on the default port.  We should add environment variables for greater control:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;MONGOCXX_SKIP_INTEGRATION &#8211;&#160;if set, skip rather than possibly fail integration tests&lt;/li&gt;
	&lt;li&gt;MONGOCXX_TEST_URI &#8211; if set, use instead of the default URI string&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="322640">CXX-1079</key>
            <summary>Control integration tests via environment variables</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="12300">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="david.golden@mongodb.com">David Golden</reporter>
                        <labels>
                            <label>bgtrack</label>
                    </labels>
                <created>Tue, 11 Oct 2016 01:54:47 +0000</created>
                <updated>Mon, 6 Feb 2023 20:04:57 +0000</updated>
                            <resolved>Mon, 6 Feb 2023 20:04:57 +0000</resolved>
                                                                    <component>Testing</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="1486383" author="david.golden" created="Thu, 26 Jan 2017 23:00:31 +0000"  >&lt;p&gt;This may happen anyway as part of our conversion to Evergreen testing multiple server versions with mongo orchestration.&lt;/p&gt;</comment>
                            <comment id="1405062" author="david.golden" created="Tue, 11 Oct 2016 13:23:03 +0000"  >&lt;p&gt;Using CTest or other mechanism to disable integration tests would be fine once we have them split out.&lt;/p&gt;

&lt;p&gt;The advantage I&apos;ve found using an environment variable for the connection URI is that I can set the URI differently in different shells and then run tests against different mongods in each shell without having to reconfigure anything.  It&apos;s fine to default to localhost:27017, but superseding it with an environment variable gives a lot of development flexibility.&lt;/p&gt;</comment>
                            <comment id="1405022" author="acm" created="Tue, 11 Oct 2016 12:41:33 +0000"  >&lt;p&gt;Maybe we should make more use of &lt;a href=&quot;https://cmake.org/Wiki/CMake/Testing_With_CTest?&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://cmake.org/Wiki/CMake/Testing_With_CTest?&lt;/a&gt; Or does catch offer some more customizations that we have not explored? I&apos;m generally not in favor of environment variables to control testing. Something declarative, file based, or command line argument driven is better. Otherwise, the same command executed in different contexts yields different results. That can quite puzzling, if you forget that you set one of these in your environment.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CXX-1023</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr6mnz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>