Details

    • Type: Sub Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Complete
    • Affects Version/s: 1.0.1, 1.0.1.1
    • Fix Version/s: 1.0.1.1, KFS Release 3.0.1
    • Component/s: Unit Testing
    • Labels:
      None
    • Rice Module:
      KEW

      Description

      As described in the parent Jira this part of the task deals with creating, or using existing, data dictionary test information.

      Basically the xml and bootstrap info needed to test the data dictionary doc search features.

        Attachments

          Activity

          Hide
          jksmith James Smith added a comment -

          Thanks Chad.

          Show
          jksmith James Smith added a comment - Thanks Chad.
          Hide
          chagstrom Chad Hagstrom added a comment -

          Yes, you can go ahead and resolve this; I have plenty of test documents to work with now. Thanks for your help!

          Show
          chagstrom Chad Hagstrom added a comment - Yes, you can go ahead and resolve this; I have plenty of test documents to work with now. Thanks for your help!
          Hide
          jksmith James Smith added a comment -

          Chad, I'm at a point where I can resolve this, right? Thanks!

          Show
          jksmith James Smith added a comment - Chad, I'm at a point where I can resolve this, right? Thanks!
          Hide
          jksmith James Smith added a comment -

          Well, there's a question I wish I knew the answer to : - >

          Do we need to run the kns.sql ourselves, perhaps on some test data source? I'm trying the test locally...

          Show
          jksmith James Smith added a comment - Well, there's a question I wish I knew the answer to : - > Do we need to run the kns.sql ourselves, perhaps on some test data source? I'm trying the test locally...
          Hide
          chagstrom Chad Hagstrom added a comment -

          James, I've just submitted a couple changes of my own, most notably to the unit test class itself. However, I've left the @Ignore annotation present on the unit test method for now because I'm getting this error when attempting to route the test document:

          • SQLException during execution of sql-statement:
          • sql statement was 'SELECT A0.DOC_HDR_ID,A0.OBJ_ID,A0.VER_NBR,A0.ACCT_NUM,A0.ACCT_OWNR,A0.ACCT_BAL,A0.ACCT_OPN_DAT,A0.ACCT_STAT,A0.ACCT_UPDATE_DT_TM,A0.ACCT_AWAKE FROM ACCT_DD_ATTR_DOC A0 WHERE A0.DOC_HDR_ID IN '
          • Exception message is [ORA-00942: table or view does not exist
            ]
          • Vendor error code [942]
          • SQL state code [42000]

          Any idea why it can't find the table (if that's what is causing this problem)? Or is this something that we won't need to deal with once the bootstrapping is fully configured?

          Show
          chagstrom Chad Hagstrom added a comment - James, I've just submitted a couple changes of my own, most notably to the unit test class itself. However, I've left the @Ignore annotation present on the unit test method for now because I'm getting this error when attempting to route the test document: SQLException during execution of sql-statement: sql statement was 'SELECT A0.DOC_HDR_ID,A0.OBJ_ID,A0.VER_NBR,A0.ACCT_NUM,A0.ACCT_OWNR,A0.ACCT_BAL,A0.ACCT_OPN_DAT,A0.ACCT_STAT,A0.ACCT_UPDATE_DT_TM,A0.ACCT_AWAKE FROM ACCT_DD_ATTR_DOC A0 WHERE A0.DOC_HDR_ID IN ' Exception message is [ORA-00942: table or view does not exist ] Vendor error code [942] SQL state code [42000] Any idea why it can't find the table (if that's what is causing this problem)? Or is this something that we won't need to deal with once the bootstrapping is fully configured?

            People

            • Assignee:
              jksmith James Smith
              Reporter:
              gtaylor Garey Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: