[WG: Sakai QA] [Building Sakai] QA for trunk/Morpheus

Neal Caidin neal.caidin at apereo.org
Wed Mar 4 05:42:51 PST 2015


+1

Sure, turning on the tools on is a good idea. We also need to document
specifically what configurations are tested. We do not have regression
tests that cover all the permutations.

-- Neal


On Tue, Mar 3, 2015 at 2:25 AM, Adrian Fish <adrian.r.fish at gmail.com> wrote:

> It's less properties and more tools really. We should start to build a
> document of any problematic tools now, so work to get those tools shipshape
> can get delegated out and started asap. One of the Morpheus emails
> mentioned that some tools were problematic, but wasn't specific, that's all.
>
> Adrian.
>
>
> On Tuesday, 3 March 2015, Matthew Jones <matthew at longsight.com> wrote:
>
>> What additional properties do you want? We can turn them on the
>> nightlies. I don't know what optional stuff is still currently off.  I
>> think if there is some optional stuff off which should be considered on by
>> default in 11 we should be looking to turn it on at this point like we did
>> before 10.
>>
>>
>>
>> On Mon, Mar 2, 2015 at 5:52 PM, Adrian Fish <adrian.r.fish at gmail.com>
>> wrote:
>>
>>> Would it be possible for someone to test a build with all the optional
>>> stuff on and just smoke test as many tools as possible for viability in the
>>> new skin? I'm just talking about a quick visual test to determine whether
>>> more investigation is necessary. A central Jira ticket with sub tasks
>>> resulting from such an assessment would be excellent. I know portal chat
>>> needs some TLC, for a start :)
>>>
>>> Cheers,
>>> Adrian.
>>>
>>>
>>> On Monday, 2 March 2015, Neal Caidin <neal.caidin at apereo.org> wrote:
>>>
>>>> [sakai-dev, sakai-qa, sakai-pmc]
>>>>
>>>> Hi All,
>>>>
>>>> Now that we have Morpheus (Responsive Design) turned on in trunk,
>>>> perhaps the focus should be :
>>>>
>>>> 1) On fixing some of the bugs that will hold up (i.e. make more
>>>> difficult and less complete) QA like:
>>>>
>>>> https://jira.sakaiproject.org/browse/SAK-28978
>>>> https://jira.sakaiproject.org/browse/SAK-28946
>>>>
>>>> (those two are apparently related)
>>>>
>>>> 2) coming up with at least a high level Test Plan.  I think I need some
>>>> input or general direction from Developers on this.
>>>>
>>>> 3) Scheduling an intensive Test Fest for several days which involves
>>>> developers and QA testers, and having some open communication channel
>>>> between them (Big Blue Button? , some sort of internet chat tool? , Google
>>>> hangouts?  ... etc).
>>>>
>>>> I am off to a conference the week of March 16, so for me, the timing
>>>> would seem to be to do this next week, the week of March 9.
>>>>
>>>> What do you think?
>>>>
>>>> Thanks!
>>>> Neal Caidin
>>>> Sakai Community Coordinator
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> sakai-pmc mailing list
>>> sakai-pmc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20150304/7c6f379d/attachment.html 


More information about the sakai-qa mailing list