TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-23T06:28:58ZTYPO3 Forge
Redmine TYPO3 Core - Task #103473 (Resolved): Account for double click pagetree timeout in acceptance testshttp://forge.typo3.org/issues/1034732024-03-23T06:28:58ZBenjamin Franzkeben@bnf.devTYPO3 Core - Feature #103439 (Under Review): Site TypoScripthttp://forge.typo3.org/issues/1034392024-03-20T14:35:14ZBenjamin Franzkeben@bnf.dev
<p>Allow TypoScript without requiring sys_template records.</p>
<p>Idea: A site can define TypoScript and include other dependencies via profiles (<a class="issue tracker-2 status-8 priority-4 priority-default child" title="Feature: Site Profiles that ship Settings, TypoScript, TSConfig, Templates and enabled Content Elements (Under Review)" href="http://forge.typo3.org/issues/103437">#103437</a>)</p> TYPO3 Core - Task #102502 (Closed): Fix support for bash v3 in runTests.shhttp://forge.typo3.org/issues/1025022023-11-24T09:06:20ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #102450 (Closed): Refer to minor versions for our images in runTestshttp://forge.typo3.org/issues/1024502023-11-22T13:54:56ZBenjamin Franzkeben@bnf.dev
<p>Allows to auto-update local images for feature-updates<br />simply by raising them in runTests.sh (like we do for<br />external images as well).</p>
<p>That means <code>runTests.sh -u</code> is only needed in case<br />patch updates are desired or needed.</p> TYPO3 Core - Task #102449 (Closed): Automatically remove containers in runTests.shhttp://forge.typo3.org/issues/1024492023-11-22T13:45:17ZBenjamin Franzkeben@bnf.devTYPO3 Core - Bug #101278 (Resolved): Fix incorrect DateTimeTest method nameshttp://forge.typo3.org/issues/1012782023-07-06T21:16:34ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #98270 (Closed): Drop unneeded .cache/.npmrchttp://forge.typo3.org/issues/982702022-09-06T20:15:27ZBenjamin Franzkeben@bnf.dev
<p><code>unsafe-perm = true</code> is not available in npm v8 documentation, and TYPO3 core requires npm v8, so the setting should not be needed.</p> TYPO3 Core - Bug #97123 (Closed): ResourceCompressorTest.php fails in random ordered unit testshttp://forge.typo3.org/issues/971232022-03-06T06:44:52ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://git.typo3.org/typo3/CI/cms/-/jobs/1109375">https://git.typo3.org/typo3/CI/cms/-/jobs/1109375</a></p>
<pre>
1) TYPO3\CMS\Core\Tests\Unit\Resource\ResourceCompressorTest::getFilenamesFromMainDirInBackendContext with data set #3 ('typo3temp/assets/compressed/.htaccess', '../typo3temp/assets/compresse...access')
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'../typo3temp/assets/compressed/.htaccess'
+'typo3temp/assets/compressed/.htaccess'
/builds/typo3/CI/cms/typo3/sysext/core/Tests/Unit/Resource/ResourceCompressorTest.php:604
</pre>
<p>Steps to reproduce:</p>
<pre>
rm -rf typo3temp/Build/Scripts/runTests.sh -s unitRandom -o 1646183048
</pre>
<p>Also reproducible with:</p>
<pre>
rm -f typo3temp/assets/compressed/.htaccess && Build/Scripts/runTests.sh -s unit -e "--filter getFilenamesFromMainDirInBackendContext" typo3/sysext/core/Tests/Unit/Resource/ResourceCompressorTest.php
</pre> TYPO3 Core - Task #96951 (Closed): Streamline tab-handling in ElementsBasic cestshttp://forge.typo3.org/issues/969512022-02-17T15:03:36ZBenjamin Franzkeben@bnf.dev
<ul>
<li>Avoid scrollIntoView which is no longer<br /> needed since <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: preselected TCA useOrOverridePlaceholder checkbox/input fields cause autofocus on initial page load (Closed)" href="http://forge.typo3.org/issues/96947">#96947</a></li>
<li>Do not catch exception on tab-click in<br /> ElementsBasicInputRangeCest which only have been<br /> introduced in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Acceptance Test Failure for InputRangeCest (Closed)" href="http://forge.typo3.org/issues/93629">#93629</a> but actually due not catch<br /> the case where the tab is already scrolled, but<br /> where the content is scrolled away.<br /> Again no longer needed due to <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: preselected TCA useOrOverridePlaceholder checkbox/input fields cause autofocus on initial page load (Closed)" href="http://forge.typo3.org/issues/96947">#96947</a>.</li>
</ul> TYPO3 Core - Task #96409 (Closed): Port remaining JavaScript unit tests to TypeScripthttp://forge.typo3.org/issues/964092021-12-21T07:03:33ZBenjamin Franzkeben@bnf.dev
<p>typo3/sysext/backend/Tests/JavaScript/FormEngineValidationTest.js<br />typo3/sysext/backend/Tests/JavaScript/IconsTest.js<br />typo3/sysext/backend/Tests/JavaScript/PopoverTest.js</p>
<p>Will ease igration to ES6 modules.</p> TYPO3 Core - Task #96396 (Closed): Prepare ImmediateActionElementTest for ES6 moduleshttp://forge.typo3.org/issues/963962021-12-20T12:55:12ZBenjamin Franzkeben@bnf.dev
<p>In ES6 mode Viewport.Topbar and ModuleMenu.App properties<br />cannot be overwritten (in order to be substituted with a call spy),<br />as they reference other JavaScript modules.<br />The properties of ES6 models are readonly ("frozen") and can<br />therefore not be overwritten in a test setup.</p>
<p>Therefore the test should adapted to overwrite the references<br />in Viewport and ModuleMenu instead.</p> TYPO3 Core - Bug #94135 (Closed): Typo3DbQueryParserTest fail with wrong timestamp when php timez...http://forge.typo3.org/issues/941352021-05-13T08:25:12ZBenjamin Franzkeben@bnf.dev
<p>My php timezone is Europe/Berlin and unit tests error in this case:</p>
<pre>
./bin/phpunit -d memory_limit=1G -c vendor/typo3/testing-framework/Resources/Core/Build/UnitTests.xml typo3/sysext/extbase/Tests/Unit/Persistence/Generic/Storage/Typo3DbQueryParserTest.php
1) TYPO3\CMS\Extbase\Tests\Unit\Persistence\Generic\Storage\Typo3DbQueryParserTest::visibilityConstraintStatementIsGeneratedAccordingToTheQuerySettings with data set "in fe: respect enable fields and do not include deleted" ('FE', false, array(), false, '(tx_foo_table.deleted_column ...79200)')
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'(tx_foo_table.deleted_column = 0) AND (tx_foo_table.disabled_column = 0) AND (tx_foo_table.starttime_column <= 1451779200)'
+'(tx_foo_table.deleted_column = 0) AND (tx_foo_table.disabled_column = 0) AND (tx_foo_table.starttime_column <= 1451775600)'
/home/ben/src/TYPO310.CMS/typo3/sysext/extbase/Tests/Unit/Persistence/Generic/Storage/Typo3DbQueryParserTest.php:607
/home/ben/src/TYPO310.CMS/vendor/phpunit/phpunit/phpunit:61
2) TYPO3\CMS\Extbase\Tests\Unit\Persistence\Generic\Storage\Typo3DbQueryParserTest::respectEnableFieldsSettingGeneratesCorrectStatement with data set "in FE: respectEnableFields=true" ('FE', true, '(tx_foo_table.deleted_column ...79200)')
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'(tx_foo_table.deleted_column = 0) AND (tx_foo_table.disabled_column = 0) AND (tx_foo_table.starttime_column <= 1451779200)'
+'(tx_foo_table.deleted_column = 0) AND (tx_foo_table.disabled_column = 0) AND (tx_foo_table.starttime_column <= 1451775600)'
/home/ben/src/TYPO310.CMS/typo3/sysext/extbase/Tests/Unit/Persistence/Generic/Storage/Typo3DbQueryParserTest.php:672
/home/ben/src/TYPO310.CMS/vendor/phpunit/phpunit/phpunit:61
</pre> TYPO3 Core - Task #89890 (Closed): Reset PSR-11 container in GeneralUtility in unit testshttp://forge.typo3.org/issues/898902019-12-06T21:43:26ZBenjamin Franzkeben@bnf.dev
<p>If a container instance is provided for a unit test via GeneralUtility::setContainer(), it needs to set to null again, in order to not affect other unit tests.</p> TYPO3 Core - Task #89280 (Closed): TypoScript Template Constant Editor flushes to many caches, re...http://forge.typo3.org/issues/892802019-09-25T21:26:07ZBenjamin Franzkeben@bnf.dev
<p>Reported by Simon Schaufelberger via Slack channel #psr11-initiative:</p>
<pre>
Sunday, August 4th 3:21 pm
The problem also is that the DI cache gets flushed way too often.
I just saved a typoscript constant in the template module and the whole cache was empty again afterwards.
Wondering why the DI cache needs to get flushed in such a case
</pre>
<p>The reason is the usage of clear_cacheCmd('all') which flushes all core caches like ext_localconf and DI cache.<br />Also opcache is flushed. These caches are unaffected by TypoScript Template change.s</p> TYPO3 Core - Bug #87997 (Rejected): Links to workspace overlays should not be generated without b...http://forge.typo3.org/issues/879972019-03-25T11:49:57ZBenjamin Franzkeben@bnf.dev
<p>If an editor links to a versioned page id (let's say 1011) directly (e.g. by specifying that id in header_link),<br />that link is currently generated as /index.php?id=1011 when the frontend is visited as a regular visitor (e.g. without backend/workspace context).</p>
<p>Visiting that page will fail with "page not found" (which is fine).</p>
<p>It would be expected that links wouldn't be generated at all (that means: link is empty), as for hidden/deleted pages.</p>