[WG: Sakai QA] 2.9 Feature list

[Sam Ottenhoff]

Beth,

Do you think we should simply modify the QA servers with the property?  Or
should we modify trunk and set this as a blocker target for 2.9.0 release?

--Sam

On Wed, Nov 2, 2011 at 9:20 PM, Beth Kirschner <bkirschn at umich.edu> wrote:

> There are still quite a few tools that have open JIRAs filed against IE9
> -- that being said, I can see the value in having one QA server setup _not_
> to emulate IE8 (https://jira.sakaiproject.org/browse/KNL-697). I believe
> the setting sakai.properties setting would be:  "sakai.X-UA-Compatible=".
> Thoughts?
>
> - Beth
>
> On Nov 2, 2011, at 4:05 PM, Charles Hedrick wrote:
>
> > I would prefer to see testing down without this. It was added because IE
> 9 was released at a time we couldn't easily address it. This is the time to
> do so. If we stick to current and one back, in 2.10 we won't even support
> IE 8. So I think we need to support IE 9 natively in 2.9.
> >
> > On Nov 1, 2011, at 4:17 PM, Sam Ottenhoff wrote:
> >
> >> IE compatability is forced via the setting of an HTTP header by
> default.  So yes, compat mode is still enabled for 2.9 testing unless the
> QA admin specifically disables it.
> >>
> >> On Mon, Oct 31, 2011 at 8:44 PM, May, Megan Marie <mmmay at indiana.edu>
> wrote:
> >> Is compatibility mode for IE still enabled for 2.9 testing?
> >>
> >>
> >>
> >> Megan
> >>
> >>
> >>
> >> From: sakai-qa-bounces at collab.sakaiproject.org [mailto:
> sakai-qa-bounces at collab.sakaiproject.org] On Behalf Of Matthew Jones
> >> Sent: Thursday, October 27, 2011 4:04 PM
> >>
> >>
> >> To: Sam Ottenhoff
> >> Cc: Rob Egan; Sakai QA
> >> Subject: Re: [WG: Sakai QA] 2.9 Feature list
> >>
> >>
> >>
> >> Also, regarding browsers that are tested on since IE7 was mentioned,
> >>
> >>
> >>
> >> The question comes up a lot on the lists and I think the QA team should
> make a decision and stick to only testing on a smaller set of the most
> popular modern browsers. This would mean that no extensive testing be done
> on anything like Safari 3 (Tiger), IE7 or Firefox 3.5. It would be good to
> know about any problems so they can be worked around or features disabled
> but I don't think we'd be putting much time into fixing issues for older
> browsers and it doesn't seem to help the community as much testing on less
> popular browsers.
> >>
> >>
> >>
> >> At Michigan, the 3 most popular browsers as of 10/2011 are:
> >>
> >> Chrome v14 (~30% traffic)
> >>
> >> Safari 5 (~25% traffic)
> >>
> >> IE 8/9 (~20%)
> >>
> >>
> >>
> >> Firefox 6 & 7 (~15% traffic) and Firefox 3.6/4.0 (~10% traffic) are the
> 2 remaining.
> >>
> >>
> >>
> >> Thanks!
> >>
> >>
> >>
> >> On Thu, Oct 27, 2011 at 3:47 PM, Sam Ottenhoff <ottenhoff at longsight.com>
> wrote:
> >>
> >> Hi Rob,
> >>
> >>
> >>
> >> I am attaching an export from JIRA containing relevant 2.9 permissions.
>  Here is a personal list of items that I think need testing emphasis:
> >>
> >>
> >>
> >> 1) Gradebook
> >>
> >>    a) Drop highest / drop lowest
> >>
> >>    b) Internationalization: set your language to ES in a course and
> update grades; go to Assignments and update a grad to "7,3" and see if it
> comes into gradebook
> >>
> >>    c) Generate PDF from gradebook
> >>
> >>    d) Test with students with really long names
> >>
> >>
> >>
> >> 2) Internationalization
> >>
> >>    a) Set your course language to ES (new feature in Site Info)
> >>
> >>    b) Look for dates and number entry that may not be internationalized
> >>
> >>       i) Enter your numbers like they do in ES, "7,3" instead of 7.3
> >>
> >>
> >>
> >> 3) neoportal and new chat
> >>
> >>     a) User testing for now
> >>
> >>     b) Known issues with IE7 and below.  What about other browsers?
> >>
> >>
> >>
> >> 4) New trunk tools
> >>
> >>     a) Mailsender
> >>
> >>     b) Lesson Builder
> >>
> >>
> >>
> >> 5) Announcements
> >>
> >>    a) Several regressions in 2.8
> >>
> >>    b) Test delayed announcement email delivery
> >>
> >>    c) Test reordering of announcements
> >>
> >>
> >>
> >> 6) Tests & Quizzes
> >>
> >>    a) Several regressions in 2.8 related to the new Quick Publish
> (bypass Settings)
> >>
> >>        i) Bypass settings and publish, then duplicate that assessment
> >>
> >>    b) Respondus Lockdown Browser is now an option
> >>
> >>        i) We may need someone to reach out to Respondus to see if we
> can get a license to test this
> >>
> >>    c) Testing Respondus IMS-QTI imports
> >>
> >>
> >>
> >>  7) Site Manage
> >>
> >>     a) Import from Site and Duplicate Site rarely receive testing
> >>
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> sakai-qa mailing list
> >> sakai-qa at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
> >>
> >> TO UNSUBSCRIBE: send email to
> sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> sakai-qa mailing list
> >> sakai-qa at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
> >>
> >> TO UNSUBSCRIBE: send email to
> sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >
> > _______________________________________________
> > sakai-qa mailing list
> > sakai-qa at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
> >
> > TO UNSUBSCRIBE: send email to
> sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.orgwith a subject of "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20111103/e2adeee4/attachment.html