Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure how testing a view is tricky.</p> <p>You just use the <a href="https://docs.djangoproject.com/en/dev/topics/testing/tools/#the-test-client" rel="nofollow noreferrer">test client</a>.</p> <p>Code coverage is easy. You reason how how a URL request maps to a code path and make the appropriate URL requests.</p> <p>You can, if you want, call the view functions "manually" by creating a Request object and examining the Response object, but this is too much work.</p> <p>If you have doubts about your code coverage, that's a good thing. It means you have code you can't easily map to a URL (which is all a user can ever see of a web application.) If you have code that doesn't map to a URL, you should probably either (a) delete the code or (b) refactor it into a separate module.</p> <p>We have lots of modules outside our view functions. Our view functions import these modules. We test these "outside the view function" modules with ordinary unittest.</p> <hr> <p>Here's a typical structure.</p> <pre><code>some_big_product/ |-- __init__.py |-- settings.py |-- urls.py |-- logging.ini |-- other_global_files.py |-- an_app_1/ | |-- __init__.py | |-- urls.py | |-- models.py | |-- views.py | |-- tests.py &lt;-- the generic Django testing | |-- app_specific_module.py | |-- app_specific_package/ | | |-- __init__.py | |-- test_app_specific_module.py &lt;-- unittest | |-- test_app_specific_package.py |-- generic_module.py |-- generic_package/ | |-- __init__.py |-- tests/ | |-- test_this.py | |-- test_that.py | |-- test_all.py &lt;-- not always practical |-- scripts/ |-- run_tests.sh </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow do I unit test Django Views?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USautodidacticon
    1. USS.Lott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I unit test Django Views?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHmm this could answer another question I have. How do you manage the directory structure when adding other modules in the django project/app hierarchy?
      singulars
      1. PO
      1. USThomas Schultz
    2. COThanks! That helps out a lot.
      singulars
      1. PO
      1. USThomas Schultz
    3. COHow might test_all.py work? I'm assuming I'd like to get everything into one big TestCase.TestSuite, and then run it. That way all test stats (passes & fails) are aggregated into a single output at the end. I can't decide whether I should be customising Django's "manage.py test" to run the extra unittests, or writing my own top-level test runner that incorporates Django's unit tests.
      singulars
      1. PO
      1. USJonathan Hartley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload