You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/04/10 12:47:00 UTC

[jira] [Closed] (TINKERPOP-2194) Enforcing an order on properties in one test method of ChooseTest

     [ https://issues.apache.org/jira/browse/TINKERPOP-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-2194.
---------------------------------------
       Resolution: Fixed
         Assignee: stephen mallette
    Fix Version/s: 3.4.2
                   3.3.7

Thanks for mentioning this. Fixed via CTR with https://github.com/apache/tinkerpop/commit/03234d22530d309fa76fd477e90809e7041f0cb6

> Enforcing an order on properties in one test method of ChooseTest
> -----------------------------------------------------------------
>
>                 Key: TINKERPOP-2194
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2194
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: test-suite
>    Affects Versions: 3.4.2
>            Reporter: Moayad Alyaghshi
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.3.7, 3.4.2
>
>
> The test method "g_V_chooseXout_countX_optionX2L__nameX_optionX3L__valueMapX" in the test class "ChooseTest" in enforcing an order on the properties. According to my understanding, this's not expected from the data model.
> You can see that in the following assertion:
> {code:java}
> assertEquals(Long.valueOf(1), counts.get("{name=[marko], age=[29]}"));
> {code}
> If the order is different, then the test will fail.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)