Opened on 05/17/2016 at 02:42:31 PM
Closed on 09/01/2016 at 09:53:44 AM
#4045 closed change (fixed)
Add tests to the CMS
| Reported by: | sebastian | Assignee: | jsonesen |
|---|---|---|---|
| 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)
Background
Our CMS is used to generate the static content for websites like https://adblockplus.org (source) and https://eyeo.com (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.
Attachments (0)
Change History (5)
comment:2 Changed on 05/18/2016 at 09:58:12 PM by jsonesen
- Owner set to jsonesen
comment:3 Changed on 08/21/2016 at 12:39:01 PM by jsonesen
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:4 Changed on 08/30/2016 at 03:11:07 PM by kvas
comment:5 Changed on 09/01/2016 at 09:53:44 AM by jsonesen
- Resolution set to fixed
- Status changed from reviewing to closed
A commit referencing this issue has landed: Issue - 4045 Add CMS Test Suite.
Unfortunately I missed the wrong format of commit message and our commit hook is too forgiving :|