Sunday, July 22, 2007

Tedious Defect

Monday (16 July 2007)

This is a hard war. I am working on a defect which is having calculation error in report. At first I suspect there is a double entry error. This could be a new challenge on me as I never work this before. I am spending the whole day to look for the real problem in the source code, resource file and the work flow. Unfortunately all the effort are wasted in this day because nothing can be found.

Tuesday (17 July 2007)

There was no error in double entry because the calculation was a real time process during the "report making" process.

Today I dive into the code to see how double entry was created, how the journal entry is made and how the recap function work. Actually the error is not here. If this is an error, there must be an error in double entry. Since double entry is working fine. There must something wrong in other place. I stop my analysis work on double entry and request help from my senior. After the discussion, I suspect there must be some work need to be done in resource file.

Wednesday (18 July 2007)

I have found something in the resource file. This is very tricky. Every ID defines in resource file represent fields in the data file. This field may have some attribute apply on it to indicate how the field is 'work'. A few changes were made and it works finally. But I need to test other part of the report to ensure my work is complete.

Thursday (19 July 2007)

I am doing the wrong thing. All my works are gone. My effort was wasted. I am not yet clearly understand the real problem. I am not yet clearly understood the work flow. I though I have complete my work. But the fixed I have done will be reactivated in someday. I have no clue how this thing should be fix.

Friday (20 July 2007)

YES!! I have completed the fix. The report is showing the correct value in both invoice and purchase. I couldn't sleep well on yesterday night just because of thinking a 'real' solution for this problem. Now it is working fine here.

Anyhow I found an error during the crash test. I am almost complete my work. At this moment I need to calm down to check every test detail. It should be done in one day effort.

No comments: