-
Notifications
You must be signed in to change notification settings - Fork 800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Themes #1
Comments
Proposal:
The look of the page should not change at all during these steps. Might be a use case for PhantomCSS. When finished, the semantic classes can be used as an API for custom CSS styling. Notes on the CSS classes: I have been playing with stuff based on Simple Naming for Modular CSS Class Names and settled on giving most elements a three point identifier like While using double dashes raises eyebrows at first, these classes have not only been a breeze to style, but also to write tests for. I'll try to send a PR for step one. |
@wwebfor How do I start the app locally? |
@filtercake, you should compile less file with grunt task: grunt lessc |
- failed screenshots folder is in base directory. that way a git status will output a list with failed test diff images
- without any more setup, fail screenshots need to be manually removed from failure/ and test/visual/screenshots - an automated setup in grunt should clean up failures when tests are back to green. - a watch task for the failures folder could open an interface where you approve a failed test image as still passing or mark a new master (which should trigger the tests again). see csscritic.
- screenshot folder is now ignored by git - failures folder moved to test directory and is not ignored. - that way failed tests show up as untracked files in git status.
- failed screenshots folder is in base directory. that way a git status will output a list with failed test diff images
- without any more setup, fail screenshots need to be manually removed from failure/ and test/visual/screenshots - an automated setup in grunt should clean up failures when tests are back to green. - a watch task for the failures folder could open an interface where you approve a failed test image as still passing or mark a new master (which should trigger the tests again). see csscritic.
- screenshot folder is now ignored by git - failures folder moved to test directory and is not ignored. - that way failed tests show up as untracked files in git status.
Added notes search form
No description provided.
The text was updated successfully, but these errors were encountered: