Originally posted by Junilu Lacar:
On Ilja's suggestion, I took a look at the material in the WELC Yahoo! group. It seems very relevant to my questions (I even found a couple of my questions in there!).
Thanks, Ilja!
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Junilu Lacar:
Well, maybe I do have a question. But first, to summarize:
The problem: We're getting bugs and it's hard to tell if the TaskProcessor and/or the classes it services is/are doing anything wrong.
The task: To retrofit the CUT with a unit(?) test to make sure it works correctly.
Ilja, you suggested system/acceptance tests. That will definitely help although I haven't really used FitNesse before.
So these tests would simulate entering data as a user and then verify what it expects to find in the database, right?
In some cases, the "user" is actually a background process
and it's still not certain if this background process is correctly doing everything it should.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Junilu Lacar:
Code ownership is individualized in this project.
...
Another problem I have seen with the current code is that the CUT is taking on responsibities that seem to be more appropriate for its client classes. Conversely, client classes to the CUT take on responsibilities that seem more appropriate for the CUT.
We know there are bugs because we are getting unexpected and inconsistent data (e.g. two rows created in the DB when only one should have been). What makes things worse is that the bugs are intermittent. Because there are many different conditions involved in the process (which, of course, can be threaded :rolleyes it's hard to tell which particular combination of conditions cause the errors.
My half of the "solution" to the problem is to have the CUT check for requests that would result in these data inconsistencies and ignore them.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |