I have an option set fred.opt
I open it and run some tests.
I change some options just to try some more stuff out.
I then close the option set down and reopen it in the hope I am back where I started.
Oh dear, silktest had saved those options I changed over the top of the original fred.opt settings.
So the innocuous 'Close Options Set' actually saves any 'temporary' changes you have made over the top of the option set you have open at the time.
I tried this with some Agent options and some Extension options. I checked the actual .opt file and sure enough the changes had been saved.
Nasty. Really very nasty.
Surely you should have to save a new option set to make this happen...?
Saving any options will cause SilkTest to write the saved settings to the current .INI file. Opening an Option Set sets the option set file to act as the new .INI file. That's just the way it works. You may want to try to create a read only .OPT file and that way SilkTest can write to it.
Setting the .opt file read-only means you can't change any options when that option set is loaded.
It seems it would have been more intuitive -instead of continually writing to the .opt file whenever you change an option - to have loaded the .opt information into memory and change the settings there, then if you try to quit silktest or close the .opt file, silktest could do a compare to the .opt file on disc and prompt the user to save the new options or not.
I know the way it works is the way it works, but, the point is, the way it works is really bad [img]images/icons/wink.gif[/img]