expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-26 22:25:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Django version documn

Browse Source
This commit is contained in:
Philip Sargent
2023-02-11 23:04:08 +00:00
parent 069609e814
commit 678326aae3
6 changed files with 7 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
handbook/troggle/trogtests.html
View File

@@ -10,7 +10,7 @@
<h1>Handbook Troggle - Automated Testing</h1>
<h2>Troggle Automated Testing</h2>
<p>We have a suite of more than 70 <a href="https://en.wikipedia.org/wiki/Smoke_testing_(software)">smoke tests</a>
<p>We have a suite of more than 85 <a href="https://en.wikipedia.org/wiki/Smoke_testing_(software)">smoke tests</a>
which are run manually by troggle programmers like this:
<pre><code> troggle$ python manage.py test -v 1</code></pre>
@@ -49,7 +49,7 @@ No tests are run with the real expo database.
<p>As yet we have no test database set up, so the in-memory database starts entirely empty. However we have 'fixtures' in
<var>troggle/core/fixtures/ </var>
which are JSON files containing dummy data which is read in before a few of the tests.
which are JSON files containing dummy data which is read in before a few of the tests. (Though current wisdom is that <a href="https://lukeplant.me.uk/blog/posts/test-factory-functions-in-django/">factory methods in the test suite</a> are a superior way of managing tests for very long-term projects like ours.)
<h4>Automated testing on the server</h4>
<p>Something is stopping the test suite running on the server. We haven't fixed this yet.