gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kazuomi Kashii (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (GORA-53) Add Gora-Cassandra tests
Date Thu, 12 Jul 2012 17:23:36 GMT

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

Kazuomi Kashii edited comment on GORA-53 at 7/12/12 5:22 PM:
-------------------------------------------------------------

I have updated setUp() method of DataStoreTestBase.java as follows:

  public void setUp() throws Exception {
    //There is an issue in JUnit 4 tests in Eclipse where TestSqlStore static
    //methods are not called BEFORE setUpClass. I think this is a bug in
    //JUnitRunner in Eclipse. Below is a workaround for that problem.
    if(!setUpClassCalled) {
        setUpClass();
    }   // <========================= I moved this bracket from the end.

    log.info("setting up test");
    if(testDriver != null) {
      employeeStore = testDriver.createDataStore(String.class, Employee.class);
      webPageStore = testDriver.createDataStore(String.class, WebPage.class);
      testDriver.setUp();
    } else {
      employeeStore =  createEmployeeDataStore();
      webPageStore = createWebPageDataStore();

      employeeStore.truncateSchema();
      webPageStore.truncateSchema();
    }
  // }  <==== originally here !!
  }

then, the test itself began to work, but I got the following numbers:

Tests run: 51, Failures: 1, Errors: 48, Skipped: 0

                
      was (Author: kazk):
    I have updated setUp() method of DataStoreTestBase.java as follows:

  public void setUp() throws Exception {
    //There is an issue in JUnit 4 tests in Eclipse where TestSqlStore static
    //methods are not called BEFORE setUpClass. I think this is a bug in
    //JUnitRunner in Eclipse. Below is a workaround for that problem.
    if(!setUpClassCalled) {
        setUpClass();
    }   // <========================= I moved this bracket from the end.

    log.info("setting up test");
    if(testDriver != null) {
      employeeStore = testDriver.createDataStore(String.class, Employee.class);
      webPageStore = testDriver.createDataStore(String.class, WebPage.class);
      testDriver.setUp();
    } else {
      employeeStore =  createEmployeeDataStore();
      webPageStore = createWebPageDataStore();

      employeeStore.truncateSchema();
      webPageStore.truncateSchema();
    }
  // }  <==== originally here !!
  }

then, I got the following:

Tests run: 51, Failures: 1, Errors: 48, Skipped: 0

                  
> Add Gora-Cassandra tests
> ------------------------
>
>                 Key: GORA-53
>                 URL: https://issues.apache.org/jira/browse/GORA-53
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: storage-cassandra
>    Affects Versions: 0.1.1-incubating
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Critical
>             Fix For: 0.3
>
>         Attachments: GORA-53-v2.patch, GORA-53.patch, GORA-54-v8.patch
>
>
> As per this thread [1], it is absolutely essential that we get some tests for the Cassandra
module. Therefore this task should act as a summary task to manage all test which are hereby
proposed.
> Realistically, this is going to take a good while, so I have marked it for 0.2 and 0.3-incubating
releases.
> [1] http://www.mail-archive.com/gora-dev@incubator.apache.org/msg00241.html 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message