To run browser tests, open a new Terminal window or tab and change to the project directory, then tell gulp to start the tests:
gulp build gulp test:acceptance ( tox -e acceptance can be run as well )
Decorative images don’t add information to the content of a page. For example, the information provided by the image might already be given using adjacent text, or the image might be included to make the website more visually attractive. 
Images may be deemed decorative when they are :
|# Decorative images|
|Decorative images don’t add information to the content of a page. For example, the information provided by the image might already be given using adjacent text, or the image might be included to make the website more visually attractive. |
|Images may be deemed decorative when they are :|
|- Visual styling such as borders, spacers, and corners;|
|- Supplementary to link text to improve its appearance or increase the clickable area;|
|- Illustrative of adjacent text but not contributing information (“eye-candy”);|
Our testing philosopy and policy is explained in the following documents:
I would only add that our Acceptance tests should focus on testing functionality and dom structure. Testing content becomes tricky because it's constantly changing via the CMS or some other channel. This is demonstrated in the following example:
#Notes on Frameworks
We opted not to use any frameworks; the application isn't a SPA (single page application) and we didn't think it's level of complexity warranted using one. This might be a mistake and it's worth revisiting this decision, now that we have migrated to Atomic design.
The pros / cons of that decision are as follows:
- Smaller builds and minimal markup ( JS, CSS, HTML). Many frameworks are bloated and applications only use a small portion of their functionality / features.
I highly suggest reading http://www.ebaytechblog.com/2014/10/02/dont-build-pages-build-modules/. It encompasses exactly what we are trying to achieve by building components using atomic design. I also want to stress that our front-end atomic architecture is still evolving.