It would probably be possible to automate this via Selenium. What you could have is a build that runs a bunch of ‘tests’ that the sole purpose is call ‘captureEntirePageScreenshot()’ (or whatever it’s called in your language binding to Selenium).
A good place to crib ideas from would be SauceLabs: if you run a browser test suite with them, the report they give you is peppered with screenshots (and not just at failures, like Selenium usually does).
So on every merge to master/trunk, whatever your ‘screenshot’ build could run, regenerating all your screenshots.
Granted, this won’t help you if you need to modify the images at all (arrows, boxes, etc.), but you might be able to automate that bit, too.
> On Jan 26, 2015, at 11:37 AM, Owen Stephens <[log in to unmask]> wrote:
> I work on a web application and when we release a new version there are often updates to make to existing user documentation - especially screenshots where unrelated changes (e.g. the addition of a new top level menu item) can make whole sets of screenshots desirable across all the documentation.
> I'm looking at whether we could automate the generation of screenshots somehow which has taken me into documentation tools such as Sphinx [http://sphinx-doc.org] and Dexy [http://dexy.it]. However, ideally I want something simple enough for the application support staff to be able to use.
> Anyone done/tried anything like this?
> Owen Stephens
> Owen Stephens Consulting
> Web: http://www.ostephens.com
> Email: [log in to unmask]
> Telephone: 0121 288 6936