mirror of
https://github.com/TryGhost/Ghost.git
synced 2025-01-20 22:42:53 -05:00
034f7d9a55
refs: https://github.com/TryGhost/Toolbox/issues/168 - Having large theme fixtures makes tests run slower, so we're working to reduce them - This fixture was a full copy of a very old version of Casper, but all we needed was a handful of files so that the tests can run - This theme is also used for testing members, not just price data so I've renamed it for clarity - The remaining files is the bare minimum we need to test these features |
||
|---|---|---|
| .. | ||
| broken-theme | ||
| casper | ||
| casper-1.4 | ||
| locale-theme | ||
| members-test-theme | ||
| test-theme | ||
| test-theme-channels | ||
| casper.zip | ||
| invalid.zip | ||
| README.md | ||
| valid.zip | ||
| warnings.zip | ||
Modifying theme fixtures
When a new rule is introduced in gscan one of these fixture files might break and you'll have to update a "zip" which isn't as easy as opening a text editor... It could become that one day but for now here are some commands to help out with the edit process
- Unzip the theme files, e.g.:
cd $CURRENT_DIR && unzip valid.zip -d valid - Make a change in the file which caused a warning/error/whatever
- Zip the files back:
zip -r valid.zip ./valid - Commit changed zip file:
git add valid.zip ;... you know the drill :)
Ideas for future improvements in theme tests:
- Decouple tests from file system as much as possible
- Track contents of what is in "zips" in source control. Right now, having a diff on a binary file is not useful at all