Currently, tests for the JavaScript API for Downloads place download target files directly under the system temporary directory. This works fine, but it has been suggested that they could be moved to their own folder. Alternatively, the test suite could provide a folder upon request. These aspects should be taken into account: - The new directory under the temporary directory should not be left behind, but should be deleted at the right time when the tests in the file or group of files are finished. - The directory name itself should include a random part or be created with a unique algorithm, since its creation and deletion can happen while several tests are running in parallel. One tricky part about the directory deletion is that Windows queues up deletions rather than performing them immediately. This may create intermittent failures if using a unique algorithm rather than a random number based one. Also, the queued up deletions of the files inside the folder may or may not have an effect. A try run of several dozens Windows jobs should verify that we don't regress the intermittent failures, whatever approach we take.