It is well known that Microsoft releases a patches on the second Tuesday of every month. Regression testing every product in RedDot's arsenal every month is not a sensible thing to attempt, even with automated test tools.
As Frederic was saying, they most likely test when dependancy components are affected, but to be honest I've never seen an MS patch release bring down either CMS or Live Server. Not sure if anyone else has... HTH. Regards, Richard Hauer ==================== 5 Limes Pty Limited www.5Limes.com.au On Sep 6, 6:42 pm, Frederic Hemberger <[EMAIL PROTECTED]> wrote: > Take every CMS build still used by major customers (ranges approx. > from 7.1.x to 7.5.1.x), and check it against every single microsoft > patch, hotfix, hotfix for nonworking hotfixes and service packs (and > there are some each month on "microsoft patch day") and test it > against Windows 2000, Windows Server 2003, Windows 2008. To make sure > everything works fine, test it on MySQL, MSSQL2003, MSSQL2005, Oracle > (10g to 10i) and the other major DB systems supported by RedDot. > Uhh... I guess they do not. ;) > > I think they check it, if the patch canges the behavior of core > components, which RedDot depends on (COM+, DCOM, IIS, .NET, Network > components, etc). And personally, I don't know how such a test could > look like (Check navigation manager? Publish demo project? Run > automated network tests?). > *** > > Take every CMS build still used by major customers (ranges approx. > from 7.1.x to 7.5.1.x), and check it against every single microsoft > patch, hotfix, hotfix for nonworking hotfixes and service packs (and > there are some each month on "microsoft patch day") and test it > against Windows 2000, Windows Server 2003, Windows 2008. To make sure > everything works fine, test it on MySQL, MSSQL2003, MSSQL2005, Oracle > (10g to 10i) and the other major DB systems supported by RedDot. > Uhh... I guess they do not. ;) > > I think they check it, if the patch canges the behavior of core > components, which RedDot depends on (COM+, DCOM, IIS, .NET, Network > components, etc). And personally, I don't know how such a test could > look like (Check navigation manager? Publish demo project? Run > automated network tests?). > > *** > > Take every CMS build still used by major customers (ranges approx. > from 7.1.x to 7.5.1.x), and check it against every single microsoft > patch, hotfix, hotfix for nonworking hotfixes and service packs (and > there are some each month on "microsoft patch day") and test it > against Windows 2000, Windows Server 2003, Windows 2008. To make sure > everything works fine, test it on MySQL, MSSQL2003, MSSQL2005, Oracle > (10g to 10i) and the other major DB systems supported by RedDot. > Uhh... I guess they do not. ;) > > I think they check it, if the patch canges the behavior of core > components, which RedDot depends on (COM+, DCOM, IIS, .NET, Network > components, etc). And personally, I don't know how such a test could > look like (Check navigation manager? Publish demo project? Run > automated network tests?). > > *** > > SCNR. ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
