Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Has anyone other than you actually tried to use the new system yet?

    I find that when I’m the only one working on some code, my bug count is low even if I don’t write tests, but it’s not as low as I think. The minute someone else starts pounding at the app, all sorts of bizarre niggles crop up that I just never thought to look for.

    Usually they’re all quite easy to fix – but not always.

    But maybe you’re better than me and most others at testing your own UIs. That may we

    • I've had a beta running for week or so and people have been using it. I've gotten some bug reports, but nothing major so far.

      I think part of the reason this may be an exceptional case is that to a large degree I'm rewriting existing functionality with a new UI. I'm not inventing the backend logic and the frontend code at the same time. The backend logic has been around for a few years in the case of most features, and I have a pretty darn good idea of what it should do. The backend code is well tested (from real use) so it's not terribly buggy.

      The point of my journal entry wasn't that I was exceptional (though I am ;), but rather that this particular project may be exceptional. I don't know if I'm better at testing _all_ of my UIs, but maybe for this one I am, since the entire project is the product of my imagination. I'm not trying to interpret anyone else's specs, which certainly makes development simpler.