# data[].attributes.body
Test on Saucelabs: David

# data[].attributes.body
Create E2E doc page => Start Jürgen

# data[].attributes.body
First iteration on that template.

# data[].attributes.body
We have no solid strategy (Edge, IE, Firefox, Safari) we use 99.99% Chrome on Mac

# data[].attributes.body
That would be nice

# data[].attributes.body
Waiting for execution on jenkins is not ideal.
We also need to release granite.ui.content before being able to run the e2e tests.

# data[].attributes.body
I think we advanced towards our goal.

# data[].attributes.body
Understanding the JCR context a little better.

# data[].attributes.body
Legacy code hard to maintain. Hidden bugs

# data[].attributes.body
work only after releasing in QS

# data[].attributes.body
Before testing

# data[].attributes.body
Found crucial bugs on other browsers (Omnisearch Firefox)

# data[].attributes.body
3th party items failed our test (tutorial popup that blocks UI)

# data[].attributes.body
Writing e2e tests is good for regression and for providing user stories.

# data[].attributes.body
Takes a lot of time to make it work.