Not only the execution of an automation may produce unwanted evidence, but also its development process.
For example, traces of software, libraries, files used to implement the automation may remain on the TS in the form of temporary data, unlinked blocks on the disk, filesystem metadata, operating system records, etc.. In general,
the development environment should meet some specific requirements: (1) it should be totally isolated from the TS, so that no evidence of the development process is left on the TS; (2) it should be temporary, since it is, in its complexity,
an unwanted evidence to be destroyed; (3) it should be as similar to the TS as possible,
since the automation implemented/tested on this environment should be exported and executed on the TS without a hitch.
There are many techniques to create a proper development environment: