Using the testing tool to run Django tests

edit

Yes, if you plan to run your tests using the Django test runner then you need to create a separate file for each launch configuration, add that file to the Testing tool and configure the launch configuration for that file in its File Properties under the Testing tab. Then clicking on one or the other will run tests with each launch configuration. The files can presumably just import the main manage with 'image manage' and then have the usual 'if __name__ == "file": main()' section.

Hello I am sorry but I do not understand you last suggestion. Should I write import manage in the main section of the file. ?

Yes. I think the files would just contain:

import manage
if __name__ == '__main__':
  manage.main()

Hello I do not understand the workaround you propose. You say I would need to set/reset the testing tab launch configuration on manage.py itself, in its file properties. Since each file has a specific launch configuration , I understand it would mean changing the manage.py file properties each time I need to run a test. Is this understanding is correct, it really drives to the testing tool being unusable as its main purpose is to be able to launch all tests in one click for non regression. It would be easier to give up the django project automatic configuration and manually set up a launch configuration for runserver, makemigrations etc... Could you document this other work around?

Wing expects to have just the one launch env per test file listed in the Testing tool so yes resetting the launch configuration on manage.py is not ideal, unless you do it only rarely. What might work better is to add multiple files to the Teseting tool that are either identical to or similar to manage.py and then you can set the right launch env in the Testing tab for each of those. Then no resetting of things in File Properties is necessary going forward.

I also saw in a test project I have here that in manage.py there can be something like "os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'dj2.othersettings')" at the top to select a different settings module, which maybe is another way to address this if you do have multiple manage_*.py's for testing.

And in case it's useful to you or someone else that reads this in the future: If you add other test files to the Testing tool, other than manage.py, those don't necessarily also have to use the Django testing framework. You can set the Test Framework to use to unittest or one of the others in the file's File Properties, under the Testing tab.

Hello Please excuse me. Yes I had not changed the Default Test Framework in the project properties as your comment suggested that I did not use Django Test Framework. Yes I do use it but it is specified in the launch configuration of each file. After resetting the default testFramework, I got rid of the manage.py problem. However I do run into another problemfor which I will open another question. Thanks for your help

Glad that helped!

Which test framework you tell Wing to use doesn't have any effect on other parts of the project configuration, e.g. debugging Django templates. If tests don't work when invoked by unittest it's because the setup magic done by manage.py hasn't been done. I think there is a way to do that manually in your test's setUp() call but I don't know Django well enough to tell you how that's done. I do know you need to make sure DJANGO_SETTINGS_MODULE is defined, but presumably that already is in your Project Properties. You can probably search around using the specific error string you are getting or ask in a Django-specific forum about how to run your tests using unittest and not manage.py.