View on GitHub

equella.github.io

Testing Guide for Equella 6.5-GA

_DRAFT_

Please refer to the 6.5-GA Release Notes for more details.

#104 Scripting pack

Now in the master docs repo. Self-creation of the javadoc in issues #105 and #106 (still pending)

Testing:

#98 / #102 Office Integration

Equella has the ability integrate with Microsoft Office products to enable a smoother editing experience. Due to licensing issues, and the inherit issues of using an older interop DLL on more modern installs of Office, the download of the Office Integration msi package has been removed from the Equella Web UI, and the DLLs in question have been removed from the git repo. The functionality is still useful, so conceptual documentation has been provided for users to build this functionality.

Testing:

#101 / Documentation / example files moved to the master docs repo

Testing:

#100 HTML Editor Plugins

Another documentation shift to the main docs repo.

Testing:

#96 (Make installer set executable bit for files that need it)

After a Linux install, the sys admin no longer needs to chmod the jsvc, manager, and equellaserver scripts

Regression testing:

#84 Re-implement file upload features

File uploads were re-implemented using AJAX instead of multipart and client side progress instead of server side.

Regression testing:

#56 (Remove dhfjava dependency)

The functionality was changed to not rely on dhfjava. Instead it uses a Tika open source library. The results are not as clean as dhfjava, so enhancements are welcome!

Functional testing:

Performance testing:

#72 (Allow configuration of the historically hardcoded donotreply@equella.com email address)

System admins now configure the ‘do not reply’ email address via the Server admin pages.

Functional testing:

#74 (Remove the UpgradeProxyWeb python server)

The functionality point the Equella Manager at a server that provides the latest Equella update has been removed.

Functional testing:

Regression testing:

#73 / #60 General build changes / scrubbing of commercial terminology

Hard-coded words denoting the last commercial owner and last commercial website of Equella were removed. Generally, resources (lang bundles and images) functionally haven’t changed, but how they are bundled into Equella did change.

Functional testing:

Regression testing:

#71 ( Allow configuration of LTI external tool contact for Equella )

When an LTI attachment was added to an item, at times it’s considered ‘default’, and historically, a default consumer contact email of support@equella.com was used. Now, you can configure this behavior by adding external.tool.contact.email into optional-config.properties.

Functional testing:

Regression testing:

#62 ( Upgrade flamingo )

Flamingo was upgraded to streamline dependencies from Maven.

Functional testing:

#59 ( Replace use of hibernate-beanlib )

beanlib-hibernate was used for cloning a whole hibernate object tree but it had code which we no longer had the source too, so it was replaced with the use of xstream + special hibernate converters.

Regression testing:

#55 / #107 ( Kaltura licensing issues )

The Kaltura Java client API is not Apache-license-friendly. It was moved into it’s own repo, but can be integrated back into Equella per client by building the Equella and Kaltura source repos together into an upgrade binary.

Functional testing:

Regression testing:

#54 ( Make Oracle DB driver optional )

Oracle DB driver is no longer included by default. To run these tests, you’ll need a build of Equella with Oracle drivers included.

Regression testing:

#44 / #46 ( Installer / Upgrader built via SBT )

Installers and upgraders are all built via SBT.

Regression testing:

#41 ( Remove eCommerce )

eCommerce was never used by clients in Equella (since it was an option when generating commercial licenses).

Regression testing:

#33 ( Upgrade ROME )

Regression testing:

#27 ( Work out what to do about hardcoded SHA256 hash salt )

Functional testing:

Regression testing:

#5 ( Remove license validation components )

Functional testing:

Fixes arising from cherry pick

https://github.com/equella/Equella/commit/64e85c2b4560580e517474c302b3d543ce79c34f

Regression testing:

Upgrade javax.servlet, flickr, datatools, sqlserver jdbc, kalturaclient

https://github.com/equella/Equella/commit/2b18a3707c31a5c643803560570073db445e8d3c

Regression testing:

Upgrade srw servlet

https://github.com/equella/Equella/commit/e2ab5bd7a6574b77b3abddd91b2802574dd9ad71

Regression testing:

Use latest jna

https://github.com/equella/Equella/commit/be29f0e80e8db106216301aac21b7563e8ddbaa1

Regression testing:

Option to self-generate a keystore when building or use a previously

https://github.com/equella/Equella/commit/8f1201bf561bfbf340dbedcfa2f1c88d3f0888d7

Regression testing:

“Use a custom param for the course ID” in Canvas

EQ-31 ensure IMS/SCORM resources containing query strings will work

EQ-32 batched audit log removal

EQ-33 don’t use the public bookmark, use the actual params

EQ-34 use string URLs instead of URL URLs

EQ-2045 use LIST_COURSE_INFO priv, not LIST_COURSE

EQ-2038 course API refactor

Activation, Course,

EQ-1045 (et al) refactors of entity rest services

One of [VIEW_SECURITY_TREE, EDIT_SECURITY_TREE] is required

EQ-2026 Do some validation on entities. don’t let entity editing be a free-for-all

Users can edit the names of selected resources that will be added to the LMS in a selection session

A new checkbox “Select all attachments” has been added to the “Add to External System” page.

Course builder in brightspace not using selected module

New permission for selection sessions

URL checker number of attempts

URL checker will disable links to external sites (e.g. Link attachments) if the URL check fails 10 times, and will send email notifications to item owners if the check fails 5 times. This hard coded settings are now configurable in optional-config.properties

urlChecker.triesUntilWarning = 3
urlChecker.triesUntilDisabled = 5

SQL Server concurrency issue

The TLE_ADMINISTRATOR account is not required to accept DRM agreements

Users were able to access inactive copyright attachments via using a direct URL

The item moderation REST API would return a random workflow node status each time it was invoked

Issues Covered in General Regression Test