UVR wrote: <snip>
> SUNWstc-checkenv. Checkenv is an independent tool, so you'll > essentially have to invoke checkenv directly (as opposed to > having the harness call it on your behalf, which is what STF > does). > >> My usage scenario is very simple one: before any of the test cases are >> run, check if the binary which is going to be tested is in place and >> executable; if not, bail out and do not execute any tests. > > It may help to look at the way in which STF invokes checkenv: > http://src.opensolaris.org/source/xref/test/ontest-stc2/src/tools/stf/include/stf_common.kshlib > I have returned to this again, sorry for the late reply. Although this is probably workable, I don't want to become a pioneer of closed streets and hack checkenv support into the test suite just to see it actually works. There is little benefit from doing this in the test suite itself. The main motivation is to do the checks just once per test suite run to avoid performing them uselessly over and over for each test case (and with CTI-TET I do not see a clean way how to do it for both positive and negative case). The proper place for calling checkenv script would be the run_test script I believe (which would avoid code duplication and make checkenv run just once per test suite run). v.
