This week has been a bit of fun for me. After the USB simulation infrastructure I started to write about in my last post- and never got close to finishing the description of, I began working on my dream test setup, for use in some work I knew was coming.
The core concept for me was to have a context shared among all the participants in a test- the test application and all the drivers in the stack, to have it fully readable and writable by all of them, to have provision for them to signal one another in a structured way- and to not utilize the usual I/O paths to do so. Then to package that in some reusable library code with suitable application-specific extension points.
I'm not done by any means, but what I've got so far is proving usable and it makes me happier than what I've had to deal with previously:
Well, this week, I started on Monday afternoon to combine that with the USB simulation infrastructure to address a current test need (yes, I'm being purposefully vague). On Wednesday evening, I had:
Not a lot, but it proved it could be done, and provides a foundation to build on- and it even found a product bug (again, can't tell you where- but you're never going to see it, anyway- I got there and got it fixed before it made its way out to you).
Not particularly trend-setting- twitter's not going to be ablaze with this, and I'm not going to be winning any awards because of this- but I'm going to be happy about it, anyway. I'll get paid for it, and I don't think anyone really got hurt by all of that. When I move on, I still believe most of it will get thrown away the first time anyone looks closely at my code (I've decided to keep my reasons for believing that to myself). But that's OK- I get to eat, kid gets through college- I'm not expecting fame or glory, and that's good, because its not likely I'll be seeing either. LOL...
Today it's verifying bug fixes, but I'll get back to work on it tomorrow- add pipes and I've got more test-type stuff needs doing before I can put this toy aside...