5 ms·
So you've got a working prototype, which is 80% of the way towards your spec (which changes by the day, mind you) where and when do the tests then get written?
by yomly 10y ago
So you've got a working prototype, which is 80% of the way towards your spec (which changes by the day, mind you) where and when do the tests then get written? Do you start from scratch when you go from prototype to product? Is that feasible in a tiny lean startup with few developers and real hard fast deadlines?
- itamarst 10y agoGoing 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.
- kkapelon 10y agoIf you have a spec that changes by the _day_ = it means you don't have a spec. You are still prototyping. So yes, start writing unit tests when you no longer prototype.