2 ms·
Going from prototype to tested code is possible. Here's how I'm doing it, for command line tool that provides local development environment for remote Kubernet
by itamarst 10y ago
Going from prototype to tested code is possible.
Here's how I'm doing it, for command line tool that provides local development environment for remote Kubernetes cluster (https://datawire.github.io/telepresence/ https://datawire.github.io/telepresence/):
1. Build prototype, test manually.
2. Have coworkers try it out.
3. Fix UX based on feedback, test manually.
4. Once initial UX was nailed down, write end-to-end tests.
Beyond adding features, next I will rewrite the core using test-driven development (TDD), so that the internals are maintainable. and the end-to-end tests will ensure the basic functionality continues to work.
The UI is fairly simple, and at this point I have confidence that it won't change multiple times in a day, so it's worth the effort to stop relying solely on manual testing and write some automated UI tests.