<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:24:46 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>[DRIVERS-2115] CMAP tests are missing coverage for connection establishment failure</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-2115</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;The CMAP spec is a little bit light on tests around the behavior of failed attempts to create a connection. For instance, the &quot;checkOut&quot; pseudocode indicates that a connection should be created if&#160;&lt;tt&gt;totalConnectionCount &amp;lt; maxPoolSize&lt;/tt&gt;, but its easy to miss that a &lt;tt&gt;ConnectionCheckOutFailedEvent&lt;/tt&gt; should be emitted if that connection fails to connect.&#160;&lt;/p&gt;

&lt;p&gt;It seems we could generally improve test coverage around the creation of connections. It might be enough to add a flag to the &lt;tt&gt;checkOut&lt;/tt&gt; test runner operation informing the runner that the operation should fail with a specific error type. If the &lt;tt&gt;checkOut&lt;/tt&gt; fails with &lt;tt&gt;failToCreateConnection&lt;/tt&gt;, then we should expect a&#160;&lt;tt&gt;ConnectionCheckOutFailedEvent&lt;/tt&gt;.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="1106629">DRIVERS-2115</key>
            <summary>CMAP tests are missing coverage for connection establishment failure</summary>
                <type id="14901" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14700&amp;avatarType=issuetype">Spec Change</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="3">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="matt.broadstone@mongodb.com">Matt Broadstone</reporter>
                        <labels>
                    </labels>
                <created>Tue, 21 Jan 2020 14:07:36 +0000</created>
                <updated>Tue, 10 Jan 2023 18:49:59 +0000</updated>
                            <resolved>Tue, 10 Jan 2023 18:49:59 +0000</resolved>
                                                        <component>CMAP</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="3414881" author="divjot.arora" created="Mon, 28 Sep 2020 19:45:55 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=patrick.freed&quot; class=&quot;user-hover&quot; rel=&quot;patrick.freed&quot;&gt;patrick.freed&lt;/a&gt;&#160;and I think this is a valuable ticket as it would add coverage for an important part of the spec. Also, the existing prose test is not implemented by all drivers.&lt;/p&gt;

&lt;p&gt;CC &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kaitlin.mahar&quot; class=&quot;user-hover&quot; rel=&quot;kaitlin.mahar&quot;&gt;kaitlin.mahar&lt;/a&gt; &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kevin.albertson&quot; class=&quot;user-hover&quot; rel=&quot;kevin.albertson&quot;&gt;kevin.albertson&lt;/a&gt; &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rachelle.palmer&quot; class=&quot;user-hover&quot; rel=&quot;rachelle.palmer&quot;&gt;rachelle.palmer&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2747802" author="shane.harvey" created="Tue, 21 Jan 2020 18:20:58 +0000"  >&lt;p&gt;Yeah I agree. Spec tests are always better and your checkOut idea seems simpler to implement than the prose test. I recommend removing the prose test when we make this change. (And &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-688&quot; title=&quot;Add &amp;quot;connectionError&amp;quot; as a valid &amp;quot;reason&amp;quot; for a ConnectionCheckOutFailedEvent when connection set up fails&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-688&quot;&gt;&lt;del&gt;DRIVERS-688&lt;/del&gt;&lt;/a&gt; was the tracking ticket for SPEC-1298).&lt;/p&gt;</comment>
                            <comment id="2747786" author="matt.broadstone" created="Tue, 21 Jan 2020 18:12:38 +0000"  >&lt;p&gt;Yes, I think it does but propose a unit test as the prose tests are easily missed (I don&apos;t think any DRIVERS tickets were made for that change either!).&#160;&lt;/p&gt;</comment>
                            <comment id="2747667" author="shane.harvey" created="Tue, 21 Jan 2020 17:27:58 +0000"  >&lt;p&gt;Do you think &lt;a href=&quot;https://github.com/mongodb/specifications/commit/ef782f2be3bfa32cb3c2befb63d85de142df31aa#diff-edf0cbe50936c131163dbceb123214d1R157&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;the prose test added&lt;/a&gt; in SPEC-1298 should cover this case?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                                        </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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_10257" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Documentation Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11861"><![CDATA[Not Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hvrsi7:</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>