Website UI and CMS testing

Where do you draw the line between testing a CMS integration with CSS / html templates and actually testing the 'Out of the Box' CMS functionality itself? I'm interested to hear people's points of view on this one? Often in my life I've been told "You don't need to test creating a page or adding an ordered list because that's 'out of the box' CMS functionality. But if you don't do this , how do you test the integration with the front end?

Any help or ideas welcome :-)

Do we need to change test documenation to be fit into Agile testing methods?

I'm in the process of re-desigining our test documentation to fit into a more agile development methodology. I'm leaning towards the user of storyboard designs with tests written on the back of cards for each functional element. This seems to be the way to go for me, but I'm interested if anyone has any experience of using this practically on web based projects.

Does it work?
Does it save time?
Does agile testing improve quality rather than standard testing against requirements?

How do you involve testing earlier in the developement lifecycle?

I'm looking into involving testers much earlier in the development life cycle. I want them to be involved during development, testing and adding value. There's things to consider here such as the cost of training, the testers comfortableness with testing when requirements are not clearly defined and documented. I'm keen to add more value than currently formal system testing adds at the end of the development process.

If anyone has any interesting points or is currently providing testing services in a digital media world (as I an), then please post and let me know.

Looking forward to hearing from you

Agile Testing

Over the coming weeks I will be researching Agile test methods. Over the next few months I will be attempting to integrate these methods into my workplace.
Stay in touch with the blog to see the outcome