Slogging Through the Big Testing Cycle
Today has been a lot of little things that came out of the continuing testing cycle with the traders. The greek engine is at the core of quite a few products that are switching over to it as the source of their information, and it's creating quite a mess about it. Lots of people sending in the same issues, not realizing that someone else is reporting the same thing, etc. Then we're purposefully not fixing things in the code they are testing because the management of this testing cycle didn't want to shift the testing underneath them. Truth be told, I'm not a fan of this scheme, but I can't say it's wrong either. The thought is that this is what they are testing, and if the rack up 100 bugs that are all the same thing, then when we fix that, it'll be easy to check those 100 things again and prove they are all working.
I'm more of the "fast waterfall" testing - find a bug, fix it, repeat as quickly as possible. This has the problem that you're always "starting" the testing process. The upside is that you aren't going to find 100 bugs with the same cause - only one.
So I'm trying to make sense of this and keep my head above water. It's hard, because work is becoming oppressive again, and my ability to post is getting beaten out of me. I have to fight the urge to just give up on posting, as it's about the only thing I can always look at and be happy about.