Meeting 7-22-2010

Agenda:

Introduction of QA team members
Review of QA branch and how to test and enter JIRAs
Review of how participants use EvalSys, particular areas of interest for QA
First stab at Test Plans

Etherpad link: http://titanpad.com/ketxs5k8qH

Evaluation System QA Call - July 22, 2010

Attendees: John Ansorge (OHSU), Nicola (Longsight), Adam Marshall (Oxford), Norhal & Matt (UMich), Ellen (UMaryland), Joe (Rutgers)

http://confluence.sakaiproject.org/display/EVALSYS/1.3.x+QA+Effort

How do you use the tool?

Oxford - Pilot for about a year. Going into 'beta'. Three uses: 1) Data gathering, surveys, get info about students 2) General Public survey 3) Course evaluation

No hierarchy, can't get it to work

Not a top-down approach to evals. There are templates though. 80-90 templates. Happy with it.

Most bugs are in Sakai JIRA, some in Oxford JIRA, have to see which ones have been fixed, etc.

UMaryland - Used to do course evals de-centralized. Back in 2004-2005, University decided to have one system across campus. One eval for all courses at the end of each term. Deployed via hierarchy - University has 15 items, some colleges have their own items, plan is to make dept-level and instructor-level questions. One huge template.

Using since 2007, planning next steps now.
Use GroupProvider to pull from SIS.

Populates the hierarchy via db scripts, not via the gui or the hierarchy provider

UMich - similiar to UMaryland.
Business req: evals need to be able to be imported. XML files. templates, items, everything. Only used for administering the evals.

Michigan additions also include email and notification options that we'd like to get back into trunk: http://jira.sakaiproject.org/browse/EVALSYS/component/10820

Perhaps using some kind of home-grown system to generate the XML? Peoplesoft is the interface?

Rutgers - transitioning to online system. University-wide, in all courses, voluntary. Generate XML files and upload into the system.
Don't know who the instructors are. Use groupProvider to send out an email to all students in courses specified. Instructors don't get a notification.

OHSU - Planning update soon. UCT feature: which faculty you'd like to evaluate. Just a few templates (one for each dept), deploy the evals manually for the depts. As we grow, how to deploy large scale.

Review of Confluence Space and JIRA

Make sure you have a JIRA/Confluence account.
Feel free to create lots of issues!
Make sure to tag your issues as 'Affects Version'=='1.3.0-RC' so that it will show up on this page: http://confluence.sakaiproject.org/display/EVALSYS/1.3.x+QA+Effort

Creating Test Plans

Breakdown the workflow tasks?

  • Create template, deploy evaluation, template editing, etc

It's a big tool, managing the template is a big job.
Coarse-grain functionalty works, more detailed edge-cases is were wacky stuff hapens.
Will Test Plans give us false confidence?

Template ordering can sometimes get messed with large templates, many items, grouping.

'create template' test plan - ordering item, grouping items.

How to create items? Could be tedious to create all those items. Copy and paste items could make it easier for testers.

John A and Ellen to take first stab at 'create template' test plan. By mid-August.
Confluence?

Test Server

Oxford has pretty recent trunk on production. Very close to release candidate. Can give anyone accounts who wants to test. Email Adam Marshall.

Can we get this RC on a official QA server? Someone did volunteer on list. Nicola to check. UMich has a nightly server. (Not building nightly yet, hopefully in the next few weeks)

UCT has a QA server, but perhaps they want to run trunk. Nicola will follow up on this.

Final thoughts:

At somepoint we need a call for fixes on the list. People probably have local fixes, we need them to contribute.