Tests are broken.

[dharhas]

We probably need to run tests locally and then push fixes. I'm going to merge pr #7 so we have testing enabled.

Error On Win:

======================================================================
ERROR: quest.scripts.test_settings (unittest.loader.ModuleImportFailure)
----------------------------------------------------------------------
ImportError: Failed to import test module: quest.scripts.test_settings
Traceback (most recent call last):
  File "C:\Miniconda\envs\test-environment\lib\unittest\loader.py", line 254, in _find_tests
    module = self._get_module_from_name(name)
  File "C:\Miniconda\envs\test-environment\lib\unittest\loader.py", line 232, in _get_module_from_name
    __import__(name)
  File "c:\projects\quest\quest\scripts\test_settings.py", line 8, in <module>
    quest.api.new_project('project1')
  File "c:\projects\quest\quest\api\projects.py", line 81, in new_project
    raise ValueError('Project %s exists, please use a unique name' % name)
ValueError: Project project1 exists, please use a unique name

Error On Linux & OSX:

 File "/home/travis/build/erdc/quest/quest/scripts/test_settings.py", line 21, in <module>
    dataset = quest.api.stage_for_download(feature, download_options={'parameter': 'streamflow'})
TypeError: stage_for_download() got an unexpected keyword argument 'download_options'
The command "coverage run --source=quest setup.py test" exited with 1.

[AaronV77]

Test are going to be our main object for this week for Quest. Here is an outline of what we are going to try and accomplish for this week.

Outline:

• Disable the task test ( is not working correctly )
• Have a nightly run test for Quest that will test all the providers.
  • If test pass then we are going to update a cache of the new available services.
  • If test fail, then we are just going to keep using the previous cache from the last passing test.
• Have a pull request test for Quest that will test the general code that is in the PR.
  • We are doing this to cut down on the run times.
• Get the Linux Python-2.7 tests working correctly.
  • There is something happening at startup that fails the test right from the start.

[AaronV77]

This was fixed in PR #64