Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Merge branch 'master' of https://github.com/collective/tutorial.todoapp

  • Loading branch information...
commit e4acc80e04d6c5163cc777af7bc21b2dc0a3ce5e 2 parents 4ae5ab7 + bde9308
@eleddy eleddy authored
Showing with 37 additions and 16 deletions.
  1. +0 −2  buildout.d/versions.cfg
  2. +37 −14 docs/chapter_3.rst
View
2  buildout.d/versions.cfg
@@ -26,8 +26,6 @@ Products.PrintingMailHost = 0.7
setuptools-flakes = 0.1
sourcecodegen = 0.6.14
Sphinx = 1.0.7
-Jinja2 = 2.6
-Pygments = 1.5
z3c.pt = 2.2
z3c.recipe.scripts = 1.0.1
zptlint = 0.2.4
View
51 docs/chapter_3.rst
@@ -41,19 +41,19 @@ Static resources
The template displays different icons for different workflow states of your
Todo Items. We need to add these icons to your package:
- #. Download ``open.png`` and ``completed.png`` from GitHub (they are in
- ``src/tutorial/todoapp/browser/static``) into a new folder on your local
- computer: ``src/tutorial/todoapp/browser/static``.
- #. Tell Zope that this ``static`` folder contains static resources (icons,
- CCS files, JavaScript files, etc.) by adding the following lines to
- ``src/tutorial/todoapp/browser/configure.zcml``:
+#. Download ``open.png`` and ``completed.png`` from GitHub (they are in
+ ``src/tutorial/todoapp/browser/static``) into a new folder on your local
+ computer: ``src/tutorial/todoapp/browser/static``.
+#. Tell Zope that this ``static`` folder contains static resources (icons,
+ CCS files, JavaScript files, etc.) by adding the following lines to
+ ``src/tutorial/todoapp/browser/configure.zcml``:
- .. code-block:: xml
+ .. code-block:: xml
- <!-- Publish static files -->
- <browser:resourceDirectory
- name="tutorial.todoapp"
- directory="static" />
+ <!-- Publish static files -->
+ <browser:resourceDirectory
+ name="tutorial.todoapp"
+ directory="static" />
After restarting your Zope server, files in your ``static`` folder will be
available on a standard URL:
@@ -76,6 +76,29 @@ Tests
Cool, so you have verified that your code works through the browser and it's
time to add tests to make sure your code keeps on working in the future.
-This chapter comes with only one test file: ``test_todo_view.py``. Get it from
-GitHub, put it in your ``tests`` folder and run tests. Then fiddle around with
-it to see what it does.
+First add the following snippet to ``test_setup``:
+
+.. code-block:: python
+
+ # types/Folder.xml
+ def test_folder_available_layouts(self):
+ """Test that our custom display layout (@@todo) is available on folders
+ and that the default ones are also still there.
+ """
+ layouts = self.portal.folder.getAvailableLayouts()
+ layout_ids = [id for id, title in layouts]
+
+ # default layouts
+ self.assertIn('folder_listing', layout_ids)
+ self.assertIn('folder_summary_view', layout_ids)
+ self.assertIn('folder_tabular_view', layout_ids)
+ self.assertIn('atct_album_view', layout_ids)
+ self.assertIn('folder_full_view', layout_ids)
+
+ # our custom one
+ self.assertIn('todo', layout_ids)
+
+
+Then add a new test module: ``test_todo_view.py``. Get it from GitHub, put it
+in your ``tests`` folder and run tests. Then fiddle around with it to see what
+it does.
Please sign in to comment.
Something went wrong with that request. Please try again.