[yarg]

It actually amazes me the degree to which people just don't realise that what they are doing can be automated - even in software companies.

I caught my manager one day, manually traversing application screens taking screenshots and then clipping them down to size.

At least an hour's work, with each and every release (or at least those with configuration changes).

"Raise a ticket, I can do that automatically."

An hour later I sent her back the task for testing - now taking mere seconds, and with pixel perfect clipping.

It never even occurred to her to ask if that was something I could do.

[mandeepj]

> "Raise a ticket, I can do that automatically."

Can you elaborate what you did? One option I can think of - Selenium like UI testing\navigation tool and taking screenshots?

[yarg]

It was a swing application (the company's deployment tooling).

I ran through the configuration definitions and for each element created a BufferedImage the preferred size of the associated component.

Then I rendered the component to the BufferedImage using BufferedImage::getGraphics, and Component::paint.

Then I saved the image as <definition>.PNG.

Nothing magical.

[ipaddr]

Why have we ended up in a place where a developer is asking a manager to raise a ticket so they are allowed to create something only she will see. What happens if you just did it without the ticket?

[yarg]

For the commit message, for time-keeping, in order to assign it back to her when the changes were made.

[ElCapitanMarkla]

Could just be so you have a ticket to record time against.