Index

- Maintenance team, recreating the bug - QA team filtering bugs for maintenance team - Automation testing - QA-test/functionality testing (scenario based, exploratory.. etc) EXPLORATORY TESTING ======================= Test charters - Templates for test co

Find out what the rule is for testing contrib tools on the QA server. (Rob) Find out schedule for community testing (Rob) 2.9 will begin testing in September 2.7.2 and 2.8.1 will be ready for testing by the end of July Find out about documenting while tes

A space for Sakai's volunteer QA group to coordinate activites.

name: Account Tool purpose: Test Procedure to verify that users' Account details can be edited expected result: User should be able to view account details and modify them test data: dependencies: Sites and Users created setup: start at: My Workspace,

Uses auto-configuration available as of Sakai 21 Video - Adding an LTI Tool https://drive.google.com/file/d/18kca66wROYar6GUDjI7hcGpd-H-K85Lv/view?usp=drive_link Tsugi Admin Setup Log into https://sakai.tsugicloud.org/tsugi/admin/ https://sakai.tsugicloud

Tsugi Admin Setup Log into https://sakai.tsugicloud.org/tsugi/admin/ https://sakai.tsugicloud.org/tsugi/admin/ Click Manage Access Keys Click Tenant Keys Click Insert Tenant Add a key title Enter a key in LTI 1.1: OAuth Consumer Key - This key needs to be

This page is meant as a means to collect together resources to aid testing of admin-only tools such as Realms, Sites, Users, and so on. Realms Role permissions for Realms TC Matrix Site Archive Batch migration XML for Site Archive TC Matrix Realms The tes

name: Announcements purpose: Verify that the Announcements tool is functional expected result: User should be able to add, delete and manage announcements. test data: resources.doc, music.mp3, resources.txt dependencies: Sites and Users created setup: s

Overview The Sakai 12 QA Hub is the home page for the Sakai 12 QA effort. Here you’ll find useful information for getting involved with testing and becoming part of the Sakai QA community. We have four different QA testing paths from which to choose. If y

Welcome to the CLE QA Work Group space. This space is dedicated to coordinating functional testing for the Sakai CLE Latest information on QA testing activities Verify resolved issues https://jira.sakaiproject.org/issues/?filter=13684 Update Regression Te

Recipe Jlint (https://sourceforge.net/projects/jlint/ https://sourceforge.net/projects/jlint/)is yet another static code review tool. After installation via the download site or under a Debian based linux: sudo apt-get install jlint I created a script

View Source name: Assignments tool purpose: Verify that the Assignments tool is functional expected result: User should be able to create, edit, post and delete assignments. test data: resources.doc, resources.mp3 dependencies: Course Site created with no

name: Assignment; Submit purpose: Verify that the assignments created by the Assignment tool can be submitted by students expected result: User should be able to submit assignments and add attachments to the assignments test data: resources.doc dependenci

View Source name: Assignment Tool - Grade purpose: Test Procedure to verify that an instructor can view and grade a student-submitted assignment expected result: User should be able to view and grade a student-submitted assignment and the student should b

Introduction A method for code reviewing based on ISO 9126-1 standard. Static code review checks off line for bug patterns. In theory if used appropriately the methodology will push up the average code quality of the target source. See: Presentation http:

Creating users for testing A JMeter script for creating users in Sakai. Works through the 'New Account' tool to create any number of accounts based on a text file with user data. Has a build in delay to prevent server stress. createusers.zip

View Source name: Blogger purpose: Verify that the Blogger tool is functional. expected result: User should be able to create, view, edit and delete blog. test data: resources.jpg, resources.doc, URL: http://www.rsmart.com http://www.rsmart.com dependenci

Sakai 2.9 is designed to work with modern browsers. You should be safe with the latest versions of Firefox (Mozilla), Safari (Apple), Chrome (Google), and with IE 10, IE 9 (Microsoft Internet Explorer aka IE) and IE 8. Sakai CLE does not work with IE 7 an

Here is a sample script which shows how to correctly verify that your page has finished loading before continuing. The inline comments describe why the verifyText is useful for synchronisaction. openURL|/portal/xlogin enterText|eid|seleniumInstructor ent

name: Schedule Tool in My Workspace purpose: Verify that Schedule tool is accessible and functional expected result: User should be able to launch Schedule tool and see events listed on their calendar, change the calendar view (days, week, month) and add/

name: Calendar Tool Import purpose: Verify that Calendar tool import is functional expected result: User should be able to import a generic calendar file successfully and see the events listed on their calendar. test data: master_calendar_import_file.txt

name: Chat Tool purpose: Test Procedure to verify that two or more users can carry on a chat expected result: User should be able to see what users are in room, create, edit, delete rooms, create, delete, read messages test dasmoney: dependencies: SiteS

Test Framework is a project with a simple goal. Provide the community with an easy to use, deterministic load test framework that encourages regular CLE performance testing and early discovery of problem areas in the code. This framework will later suppor

Prototype - Code Coverage Introduction Code coverage allows you to see with X ray precision which parts of the code are is not being used during a given run. The technique is helpful for answering a number of questions associated with the primary question

Introduction A prototype Sakai tool was built to highlight the value of Automatic code reviews. The meaning of the generated reports and the tool itself and surrounding content are described. The advantage of this approach are numerous: reports may be gen

Under Construction Installing Hudson Installing on Ubuntu http://hudson-ci.org/debian/ Hudson Howto's Jmeter Plugin

Introduction Test framework allows you to perform tests through Jenkis. Show this screencast to see Jenkis and Test Framework working together. Configuration The next lines describe one way to run test framework with jenkins. You need only one jobs to ach

name: Announcements purpose: Verify that the Announcements tool is functional expected result: User should be able to add, delete and manage announcements. test data: resources.doc, music.mp3, resources.txt dependencies: Sites and Users created setup: s

Introduction Test framework use JMeter http://jakarta.apache.org/jmeter/ to perform load tests. Core package provides different tests made for different versions of Sakai. You could create your own package see custom test in 10 minutes. Run Tests In order

Your idea's and energy are most welcome. In my role as interim QA director I have two objectives: The first is to support the community in the on going central QA cycle. The second is to strengthen the already proven processes and find support from the co

Introduction Now is really easy to create your own test. It taks only 10 minutes !! You just follow this instructions or watch the screencast. The main steps are: svn co https://source.sakaiproject.org/contrib/qa/tags/testcases-YOUR-FAVOURITE-VERSION myte

Introduction The report generator needs a database. At present a Mysql database is used. Create a database Sakai and add the tables mentioned next. In the Scripts directory sits dbh.conf that points here. If you want to change the database name then feel

Deep Regression Scripts DeepRegression2.png # Column Name Description 1 Step The scripts have sections and the steps are numbered below each section 2 Role Role the tester should be in when completing the step 3 Action Action the tester needs to take 4 Ex

Graphing dependencies in Sakai code home:http://el4j.sourceforge.net/index.html http://el4j.sourceforge.net/index.html It is possible with the command mvn depgraph:depgraph at the top level of the source code for a Sakai tag to produce a series of image

Introduction Here under is a break down of the collaborations between players for the qa-helper tool to function correctly. See also: Instrumentation from the command line Collaboration Diagram Players (a) User that requests actions such as generation of

Sakai 10.1 Pre-release is to verify issues on trunk that should be included in Sakai 10.1 Sakai 10.1 - Pre-release Target for 10.1-rc01 (first release candidate) is July 25, 2014. Issues must please be verified by a day or two before to allow time to merg

Priority 1 - Focus on testing blocker issues that are resolved but need to be merged into 2.9. This will ensure that fixed issues are in 2.9 prior to regression testing Priority 2 - Regression testing - currently for Sakai CLE 2.9.x , targeting a 2.9.2 re

Related to the Perl wrapper for the Internationalization dashboard. Copyright (c) 2006 Universiteit van Amsterdam Licensed under the Educational Community License version 1.0 This Original Work, including software, source code, documents, or other related

View Source name: Email Archive Tool purpose: Test Procedure to verify that the Email Archive tool functions as specified. expected result: User should be able to create aliases, modify options, successfully send and receive mail test data: resources.doc

View Source name: Evaluations Tool purpose: Test Procedure to verify that the Evaluations tool functions properly expected result: User should be able to create evaluation forms and sync them to Wizards test data: dependencies: SiteSetup.htm has been ru

Overview Instructions Hi, welcome to EZ Maven. This is for testers who are "Mavens" (i.e. folks capable of tool testing) but have limited time to participate in testing. EZ Maven is the same as QA Maven, just on some of the tools that should take less ti

Overview Welcome How are you ? Thank you for helping test Sakai 12.0. By verifying as many fixed problems as possible, that they are really fixed, and by finding as many bugs as possible, you are improving the Sakai software for millions of students, many

List of frequently asked questions regarding QA. Should get you started if you are new to QA. Welcome to the Sakai QA effort! This document provides you with basic information regarding Sakai QA. FAQ What is QA and why is it so important? What is regressi

name: Feedback Tool purpose: Test Procedure to verify that users can create feedback and allow other users to view that feedback expected result: User should be able to import .csv file of feedback, allow other users to view feedback, delete feedback if n

Automated Code Review Feedback Introduction I promise to try and improve the reporting tool based on your feedback. A.M.B Index Removing false positives Improving the automated process Ignore classes with import junit Double check validity of serializatio

FindBugs Annotations Annotations work out the box with Findbugs as long as two dependencies are added in the compile scope of the pom.xml of your project. Download the latest version of Findbugs http://findbugs.sourceforge.net/downloads.html http://findbu

View Source name: Forms tool purpose: Test Procedure to verify that the Forms tool functions expected result: User should be able to add, import, export, revise, delete, and publish forms test data: schema.xsd dependencies: SiteSetup.htm has been run setu

View Source name: Forms Tool purpose: Test Procedure to verify that the Forms tools behaves as expected expected result: User should be able to Add, Revise, Export, Publish, Publish Global, Import, and Delete Forms test data: schema.xsd, ImportForm.zip de

View Source name: Forum Tool purpose: Test Procedure to verify that registered users can use the forum tool functionally expected result: User should be able to create a forum, create a topic, create, edit, delete message and reply to other messages test

Overview This section serves to provide general testing tips for web applications. It provides basic tests for different elements in web applications to help users think about different ways to test. It is not meant to provide comprehensive documentation

View Source name: Glossary Tool purpose: Test Procedure to verify that the Portfolio Glossary tool functions expected result: User should be able to add, revise, view, import, export, and delete glossary terms. test data: .zip file found in portfolio's re

Creating Test Scripts Sign up for a Gmail account http://gmail.com, preferably one that will only be used for test scripts (there's a limit on the free storage space available) Click on 'Drive' in the menu at the top to open your storage space Open the fo

View Source name: Gradebook purpose: Verify that the Gradebook tool is functional expected result: User should be able to add assignments, enter grades, edit gradebook and manage groups. test data: CSV file (generated by Gradebook tool) automation setup d

Recording of the Morpheus Virtual Hackathon https://youtu.be/Hx7pQ52mWrc on March 23, 2016. The QA Team has identified UI bugs in Sakai, categorized by tool. Each tool has its own parent JIRA. These parent JIRAs track all morpheus-related issues for a giv

View Source name: Help Tool purpose: Verify that the Help tool functionality works expected result: User should be able to use the Help tool and Help Icon test data: dependencies: SiteSetup.htm has been run setup: start at: AM HIS1 101 home page, Logi

If you are going to try to approach the fixing any tool (maybe you have found a bug, maybe QA team did), for now, we have two complementary ways to solve a bug and you may read it here. Further information to find bugs to Sakai can be found in this docume

These examples show how to add the Dashboard tool, but the same process is applied to any tool that is not available in a course or in a user’s Home (workspace). Add a Tool to a Course Video https://drive.google.com/file/d/15WfxiOlVEGLaH18mtyMfN4Tvt9iwZHs

Note: If you want to add your own instructor to the site created, make sure to create that user on the server before taking these steps. Creating a New Site Log in as an admin Click on Worksite Setup in the navigation Click the Create New Site tab El0y2pC

The Job Scheduler creates 5 sites at a time, populated with users and Gradebook items. Note: If you want to add your own users to the sites created, make sure to create those users on the server before taking these steps. Accessing the Job Scheduler Log i

Sometimes Jiras need to be tested in a different language in which the tester is not fluent. Browser translators, (Google, for example), should not be used. You will need two browsers and two different instructors for this test. Create two sites, one for

Uploading the Image Click on the tool you want to use for creating something that uses the rich text editor. Not all of the rich text editor options are exposed initially, so you will need to click the sideways triangle to expose more options: GrrMbH00Ze

This article shows you how to make requests to sakai via the command line. This is useful to making API calls to insert data into Sakai The first step is to get a session cookie which will be stored in a file called ‘cookie.txt’. This appears to be known

Most tools in Sakai can send an email, (Announcements, Assignments, Tests & Quizzes, etc.). Mailinator https://www.mailinator.com/ allows you to make up any name and use @mailinator.com to be added to the username and that address can then receive emails.

Keep in mind that once something has been set to "resolved", it will not be on the server until after the restart. The server list has the restart times at the bottom: http://nightly2.sakaiproject.org/ http://nightly2.sakaiproject.org/ Most Jiras are veri

under Construction Introduction This recipe worked on Hudson/Ubuntu and is based on http://wiki.hudson-ci.org/display/HUDSON/JMeter Plugin http://wiki.hudson-ci.org/display/HUDSON/JMeter+Plugin Potential Usages Excercise Rest services Generic Stress test

Background Francois Pierre from Toyota Europe has improved the binding Ant script and updated the features to include: Java NCSS reports Automated Merging of reports HTMLization of all the targeted source code. Good work Francois! The code http://bugs.sak

{index}{index}

Installation - Static code review Database table structure Running the code nightly.sh generates a report nightly. Modify the settings at the top of the script. Per_tag.sh includes the internationalization. You may need to update Perl for the correct data

Within about ten lines of command line coding you may be enable to perform live code coverage reporting. Introduction Emma is an open source code coverage tool. In our case, Emma enables code coverage by instrumenting the target code. The instrumentation

Introduction It is my hope to motivate the use of code coverage for command line debugging live via an example war training war file that fails in a reproducible manner. See also: EMMA homepage http://emma.sourceforge.net/ Code Coverage via a Sakai tool A

Internationalization Dashboard Overview The Internationalization dashboard is based on two components: First is a Java tool created by the Leidse Onderwijsinstellingen. The tool http://bugs.sakaiproject.org/confluence/display/I10NSTATS/Home scans through

If you download and install Java 1.6 then the updated version of Jconsole can be run against Sakai on a Java 1.5 platform. The newest version can detect thread deadlocking and has a pluggable structure. For example to run Jconsole with the a pseudo top co

A Jira may show as resolved on trunk or merged to one of the other servers (versions), yet when testing, the problem still seems to exist. Fixes will show up on the server after a restart and this is where Jenkins comes into the picture. Jenkins will list

name: Discussion Forums Tool purpose: Test Procedure to verify that students can create, edit, delete topics, posts, and private messages, can alter their preferences, and that instructors can manage categories, forums, and options for the entire system e

name: Discussion Forums Tool purpose: Test Procedure to verify that students can create, edit, delete topics, posts, and private messages, can alter their preferences, and that instructors can manage categories, forums, and options for the entire system e

The Jira Triage working group meets weekly to review newly created Jira tickets for Sakai. Newly created Jira tickets are in an "awaiting review" status. The Jira Triage group reviews these tickets weekly to ensure that the ticket contains all required i

This page is intended for sharing resources and ideas relating to using JMeter for QA Testing From Charles Hedrick on the sakai-dev list on using JMeter jmeter is a web load tester. It looks pretty good. I set it up pretty quickly and got it to beat on sa

Open Source Tools available. Example. Download the latest source: svn co https://source.sakaiproject.org/svn/sakai/trunk https://source.sakaiproject.org/svn/sakai/trunk sakai Add at the end of the top level pom.xml there is a section for reporting, expand

Keyword Listing addText(String identifier, String text) Add text into a text field, leaving the current text intact. use: addText|identifier|text where identifier is the id, label name, or name of the text field and text is the string to be entered. captu

name: Login Tool purpose: Test Procedure to verify that registered users can login to the site expected result: User should be able to login with the proper Username and Password test data: dependencies: Valid username and password setup: start at: Sa

Experimenting with a license requirements tool RAT (version 0.6) : http://code.google.com/p/arat/ http://code.google.com/p/arat/ The tool checks source code for licensing. Java based, extendable and has a future. The tool can find files without the correc

Introduction The literal first bug is widely spread throughout the Sakai code base. This bug is mostly harmless, but causes the throwing of null pointer exceptions if a given instance is null. In other words, Sakai becomes stronger and more stable when th

Limitations Resetting of data affects all reports generated after the event. This effectively forces sequential use of the tool or I will need to add a lock around the reset button which only one user may hold at a time. Only the in the WEB-INF/classes di

Introduction JMX, Java management Extensions are thoroughly used within Tomcat. The technology allows for the live viewing of the running JVM for profiling purposes. Further, with correct writing of management beans it is possible to reconfigure Sakai on

Introduction Test framework uses JMeter http://jakarta.apache.org/jmeter/ to prepare the test environment and later to perform load tests. Generic Properties jm-serverprotocol, jm-serverhost, jm-serverport: Describe the target of the test. jm-threadcount,

View Source |name:|Mailtool| |purpose:|Test Procedure to verify that the Mailtool functions correctly.| |expected result:|User should be able to send and receive emails from site participants as well as archive those emails in the Email Archive tool.| |te

name: Membership Tool purpose: Verify that the Membership tool is functional expected result: User should be able to join sites and un-join sites test data: dependencies: DevSiteSetup.htm has been run setup: start at: My Workspace logged in as student

2011-06-30 2011-06-23

name: Lessons Tool (Melete) purpose: Verify that instructors can create and manage lessons that students are able to access expected result: User should be able to created, view, edit, delete, export, import lessons that other users should be able to acce

View Source name: Messages Tool purpose: Verify that the Messages Tool is functional expected result: User should be able to use Messages to send messages to other users test data: resources.doc automation setup dependencies: site has been setup with 2 us

Get Started: Regression Testing Regression testing is critical for ensuring that all functionality in Sakai is working as intended. We are still evolving our Test scripts to make them easier to use, and happy to work with you to evolve them in this direct

The access logs act as a historic record for testing including: Historic record of tests Standard analysis tools exist Analysis can be automated Response time - Good to find under performing parts of the code Browser type - What have we tested the JavaS

View Source name: Matrices Tool (includes some Evaluation tool work too) purpose: Test Procedure to verify that the Matrices tool is functional. expected result: User should be able to add, import, revise, view, delete, publish, and customize matrices to

name: New Account purpose: Test Procedure to verify that a visitor to the CLE Gateway can sign up for an account expected result: User should be able to create an account test data: dependencies: GTWY-01 setup: start at: Gateway page Step ID Action Ex

ACNT-01 Account tool Verify that users' Account details can be edited. User should be able to view account details and modify them. LGIN-01 Login Tool Test procedure to verify that registered users can login to the site. User should be able to login with

name: News Tool purpose: Verify that the News tool is functional expected result: User should be able to manage the News URL and RSS feed test data: dependencies: Course site has been created with at least (1) Instructor setup: start at: Course site h

downloadDirectory=/storage/tests/downloads/ fileDirectory=/storage/tests/files/ logDirectory=/storage/tests/logs/ testList=/storage/tests/scripts/siteInfo/siteInfoList.txt variablesFile=/storage/tests/variables.txt xpathFile=/storage/tests/xpaths.xml

2.4 QA Participates Name Institution Email Testing interests Megan May Indiana University Unlicensed user where help is needed Kevin Brokamp Indiana University kmbrokam@iupui.edu mailto:kmbrokam@iupui.edu JIRA Bug verification, and anywhere else help is n

Overview This page contains addtional JIRA filters for the QA Planning group. This page supplements the Sakai 11 JIRAs Page. Additional Filters Use the following filters to find current Sakai 11 JIRAs 1.) Major-priority JIRAs that need additional review

Follow the instructions for creating a Plus site: Setting up the Plus Site As the instructor, in your “main” site, add several students, (at least 3), then launch the Plus site. Verify all members from the main site are in the Plus site. Copy the site ID

View Source name: Podcasts Tool purpose: Test Procedure to verify that the Podcasts tool functions as specified expected result: User should be able to add, edit, upload, download, delete, change viewability options, add Podcasts to RSS Feed, manage Podca

View Source name: Polls Tool purpose: Test Procedure to verify that the Polls tool functions properly. User should be able to create a poll, create possible answers, allow others to access the poll, and view the results/statistics. expected result: User s

name: Polls Tool purpose: Test Procedure to verify that the Polls tool functions properly expected result: User should be able to create a poll, create possible answers, allow others to access the poll, and view the results/statistics test data: depende

To test direct tool, go to schedule bookmark an event link, edit the bookmark changing tool to directtool then exit the browser. Test 1 New browser Log into sakai Access the bookmark above,you should go direct to the event, not to the calendar view and th

The following PDF is the positioning paper - plan.pdf

Feel free to change Agenda Introductions Brief introduction Who are at the meeting and what is his or her role Does anyone wish to add to the agenda What are the current short term issues Which initiatives are currently running locally and centrally for Q

name: Preferences Tool purpose: Test Procedure to verify that users can modify their notifications, time zone, and language preferences expected result: User should be able to modify the preferences to language, time zone, and notifications and these resu

Introduction There are lots of possible projects or areas where work is needed in between releases. A variety of suggestions have been made over the past few releases and are listed below. Please feel free to add to the list! Many of these projects requir

View Source name: Portfolio Layout purpose: Test Procedure to verify that the Portfolio Layout tool functions properly. expected result: User should be able to upload .xhtml and .jpg files to specify HTML layouts for particular pages and give previews for

View Source name: Portfolio Template - REQUIRES WINDOWS & IE (does not work on linux) purpose: Test Procedure to verify that the Portfolio Template tool functions as desired expected result: User should be able to add, import, edit, export, and delete Por

Contents of archive FILENAME FUNCTION basic_project_stats.pl Build some basic statics to measure defect densities and the such collisions.pl Testing for shared packages database_update.pl Remove old data and add new dbh.conf Database configuration informa

Below is a summary of the QA 2.0.1 Post-Release Review conference call on 8/22/2005. Feel free to add additional items or modify any ITEM/ACTION shown below. Attendees: Michael Beasley, Nadine Blackwood, Carol Dippel, Clay Fenlason, David Haines, Peter Kn

Table of Contents Use the WebDriver Keyword Automated Testing Framework How to file a bug report... What is JIRA? JIRA is a web-based bug and issue tracking system developed by Atlassian Software Systems. Atlassian also develops Confluence, the enterprise

Place your good idea's here: Add idea and then write an explanation in a child page. Each idea needs to discreet so that we can may a time boxed project. I will add the best to a list of recommendation for process change - Alan Berg Short title Descript

The rough idea is to automate the following using Jira web services, to improve the workflow and distribute work fairly. 1) Get a list of all the "dead" users with assigned open issues - this would would anyone who was not logged in for 3 (or something) m

QA Reporting Lexicon (new) I would like to suggest adopting a standard lexicon of QA terms to be used in jiras and when report results. The following are suggested terminology and definitions: QA SUMMARY - summary of testing plan, OS tested, instance test

Overview Welcome Hi, welcome to QA Maven. This section is for Sakai QA testers who have the time and energy to delve more deeply into Sakai QA testing. If you are new to Sakai QA testing, you might want to start with our EZ QA effort and graduate up to be

Principles of QA and release management engagement Context This document defines a suggested structure on how to transition from Milestone, beta, release candidate to production. Note:This document does not define the relationship between the release p

Interested in hosting a QA server? Please read more about this process The QA build script valiantly tries to: 1) Make building/maintaining a QA server easy and sane 2) Ensure consistency among all of the servers on the "network" To use the script, you ne

columns=cf10079;OS;type;key;summary| 2

For Evaluation, Demos and QA Testing on Trunk Note - Server administrators, if you are modifing your server instance please modify the child page for this instance (see below) Indicates inbound and outbound email is enabled Server Name Version/OS/DB Locat

Issue Verification and Regression Tests Servers Read more about it... Current QA Test Servers Sakai 2.8 (maintenance) Sakai 2.9 (release 2012)

Sakai 11 QA Servers (out of date) Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below) Current Version - Sakai 10.6 is the latest community supported version Indicates inbo

Retired QA Servers Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below) Server Name Version/OS/DB Specs/Logs Location Notes QA1-US http://qa1-us.sakaiproject.org:8580/portal [

Sakai 10 QA Servers Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below) Current Version - Sakai 10.4 is the latest community supported version Indicates inbound and outbou

Sakai 2.6 QA Servers Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below). Current Version - Sakai 2.6.1 Indicates inbound and outbound email is enabled Server Name Version/O

Sakai 2.7 QA Servers Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below). Current Version - Sakai (Sakai 2.7.2) Indicates inbound and outbound email is enabled Server Name

Sakai 2.8 QA Servers Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below). TESTERS - It is possible the information in the tables is out of date. Please review the version num

Sakai 2.9 QA Servers Note - Server administrators, if you are modifying your server instance please modify the child page for this instance (see below) Current Released Version - Sakai 2.9.3 - Use 2.9.x for most up-to-date Indicates inbound and outbo

QA Test Automation Introduction This page is intended to be a resource for sharing ideas and tools for automating some (but not all!) of the QA process. With each subsquent release, there is more and more code to test. Automating some of the basic functio

2.9 Testing Participation Signup Release Highlights Wondering what is changing in 2.9? Please take a look at the 2.9.0 QA Changes, Assignments & Testing Status page and update based on your area's of interest. Please, Indicate your interest participatin

Introduction The QA-helper tool talks to instrumented code and generates reports based on metadata files and source code stored locally. In theory, the instrumented code does not have to reside locally or even be associated with Sakai. The tool graphicall

Introduction Location of daily bug pattern reports against trunk (findbugs only): Patterns that have already generated Jira's - http://qa1-nl.sakaiproject.org/codereview/bug_dashboard/index_generic.html http://qa1-nl.sakaiproject.org/codereview/bug_dashbo

Apache configuration In the logs directory add a robots.txt User-agent: * Disallow: / Edit /etc/httpd/conf/httpd.conf (Location may be different depending on OS) Note: Change log location LogFormat "%h %l %u %t \"%r\" %>s %b \"%{User-Agent}i\" %T" combin

Using Google Docs Test Scripts Several of the test scripts are in Google spreadsheets, with more being converted to Google spreadsheets as time allows. Clicking on the link for a tool's test script will take you to the Google doc. Click on a test script l

Introduction If you want to test sites with many concurrent users, a single machine probably will not manage all this work. Fortunatelly, we can run this test in a set of remote server at the same time. Startup server You must repeat this steps in every s

This document provides a java class and instructions on performing JVM monitoring via JMX, where the monitoring client connects to the JVM via SSH tunnels. Rationale Using JMX on a firewalled server can be difficult due to the unpredictable second port th

Some notes on the configuration of the automated code review - By Antranig Basman Comments Just the sort of email that improves the automated code review service. The email This has been a highly valuable study - the XRef source is very useful, and the re

Introduction A prototype Sakai tool was built to highlight the value of Automatic code reviews. The meaning of the generated report and the tool itself and surrounding content are described. After reading the Walk through for the example report generation

name: Resources Tool purpose: Verify that the Resources Tool is functional expected result: User should be able to add, create, move and delete files, create folders test data: resources.doc test description: dependencies: Course site has been created wit

Discussion

Introduction The code http://bugs.sakaiproject.org/confluence/download/attachments/29401/website.tar.gz Well you have seen the film, read the book and ignored the nightly generated reports. Static code review looks at the rather large amount of Sakai code

Introduction If you have a cloud account like cloudbees http://www.cloudbees.com/, you will be able to run test framework on it. The next steps are an example of deployment on cloudbees. Maven artifacts First you need to deploy testframework artifacts to

HOME This is the home of the S3 performance tests - October 2010 Interested parties should also review the Development workgroup's parallel effort. Emerging documentation can be found on Sakai 3 Load Testing

Pragmatic investigation of Kernel Services. Methodology To create a test plan for Jmeter requires setting a proxy up in Jmeter and observing the calls made during web browsing. While doing this services are investigated. This page details the results of t

SETUP Before performing a full series of capacity/ smoke tests, it is important to develop the test plans and also harvest the low lying fruits. To achieve this and to be able to reasonably compare with results generated recently you will need to-do the f

Slow Services The initial definition of a slow service is a service that consistently takes more than 100 ms to respond to requests of a single user under zero load. Obviously writing content, creating users/groups cost more time than reads. However, thei

This is the landing page for QA testing efforts related to Sakai 10 (the next major release following Sakai 2.9). Adopt-A-Tool signup sheet http://bit.ly/IeLxes Sakai Tools regression scripts http://bit.ly/sakaitoolsregression Sakai Testing Jiras which ne

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA01 QA01 testing officially opens Tuesday, December 17, 2013. Estimated to run through mid to late January. QA Servers - Longsight QA server https://qa10.longsight.

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA01/QA02 QA01/QA02 testing continues, through the end of January.. QA02 server - Longsight QA server https://qa10.longsight.com/ and Indiana QA server http://indian

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA03 QA03 testing is now active. QA03 is new feature freeze and string freeze. This is the beginning of our run to a release candidate. QA03 server - Longsight QA se

Sakai 10 qa4 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA04 QA04 testing is now active. We are targeting one or two QA releases away from our first release candidate. We are releasing a QA about every 2 weeks. The job of

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA05 QA05 testing is now active. We are targeting one or two QA releases away from our first release candidate. We are releasing a QA about every 2 weeks. The job of

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA06 QA06 testing is now active. The job of QA testers is to break Sakai. We want to find as many bugs as possible so that they can get fixed before a community rele

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10 - QA07 QA07 testing is now active. The job of QA testers is to break Sakai. We want to find as many bugs as possible so that they can get fixed before a community rele

Sakai 10 está diseñado para funcionar con los navegadores más modernos ♦♦♦ Totalmente soportados: (La versión más reciente en la fecha de salida de Sakai 10 en Junio de 2014) IE 11 Safari 7+ Firefox 29+ Chrome 35+ ♦♦ Parcialmente soportado: IE 8,9,10 S

This is the landing page for QA testing efforts related to Sakai 10 (the next major release following Sakai 2.9). Adopt-A-Tool signup sheet http://bit.ly/IeLxes Sakai Tools regression scripts http://bit.ly/sakaitoolsregression Sakai Testing Jiras which ne

This is the landing page for QA testing efforts related to Sakai 10.3 Sakai Testing Sakai 10.3 fixes https://jira.sakaiproject.org/issues/?filter=15016 Jiras which need to be verified before merging into the Sakai 10 branch - QA Servers - Sakai 10

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10 Sakai 10.3 Testing Overview More QA volunteers would be helpful. Please email sakaicoordinator@apereo.org mailto:sakaicoordinator@apereo.org . We are performing smoke testing

These are the actual file changes that have been committed since 10.2 . These files represent areas that have been fixed or modified in Sakai 10.3 wrt 10.2 and provide clues of areas to QA, based on the path as well as, in many cases, the file name. ---

This is the landing page for QA testing efforts related to Sakai 10.4 Sakai Testing Sakai 10.4 fixes https://jira.sakaiproject.org/issues/?filter=15270 QA Servers - Sakai 10

Sakai 10.4 rc01 is the release candidate. If not blocker bugs are found then it will become the release. Sakai 10.4 Testing Overview Sign up sheet on Google Docs https://docs.google.com/a/apereo.org/spreadsheet/ccc?key=0AmrS3XbKQ2pmdEZxOEdCOXllM0dRMkxtVD

This is the landing page for QA testing efforts related to Sakai 10.4 Sakai Testing Sakai 10.5 fixes https://jira.sakaiproject.org/issues/?filter=15373 QA Servers - Sakai 10

Sakai 10.5 rc01 is the release candidate. If not blocker bugs are found then it will become the release. Sakai 10.5 RC01 Testing Overview Sign up sheet on Google Docs https://docs.google.com/spreadsheets/d/1KLs6fClWUwXtoWT_J11lt4ScTD_j2LQZnofTMrreC-g/edi

This is the landing page for QA testing efforts related to Sakai 10.6 Sakai Test Plans Sakai 10.6 fixes https://jira.sakaiproject.org/issues/?filter=15480 S https://jira.sakaiproject.org/issues/?filter=14299akai issues need testing on nightly (master)

A number of issues have been fixed in Sakai master/trunk, but need to be verified before they can be merged into the Sakai 10 branch and can become part of the 10.6 release. Sakai 10.6 Testing Overview Sign up sheet on Google Docs https://docs.google.com

This is the landing page for the Sakai 10.7 QA testing effort. We should complete testing by Friday, March 25 at latest. Goal Test the issues listed on this page, which should all be fixed in the 10.7 release. Server Please test on the QA server for 1

Overview The Sakai 11 JIRAs page provides information for testing Sakai 11 JIRA issues. Here you’ll find useful information for locating, testing, and documenting the resolution of Sakai 11 JIRA issues. See the sections below to get started. How to Test J

Overview The Sakai 11 QA Hub is the home page for the Sakai 11 QA effort. Here you’ll find useful information for getting involved with testing and becoming part of our growing Sakai QA community. See the sections below to get started! Current QA Testin

Last updated October 11 , 2016 Sakai 11.2-RC02 is available! This is our second release candidate for Sakai 11.2. Target completion of testing by Tuesday, November 8. Testing - test blocker priority Jiras fixed in RC02, and some light testing in Lesson

Last updated February 10, 2017 Summary Release candidate testing is to check for any regressions that may have been introduced by the 169 improvements (mostly bug fixes) that were applied for the 11.3 release. The main area to test is Samigo Test and Quiz

Last updated May 31, 2017 Summary Release candidate testing is to check for any regressions that may have been introduced by the improvements (mostly bug fixes) that were applied for the 11.4 release. Main testing: The community has done a lot of testing

Overview The Sakai 12 QA Hub is the home page for the Sakai 12 QA effort. We are testing new fixes on Master (next release version 19), to be merged back to the 12.x Maintenance Branch to prepare for our next maintenance release (12.4). We are testing on

Goals for Sakai 12.0 Regression/ Release testing: Make sure we are all on the same page for Regression/Release testing How to cover Mobile and multiple browser testing Explore (and decide) how to measure our progress Start a dialogue on how to evolve our

Overview The Sakai 19 JIRAs page provides information for testing Sakai 19 JIRA issues. Here you’ll find useful information for locating, testing, and documenting the resolution of Sakai 19 JIRA issues. See the sections below to get started. How to Test J

Overview The Sakai 19 QA Hub is the home page for the Sakai 19 Quality Assurance effort. For questions please contact sakai-qa@ mailto:sakai-qa@apereo.orgapereo.org http://apereo.org/ Testing The web page for all the testing servers can be found here: htt

CLE 2.9.3-rc03 - Release candidate 03. New Jiras added in RC03 : COMPLETE TESTING BY - Monday, August 12, 2013 by end of day, your time zone. QA Servers - currently http://qa29.longsight.com http://qa29.longsight.com is on RC03 . Please check - QA Servers

Overview The Sakai 20 QA Hub is the home page for the Sakai 20 Quality Assurance effort. For questions please contact sakai-qa@ mailto:sakai-qa@apereo.orgapereo.org http://apereo.org/ Testing The web page for all the testing servers can be found here: htt

Overview The Sakai 21 QA Hub is the home page for the Sakai 21 Quality Assurance effort. For questions please contact sakai-qa@ mailto:sakai-qa@apereo.orgapereo.org http://apereo.org/ Testing The web page for all the testing servers can be found here: htt

Overview The Sakai 22 QA Hub is the home page for the Sakai 22 Quality Assurance effort. For questions please contact sakai-qa@ mailto:sakai-qa@apereo.orgapereo.org http://apereo.org/ Testing The web page for all the testing servers can be found here: htt

Overview The Sakai 23 QA Hub is the home page for the Sakai 23 Quality Assurance effort. For questions please contact sakai-qa@ mailto:sakai-qa@apereo.orgapereo.org http://apereo.org/ Sakai QA Planning Meetings The Sakai QA Planning Group meets every Thur

Overview The Sakai 25 QA Hub is the home page for the Sakai 25 Quality Assurance effort. For questions please contact sakai-qa@ mailto:sakai-qa@apereo.orgapereo.org http://apereo.org/ Sakai QA Planning Meetings The Sakai QA Planning Group meets every Thur

Introduction Test framework use JMeter http://jakarta.apache.org/jmeter/ to perform load tests. There are two different tests, Generic and Random. The Generic test browse all sites pages and tools of the user several times (portal loop count). Browse Test

Sakai CLE 2.9.0 tool list The ISSUES are a subset of issues needing testing for this tool TOOL ISSUES Sample Tool Account +Add Tool (New!) Aliases (Admin Site Management) Announcements (ad hoc regression) https://docs.google.com/spreadsheet/ccc?ke

Introduction You can test the new chat feature in Neo Portal. Just type: mvn clean test site [-Dtest-dir=neoportal] See core package properties and readme file to get more info.

Current QA activities in this column QA Servers http://nightly2.sakaiproject.org/ Meeting Logistics: BigBlueButton https://apereo.rooms.blindsidenetworks.com/rooms/oiq-xxg-klh-dva/join hosted by BlindsideNetworks Thursdays, at 10 AM (New York time, GMT-4)

To self report your QA effort fill out this simple Google form - http://bit.ly/sakai11badges http://bit.ly/sakai11badges Black Belt Molly Kelsey 4,515 ChaithanyaKrishna Reddy Noti 2,630 Sristi Shrestha 2,105 Red Belt Laura Cira 1,650 Derek Ramsey 1,570 Ka

Coming Soon - Sakai 10 QA testing ----------------------------------------------------- We expect to ramp up a full scale QA testing effort for Sakai 10 in early December 2013! Help Now - if you are able --------------------------------------------------

The ability to add a stealthed tool and add it to several sites at once will work for both LTI 1.1 and 1.3. Tsugi Admin Setup Log into https://sakai.tsugicloud.org/tsugi/admin/ https://sakai.tsugicloud.org/tsugi/admin/ Click Manage Access Keys Click Tenan

SakaiBogoBugs Feel free to add, remove rules, change weightings and generally make comments. OK, so some bugs are worse than others so lets change that to Weighted SakaiBogoBugs per thousand lines of code. Resources http://findbugs.sourceforge.net/bugDesc

name: Samigo: Assessment Creation purpose: Verify that the Samigo tool is accessible and that users can create, edit, and manage online assessments. expected result: Users should be able to create and upload a test test data: resources.doc dependencies: C

name: Samigo: Assessment Submission purpose: Verify that the Samigo tool is accessible and that users can take the assessments and submit their results, and also check the statistics of the assessment. expected result: Users should be able to run through

name: Samigo: Assessment Import, Export and Question Pools purpose: Verify that the Samigo tool is can export, import and manage online question pools. expected result: Users should be able to export assessments, import assessments, and cull questions fro

Sample Keyword Framework Script. openURL|/portal/xlogin enterText|user id|seleniumInstructor enterText|password|seleniumInstructor click|Login verifyText|selenium instructor verifyText|Worksite Setup verifyText|Welcome to your personal workspace click

name: Sections Tool purpose: Test Procedure to verify that sections can be created, edited, deleted and students can be assigned, and can join, sections expected result: User should be able to create, edit, delete sections, assign students to sections, an

This page is intended for sharing ideas and resources related to using Selenium and Selenium IDE http://www.openqa.org/selenium-ide/ {composition-setup} {composition-setup} {deck:id=beef jerky} {card:label=Selenium How To} Selenium: For Regression testing

Selenium Remote Control http://selenium-rc.openqa.org/ http://selenium-rc.openqa.org/ Selenium Remote Control (RC) is a test tool that allows you to write automated web application UI tests in any programming language against any HTTP website using any ma

The instructions are for using two different servers to mimic a real-world experience. The tenant is on one server, while the external tool, users and main course are on a different server. Important: Given the setup instructions below, if the tenant is o

QA Milestone Boundaries http://confluence.sakaiproject.org/display/QA/QA+Milestone+Boundries Document with suggested criteria for QA transitioning across tagging boundaries.

Below you will find a list of Core Tools Assignments Smoke Test Announcements Smoke Test Chat Smoke Test Forums Smoke Test Gradebook SG2X Help Smoke Test Messages Smoke Test News Smoke Test Post'Em Smoke Test Profile Smoke Test Resources Smoke Test Roster

name: Site Editor Tool - Import From Site (Replace) purpose: Test Procedure to verify that users can import data/tools from other existing sites expected result: User should be able to import specific tools, and the tool data, into a different site test d

View Source name: Site Info - Edit Site Information, Tools purpose: Test Procedure to verify that site owner can edit the information and tools expected result: User should be able to modify the site information and toolset test data: dependencies: Site

View Source name: Site Editor - Edit Site Information, Tools purpose: Test Procedure to verify that site owner can edit the information and tools expected result: User should be able to modify the site information and toolset test data: dependencies: Si

View Source name: Site Editor Tool - Import purpose: Test Procedure to verify that users can import data/tools from other existing sites expected result: User should be able to import specific tools, and the tool data, into a different site and those impo

name: Site Statistics Tool purpose: Test Procedure to verify that an Instructor can view the recent activity for a particular site and generate a report on it expected result: User should be able to view the recent activity for a particular site test data

View Source name: Styles Tool purpose: Test Procedure to verify that the Styles tool functions properly. expected result: User should be able to upload styles and apply them to other tools that support his functionality. test data: Professional.css, Wacky

Overview An Ant script runs three custom tasks: An ant contribution task that reads a list of directories from a properties file and loops through the directory names. PMD which checks the source code for style and duplicate code QJ PRO which checks the s

rSmart has written basic test scripts for the 2.5 release that they'd graciously like to contribute back to the community. We're going to use these as a jumping point to revamp the test condition documentation the community has for testing so there is com

Introduction This section is in-progress This page will start a jumping point for test documentation for Sakai 'out of the box' (i.e. OOTB). The first step is to compile a complete and accurate test of test conditions for all components. There is a grea

This recipe is easiest way to I know to generate test coverage reports for a sakai project: Download the sakai developer license for clover (see attached) Write unit tests and configure maven to run these tests and/or test suites (see the maven test docum

Test Fest Scripts TestFest.png Test Server: Link to the server that needs to be used for this round of testing Column Name Description Status After the Jira has been tested, please enter a y (for success) or n (for failure) in this column Ji

.wiki-content { width: 1000px; padding: 1em} QA Servers - Home QA Servers - Sakai 10 QA Servers - Sakai 2.9 QA Servers - Eval, Demo and Trunk

{composition-setup}{composition-setup} {deck:id=myDeck} {card:label=tab1} This is the first tab's content {card} {card:label=tab2} This is the second tab's content {card} {deck}

Introduction Any tool's first page that requires more than one second to load most of the times has performance problems. Link to history report to validate. See test results http://qatf.yoan.cloudbees.net/ChronosGroup.html. More tests will be added soon.

Selenium Tips Selenium currently has poor support for highly dynamic sites such as Sakai 3. Often the procedure to make a test using the Selenium IDE is to record your clicks then change all the 'verifyTextPresent' commands to 'waitForTextPresent'. Tests

Setting the Auto-submit Option Tests & Quizzes has a setting to have quizzes auto-submit when the due date or late allowed date has arrived. Create a quiz Click on Settings Autosubmit saved student work after latest acceptance date is under the Availabil

Introduction To analysis each project separately PMD and QJ Pro are run from within an ANT build file. This allows for control via a specific property file. Basically a Perl script generates a bash script that runs a build per project. The Perl script als

Overview Welcome How are you ? Have you mastered the EZ QA process ? What is this? This is on level up from EZ Testing, the next "power up" to contribute to the QA effort. Here you will be testing fixes that have been made, but not applied yet to the 12

Types of issues found Introduction Catching and ignoring issues (sweeping problems under the carpet) Duplicate code (Pattern issues) Large class files (Pattern issues) Unused resources (Junk DNA) System outs (Failure to use the logging infrastructure) Unn

Generating Log files for later analysis To generate access log files in the logs tomcat directory of your Application. Add the following just before </Host> in conf/server.xml <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" p

Test Planning/Analysis

Walk through Live code coverage quickly point to failure nodes for reproducible cases. To quickly train QA in the effectiveness of EMMA I have written a tool that mimics Russian Roulette. There are size buttons that call six methods one of which is at ran

Introduction Based on: Initial manipulation of commit data by Charles Severance The commit logs since the start and Findbugs report from 20 January 2009 pulled out of .externals Static code analysis I have converted raw data into TM3 format (find attached

Introduction This is a quick walk through of a basic debug session using a prototype of the QA helper tool. see also: Report details Visual walkthru Reset of session data The current prototype resides at http://qa1-nl.sakaiproject.org:82 http://qa1-nl.sak

name: Web Content purpose: Verify that the Web Content tool is functional expected result: User should be able to display web content through the Web Content tool. User should be able to edit links and tool names. test data: dependencies: SiteSetup has

Overview The Keyword Framework has been created to expand automated functional testing to a broader range of users, and to make people familiar with automation more productive. The Framework enables users to create test cases in a pipe-delimited format, w

Introduction You can test Sakai 2.x web services (only getAllSites). Just type: mvn clean test site [-Dtest-dir=webservices] See core package properties and readme file to get more info.

This page will help you to get started with Sakai QA (Quality_Assurance) testing easily and quickly. As a QA Tester You will be responsible for finding and reporting bugs and glitches. This means you will have the fun and thrill of discovering the unknown

View Source name: Wizards Tool - Sequential and Hierarchical purpose: Test Procedure to verify that the Wizards tool functions as expected expected result: User should be able to add, revise, export, delete, import, and manage both Sequential and Hierarch

A cron job spawns the bash shell.The bash shell performs the following: uses svn to download the source code generates the internationalization information on the fresh code. via maven compiles and packages Sakai demo renames test code so that it is no lo