[jira] [Commented] (GEODE-2433) Backwards compatibility tests are not actually running

["Dan Smith (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854583#comment-15854583 ] 

Dan Smith commented on GEODE-2433:
----------------------------------

[~bschuchardt] - It looks like the build.gradle file for geode-old-versions was never checked in? I see it back in this old review request - https://reviews.apache.org/r/55688/diff/1#13.

We should also make sure the tests fail if we can't load the old versions.

> Backwards compatibility tests are not actually running
> ------------------------------------------------------
>
>                 Key: GEODE-2433
>                 URL: https://issues.apache.org/jira/browse/GEODE-2433
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>            Reporter: Dan Smith
>            Assignee: Bruce Schuchardt
>             Fix For: 1.1.0
>
>
> We have several backwards compatibility tests checked in -
> RollingUpgradeDUnitTest
> RollingUpgrade2DUnitTest
> ClientServerMiscBCDUnitTest
> These tests are all parametered by the list of old versions to run against.
> However, it looks like the code to get the list of old versions incorrectly just logs a message and continues on if it can't find a file called geodeOldVersionClasspaths.txt. That file does not exist and is not being generated as far is I can tell. The entire project - geode-old-versions, is completely empty.
> The net effect is these tests don't actually run, because the list of parameters is an empty list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)