Opened 4 years ago

Last modified 4 years ago

#4045 closed change

Add tests to the CMS — at Version 1

Reported by: sebastian Assignee:
Priority: P3 Milestone:
Module: Sitescripts Keywords:
Cc: jsonesen, kvas Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by sebastian)


Our CMS is used to generate the static content for websites like (source) and (source). It can be used in two modes, either to generate static files, or to run as a development server generating pages on demand, for more details see the README.

So far we have no automated tests for the CMS, hence future changes are quite risky and difficult to test. In particular, with the current consideration to migrate this code to Python 3, we'd need tests first.

What to change

Write a simple dummy website that uses every feature of the CMS. The tests then should generate the static files into a local folder as well as running the development server, comparing both the the generated files and the content delivered by the server against the excepted result. Also add a tox script to run those tests.

Change History (1)

comment:1 Changed 4 years ago by sebastian

  • Description modified (diff)
Note: See TracTickets for help on using tickets.