On Sat, May 17, 2014 at 10:36:20AM +0000, Antti Kantee wrote: > Well, "let's do TDD" is a bit of a pointy-haired decision ;)
My experience (again, in application development, not systems) has been the opposite. In my last job, for instance, a series of PHBs either didn't care that I was doing TDD or actively opposed it. On the other hand, they wanted me to do my work quickly and acceptably well. Knowing I'd disappoint them one way or the other, I chose to do my work quickly and well. It's possible that my experience has been atypical, but what I've seen is that TDD is sometimes a practice developers want for themselves, and almost never a practice managers want to impose on their developers. > * does it probe > * does it attach > * can I ifconfig up > * can I attach to a network > * can I send packets > * can I receive packets > * ... > > Yes, you can do TDD with rump kernels. [...] > If you really want to do fine-grained TDD, I think you'll in any case > end up doing TDTDD, when you need high-level tests to figure out what > the suitable low-level tests are. That's _precisely_ what I envisioned doing. If I undertake this, I'm in way over my head, but I at least seem to understand enough of what I don't understand. ;-) Thanks for the suggestion of where to start. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
