Manual Test Report for XWiki 11.3 RC1

Version 200.1 by Ilie Andriuta on 2019/04/25
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:TestReports.ManualTestReportXWiki139RC1.WebHome]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

The aim of this report is to test XWiki 11.3 RC1 and see that everything is working properly.

Tested Browsers & Databases

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:TestReports.ManualTestReportSummaryXWiki113RC1.WebHome]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

Here is the list of browsers we support and how they have been tested for this release:

 BrowserTests performed and results
Chrome30.pngGoogle Chrome 74Not Tested
Firefox30.pngMozilla Firefox 66Not Tested
Edge30.pngMicrosoft Edge 18Not Tested
IE30.pngInternet Explorer 11New and Noteworthy Features + Jira Tickets Marked as Fixed in the Release Notes
Safari30.pngSafari 12Not Tested

Here is the list of databases we support and how they have been tested for this release:

 DatabaseTests performed and results
hypersql.pngHyperSQL 2.4.1Not Tested
mysql.pngMySQL 5.7Not Tested
oracle.pngOracle 12cNot Tested
postgresql.pngPostgreSQL 11New and Noteworthy Features + Jira Tickets Marked as Fixed in the Release Notes

Here is the list of Servlet Containers we support and how they have been tested for this release:

 Servlet ContainerTests performed and results
tomcat-icon.pngTomcatNot Tested
jetty-icon.pngJetty (XWiki Standalone packaging)New and Noteworthy Features + Jira Tickets Marked as Fixed in the Release Notes
jetty-icon.pngJettyNot Tested

Jira Tickets Marked as Fixed in the Release Notes

Release Notes

TicketTest ResultTested by
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
Not Tested
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.

Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
Not Tested
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
FailedIlie
star
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie
PassIlie
Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
PassIlie

star Regarding Failed to execute the [jira] macro. Cause: [unable to create native thread: possibly out of memory or process/resource limits reached]. Click on this message for details.
, the issue is still reproducing due to ;

Get Connected