4 ms·
I mean that if asciinema examples in the readme tends to get outdated (ed2: "stale") , they should be kept up to date via CI and (probably) be part of the integ
by e12e 5y ago
I mean that if asciinema examples in the readme tends to get outdated (ed2: "stale") , they should be kept up to date via CI and (probably) be part of the integration tests; if a commit changes the ux/interaction tests should reflect that, and documentation should be easily (automatically) updated?
Ed: like if you for a web app have selenium/browser tests that somehow also takes screenshots that become part of the documentation?
- stavros 5y agoAh, I see. That's probably a bit too much tooling for a small OSS utility, manual updates would get me a long way there. The other issue is that it doesn't matter that the UI is exactly up to date, just good enough to give the user an idea of the functionality.
- ZeroGravitas 5y agoIt's a generally good idea though, website screenshots (and thinking about it now, animations) from test automation is another similar task. Not quite standard practice, though some people do bits of it here and there, but both probably should become so which would amortize the cost over lots of cli tools.