More work babble
Dec. 18th, 2003 12:04 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ravencallscrowsWell, as of last night, my developers assured me all the work for my release, scheduled for Friday, would be checked in and good to go when i got in this morning.
Well, that almost happened. Sorta. The one bit I was waiting on yesterday was indeed complete, but in order to test it fully, something else needed to change as well. The developer who's working on that says that it can maybe happen by the end of the day today.
So, i'm sitting, waiting on my PM to make a decision again. I'm good to go. I don't mind not testing the functionality on the stuff that's done but contingent upon the remaining bits. Then again, the part that's hung up is the part that was the whole reason we're doing this release.
The testing liability for the rest of the fixes checked in is pretty minimal- two of them are just minor adjustments to HTML pages, and should take all of a minute apiece to navigate to and verify. A third is a negative case which should have been fixed by some database work- it's to verify that a certain class of user shouldn't be able to see certain content, but since that user class was just added, most of the content hadn't been enabled for it, but a script has since run to turn it all on. This test would probably involve creating a new item and enabling it for views except the new one, then verifying that it wasn't shown. Figure this might take all of a half-hour. There's another fix closely associated with it, and testing one covers the other. The final fix is another negative case, and just requres creating two classes of viewers with the same e-mail address. The rights assignment is probably going to be all messed up in this case, but as long as the site doesn't crash as a result of it, this fix is considered good (the rights for each viewer set is addressed separately). Figure this is, all together, maybe two hours worth of work.
So, i'm giving myself until noon tomorrow. With the vagaries of the build process, that still may not happen.
Well, that almost happened. Sorta. The one bit I was waiting on yesterday was indeed complete, but in order to test it fully, something else needed to change as well. The developer who's working on that says that it can maybe happen by the end of the day today.
So, i'm sitting, waiting on my PM to make a decision again. I'm good to go. I don't mind not testing the functionality on the stuff that's done but contingent upon the remaining bits. Then again, the part that's hung up is the part that was the whole reason we're doing this release.
The testing liability for the rest of the fixes checked in is pretty minimal- two of them are just minor adjustments to HTML pages, and should take all of a minute apiece to navigate to and verify. A third is a negative case which should have been fixed by some database work- it's to verify that a certain class of user shouldn't be able to see certain content, but since that user class was just added, most of the content hadn't been enabled for it, but a script has since run to turn it all on. This test would probably involve creating a new item and enabling it for views except the new one, then verifying that it wasn't shown. Figure this might take all of a half-hour. There's another fix closely associated with it, and testing one covers the other. The final fix is another negative case, and just requres creating two classes of viewers with the same e-mail address. The rights assignment is probably going to be all messed up in this case, but as long as the site doesn't crash as a result of it, this fix is considered good (the rights for each viewer set is addressed separately). Figure this is, all together, maybe two hours worth of work.
So, i'm giving myself until noon tomorrow. With the vagaries of the build process, that still may not happen.
