The other tester working with me and I finished all integration & system testing today @ 4:00 PM. Whoo-hoo! I had been getting nervous that I would need to work until 8:00 PM to get all of the tests finished. Thankfully, several coding changes put into pre-prod last night after 10:00 PM worked, meaning that I was able to take several test cases out of Failed and moved them into Passed. Working on the testing side of a project was different, considering that I usually spend most of my time on requirements gathering, design and development. While I know that paying for testing is expensive, I can definitely say that if customers decided to include testing in their projects, they would be more confident that the application they're paying for works as they expect before they move it into production.

(0)

By my estimates, I've completed 85 test cases so far. This is interesting as I only wrote 88 total sub cases. What's happened is that several test cases the other tester working with me is responsible for have encountered repeated failures (read: coding bugs). So while she tests and retests her test cases with each fix, I've worked at keeping us on track to finish testing by next Wednesday. The testing project manager says that we're only one test behind schedule, so I think I've been successful.

(0)

The effort I started way back on 8/10/2004 has finally come to an end. I just completed writing test cases for all 57 test case identifiers assigned to me. These 57 test case identifiers include 88 sub-cases. Whew! That sure was an interesting month in my professional career, to say the least. I'll print out all of the ones I created since the review on 8/25/04 tomorrow and give them a once-over before calling this part of the testing project done.

I have to wonder, though, how much of a market there is for test case developers or writers. From my experience, very few of the bigger I've worked for have ever mention them. Too bad I wasn't involved with the development team. They were using WebSphere to execute test cases in JUnit format. Sounded cool...

(0)

The testing team I'm working with reviewed the 28 test cases I'd written as of 8/20/04. There were 44 sub-cases in all. The review itself went very well. Most of the changes requested were formatting/wording changes that I'd need to make to each test case/sub-case. I'll need to make all of the changes over the next several days. No rest for the wicked, though, as I need to write another three test cases today.

(6)

I guess I'll get to put my experience with writing test cases to good use after all. I need to begin writing test cases for the 56 test case identifiers assigned to me. The test case development schedule has me writing three test cases a day, and I feel comfortable that I can keep up that pace. After all, what is writing test cases when compared to writing articles for the Lotus or WebSphere Advisor?

(0)