Clovertech

testing tool (xlt) output

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › testing tool (xlt) output

  • Creator
    Topic
  • October 10, 2007 at 6:10 pm #49576
    Gary Atkinson
    Participant

      In testing a translation that someone else wrote I noticed some difference in the output using the testing tool versus the output through the engine (what I see in smat).  Shouldn’t the output in the testing tool be the same as what is in smat?  Now I say this knowing there can be pre-detail procs involved, but in this case there is none.  Its just a xlate that is used.  Any one else seen this type of thing  ❓

    • Creator
      Topic
    Viewing 4 reply threads
    • Author
      Replies
      • October 10, 2007 at 6:47 pm #62554
        John Hamilton
        Participant

          There are many place to change the contents of the message.

          Look at the TPS outbound data.

          But if there are not procs the data should be the same as the Xlate tester.

        • October 10, 2007 at 6:54 pm #62555
          Gary Atkinson
          Participant

            No procs in outbound tps.

          • October 11, 2007 at 12:52 pm #62556
            Gary Atkinson
            Participant

              Thanks Jim for the call yesterday.  Using your suggestion I made a copy of the xlate, remove all statements, but the MSH and the iterate w/ the concat statement.  Using this xlate, an extra value is still being outputed in the testing tool  😯 I went ahead an logged a case with support to see what they would say.

            • October 11, 2007 at 2:00 pm #62557
              Nate Kruse
              Participant

                I’ve seen this type of difference between testing with the tool and using th engine.  I wasn’t getting some values (such as filename) in the tool where I would get it in the engine.  This was probably because the file wasn’t actually getting passed the same way it does in the engine.

                Testing tools are nice, but most testing should be done using the engine since you won’t be using testing tools while in production.

              • October 16, 2007 at 5:58 pm #62558
                Gary Atkinson
                Participant

                  Issue has been resolved.  It helps when you use the inbound file to test  😉

              • Author
                Replies
              Viewing 4 reply threads
              • The forum ‘Cloverleaf’ is closed to new topics and replies.