You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we're talking tests for genesis itself rather than a genesis based site, we could run syntax checks on the playbooks:
# presuming that $HOME is the root of a checked out genesis repo...# symlink INCEPTION
mkdir -p $HOME/generator/app/templates/bower_components
ln -s $HOME$HOME/generator/app/templates/bower_components/genesis-wordpress
# run bin/provision for syntax checks
chmod +x $HOME/generator/app/templates/bin/provision
sudo $HOME/generator/app/templates/bin/provision --syntax-check
I think we'd need to confirm the genesis-based site so that the full provisioning script can be confirmed. Which means, most of the tests will rely on travis, but a local Vagrantfile for testing would suffice, too.
Activity
EvanK commentedon Nov 20, 2013
If we're talking tests for genesis itself rather than a genesis based site, we could run syntax checks on the playbooks:
ericclemmons commentedon Nov 20, 2013
I think we'd need to confirm the genesis-based site so that the full provisioning script can be confirmed. Which means, most of the tests will rely on travis, but a local Vagrantfile for testing would suffice, too.