[test] Python-Django test plan
Bug #1416108 reported by
nicopace
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-django (Juju Charms Collection) |
New
|
Undecided
|
nicopace |
Bug Description
I plan to improve this charm by adding this tests:
* improve basic test by checking if the service is running ok (accessing a public url, and an authenticated url)
* test deploying using a site template
* test deployment with gunicorn
* test using code repository
* test dpaste configuration example, from README
* test "upgrade charm"
* test fabric commands
* test application subordinate charm
* test django_version, for different options like ppa, pip like or url
* test unit-config, as it is not clear what it is for
* test urls_dir_name and urls_injection_
* test different databases relations
* test memcached
* test settings injection
To post a comment you must log in.
I recommend adding tests for settings injection.
Do you need to test fabric or will it get dropped when the ansible work is done?
I have a branch of this charm where I have added nagios checks and I have a mojo spec with a verify phase that runs http_check which does nicely for your first item in the list.