ITCL object issue

[zombieZero]

In my automated environment, I launch a 'DUT object' that is mapped to the device being tested...I communicate with the CLI, etc all through this object.

This object gets created whenever I launch a config using a proc called 'readTestConfig'...this reads the config file, and spawns the DUT object, creates the telnet session, etc.

The issue I am experiencing occurs when I try to add another layer on top of that...along with the test automation, I also do automated reporting. The reporting was tied into the harness that launched the configs and ran the tests but now I want to move it to its own REPORT object.

My problem is this: The nightly regression tests are kicked off via a standalone script...I want to begin interacting with the REPORT object right away, so I spawn the object at the beginning. So far so good. The REPORT object hangs out while the script begins to run the first series of tests...it calls 'readTestConfig' and spawns the DUT object. Again, so far so good. However, once the tests are running I want the DUT object to interact with the REPORT object - it doesn't seem to be able to see it.

I've been fooling around with this...if I create the REPORT object right after the DUT object is created (at the end of readTestConfig) they can see each other fine. If I create the REPORT object in the standalone script that calls readTestConfig, then they can not see each other.

I assume this is a scope problem of some kind but I'm not sure how to resolve it...does anyone have any suggestions?

Thanks!

 

[Bong]

I don't really have anything to offer, but have you looked into threads?

_________________
Bob Rashkin

 

[zombieZero]

Hmm...how I'm actually thinking sockets might be the way to go for this...I'm thinking I can have the REPORT object open a server socket, and the DUT objects can just send the information that way. I kind of hit a snag there as well, but it's kind of a different topic so I'll start a new thread for that one...thanks!