Proposed type of test: chrome Proposed location of test: toolkit/mozapps/downloads/tests/chrome

Note: as long as we have a test that checks that double clicking performs the same action as enter (which we either do, or you are making one), you do not need to do that part of the test. You'll also probably want to add downloads to the database in an already canceled state so you don't have to cancel them (we test canceling in the UI in another test as well).

I had named this bug wrongly. I have updated the name of this bug to the right test. Sorry for the inconvenience caused.

I have added this test to test_basic_functionality.xul The test works. Have run and checked it. The only issue is that the download completes before I can do the check. We need to check how we can keep pumping data continuously till we do the check. Also I have experience a strange thing. I am not able to fathom the reason for the issue. I have included utils.js in the file. I have cleanUp() and addDownload() in utils.js. But if I use the functions in utils.js the test hangs. This is the reason I have included addDownload as an inner function in the test and have not called cleanUp() To confirm that the test works, I have checked the parameters and the values of the downloads in the middle of running

Comment on attachment 329827 [details] [diff] [review] v3.0 I have a better idea on how to to test this, without needing to download anything. Each test function will be able to get the window, so you need to just do something like: aWin.gDownloadProgressListener.onStateChange(Ci.nsIDownloadManager.DOWNLOAD_QUEUED, { /* dummy data to represent an nsIDownload */ });