Scott Lawrence wrote: > I'm not sure that this kind of test actually qualifies as a 'unit test' > - it is actually testing multiple components simultaneously. I think > that unit tests should strive to test exactly one component (or less - > test only parts of the code within a component) by simulating other > components rather than actually using them. In this case, if the test > were simulating the supervisor then this path issue would not arise. > This really isn't a unit test - it's a mini-system test, which is much > harder (we have _lots_ of problems with this kind of test in the server > side). >
I think you may have misunderstood Bogdan. He is not writing any tests. This is for XCF-2954 - Package Updates: Update the other nodes in a cluster. sipXconfig uses XML-RPC to execute system updates through sipXsupervisor (SwAdminRpc). sipXsupervisor, in turn, returns the path of a file which contains the "yum update" output. sipXconfig has to then retrieve this file through the HTTP server in sipXsupervisor, and parse the yum output. Now, while this works fine in a standard ISO system, it will fail in some developer environments, due to the presence of "../" in the filename (because of the --prefix value, as you had pointed out earlier). Arjun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
