Update on 1.2 testing
obara.justin at gmail.com
Wed Apr 14 14:36:20 UTC 2010
As for retesting.
You can view the channel logs from today to see a conversation we had about testing.
In short, we are going to just rerun the unit tests for keyboard-a11y and the affected components. Also rerun just the keyboard a11y tasks for those components in a single demo of each version of the component (e.g. grid reorderer, simple text inline edit, rich text inline edit, and etc.) in each configuration. Michelle also had the suggestion of mixing up which demo we run in different configurations. For example in winxp ie 7 we would do the simple text inline edit example from the demo portal, in mac os 10.6 ff 3.6 we would run the sakai announcements integration example.
Hopefully we will be able to get all that done fairly soon.
On 2010-04-14, at 10:30 AM, Michelle D'Souza wrote:
> On 13-Apr-10, at 11:40 PM, Colin Clark wrote:
>> Would it not be sufficient to write a unit test that shows the bug without the patch and passes once the patch had been applied?
> Hi Colin,
> Interestingly it was actually an existing test that caught the bug. Which is good but points to a hole in our infrastructure. We depend on people to run the automated tests instead of the tests being run upon commit or during the nightly build. We've known that this is an issue for a long time but never quite found the time to rectify it. So this time around *4* of us - the bug fixer, the two independent reviewers (I'm one of them) and the QA tester didn't run the unit tests. And all of us like unit tests and generally run them - but we were crunched and rushed so it slipped through. Luckily that final testing did catch the slip and the test is passing again with the patch Justin created.
> Michelle D'Souza
> Software Developer, Fluid Project
> Adaptive Technology Resource Centre
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fluid-work