Invalid selenium.jar in the tmp directory leads to confusing errors about testium HOT 5 CLOSED

Temporary workaround (OSX): rm -r $TMPDIR"testium"

from testium.

The downloads are validated immediately, but it appears to leave the bad file in the temp directory. We should remove the file if it fails. If we do that, I don't think that we need to store the checksum.

We can certainly add a command that clears the temp directory and then downloads the latest version, like forceUpdate.

from testium.

There's always Ctrl+C (I know I pressed that from time to time during npm install), so I'm not sure removing the bad file will work 100%. But as long as there's a command for forcing a clean re-download, I think we're fine. Maybe we can even check for "Invalid or corrupt jarfile" and suggest that command when the startup fails?

from testium.

Yeah, that sounds good to me. I'll get to it probably next week, unless someone wants to send a PR before that.

from testium.

PR: groupon/selenium-download#9

Tracking this there, now.

from testium.