- 07 May, 2022 1 commit
-
-
phpstan parallel execution is limited to a maximum of 5 processes to be a nice neighbor when executed during core CI runs. This however leads to longer execution times when executed on local developer machines with many available CPU's. This patch introduces two separated phpstan config file entrypoints, one for local and one for CI. They are automatically selected in runTests.sh based on existence of a CI env variable. Resolves: #97571 Releases: main, 11.5 Change-Id: I14bf13412de7a2471703e7982dad4030ae6ba735 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74536 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 04 May, 2022 1 commit
-
-
Currently acceptance tests do not work on arm64 (Apple M1) due to the lack of support in the selenium docker image. This has been fixed by detecting arm64 and switch to arm64 compatible image (seleniarm/standalone-chromium). Resolves: #97541 Releases: main, 11.5, 10.4 Change-Id: I531e7e1d7f0f11a1c6d850699eee3b4a9aa3e5d0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74502 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
André Buchmann <andy.schliesser@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 06 Apr, 2022 1 commit
-
-
The check for doing the functional test splitting script and running the selected chunk used similar but different minimum chunk value to check against. Thus the splitting script has not been executed in all chunk execution contexts. This patch uses now exactly the same check in the 'Build/Scripts/runTests.sh' like it is defined in the corresponding docker-compose service config. Furthermore all previous created functional split files are now removed to avoid leftovers, which occured if re-run has lower chunksize defined. Example which is now properly fixed: > Build/Scripts/runTests.sh -s functional -c 1/1 Example with partial part files from previous run: > Build/Scripts/runTests.sh -s functional -c 1/10 > Build/Scripts/runTests.sh -s functional -c 1/8 Resolves: #97283 Releases: main, 11.5, 10.4 Change-Id: Id3a0d1c85540b4e7e46aaea69cf2d96839e8e72e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74157 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 31 Mar, 2022 1 commit
-
-
Christian Kuhn authored
When core functional tests started to heavily rely on CSV based import- and assertion files, we found that editing such .csv files in Microsoft Excel leads to warnings if the number of columns is not identical for each row. Script checkIntegrityCsvFixtures.php has then been established to verify all rows of .csv fixture files have the same amount of fields per file, and has been enabled as CI job to ensure all existing fixture files follow this. Nowadays, this restriction feels archaic: Devs actively working with these CSV files typically edit them in an IDE like PhpStorm directly and don't use Excel for this anymore. The PhpStorm plugin "Rainbox CSV" also helps by coloring these files and other alternatives like libreoffice do not have this 'all rows must have same number of colums' restriction. The patch drops the script, the runTests.sh usage and the CI calls. This has the additional advantage that line breaks for single fields are now possible, which will further improve handling and readability of field values in upcoming patches. Resolves: #97274 Related: #83943 Releases: main, 11.5, 10.4 Change-Id: I2b4c2afc98c8471bccae1afb15e055182b563ee7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74129 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Jan Helke <jh@f7.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Jan Helke <jh@f7.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 29 Jan, 2022 1 commit
-
-
We currently have the situation that phpstan is hard to update and maintain due to the phpstan config file that sets very specific rulesets. This is unfortunate since phpstan tends to change and rename rules at will. The general usage API of phpstan is basically as follows: Have a slim config file that sets the basic level. Then maintain a 'baseline' file that lists violations, using the --generate-baseline command option. The todo job for people working on phpstan errors is then to look at the baseline file, pick up some issues, fix them, then re-generate baseline. When baseline is small enough, the level is raised, a new baseline is generated, and the fix-job starts again. The patch does exactly this: The existing config is dropped and runTests.sh receives a command to generate baseline. With this in place, we can easily raise phpstan to a PHP 8.1 compatible version: > composer req friendsoftypo3/phpstan-typo3:"^0.9.0" --dev > composer req phpstan/phpstan:"...
-
- 24 Jan, 2022 1 commit
-
-
Gitlab is able to give a nice overview of tests and how often a test failed recently which makes it easier to investigate flaky/failed tests. Also it takes away the pain of searching for the actual failing test in a job because it only displays information of the failed test (no bootstrap log details and such) Codeception AC test reports have been added to the Gitlab GUI using the --xml flag to generate a Gitlab readable report format and it has been added to the jobs artifacts:reports:junit. Resolves: #96628 Releases: main, 11.5 Change-Id: Id5ab5adfdc318c0c97143b0f05311f47fd1d37f0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73136 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 21 Jan, 2022 1 commit
-
-
Benjamin Franzke authored
Use the JavaScript module and importmap Feature introduced in #96510 to import JavaScript as native browser modules (commonly referred to as ES6 modules, or short ESM). To be specific: we actually use ES2020 (ES11) modules, as we import modules dynamically via import() in combination with an importmap (#96510). Backwards compatibility for existing RequireJS imports is provided by a shim as introduced in #96510. How to (re)view this change --------------------------- Exclude all automatic TypeScript/JavaScript/lockfile changes with: git show --oneline -- . \ ':(exclude)typo3/sysext/*.js' \ ':(exclude)Build/Sources/TypeScript/*.ts' \ ':(exclude)Build/yarn.lock' git show --oneline -- $(find Build/ \ -name DragUploader.ts -o \ -name FormEngine.ts -o \ -name Helper.ts -o \ -name CKEditorLoader.ts -o \ -name CodeMirrorElement.ts) Gruntfile & tsconfig.json ------------------------- Gruntfile is adapted to transform all our dependencies into ES6 modules. Also tsconfig is adapted to emit es2020 modules (es2020 is required for dynamic module imports with import()). Also allowSyntheticDefaultImports is enabled while esModuleInterop is now longer needed as we target ES modules and therefore removed. allowSyntheticDefaultImports had been enabled implicitly by esModuleInterop, we still need this enabled as the type declarations of our dependencies still imply AMD/CJS exports (which we fix in our build steps). JSUnit ------ JSUnit configuration is moved from testing-framework into core for more flexibility when adaptions are required. The testing is revamped to use karma-rollup-preprocessor instead of karma-requirejs in order to support the newly compiled ES6 modules. TypeScript Exports and Imports ------------------------------ All export and import definitions have been auto-converted from AMD pseudo import/exports to native ES6 import/exports. Executed commands: find Build/Sources/TypeScript/ -name '*.ts' -exec sed -i \ -e 's/export =/export default/' \ -e 's/ = require(\(.*\))/ from \1/g' \ -e "s/^import 'tablesort';/import Tablesort from 'tablesort';/" \ '{}' + Note that the switch from `export =` to `export default` is not considered breaking because the require-adapter in requirejs-loader wil transparently resolve the .default in moduls. This is possible because AMD modules could not use `export =` and `export {}` (for named exports) at the same time. Explicitly use RequireJS for CodeMirror and ext:form for now ------------------------------------------------------------ CodeMirror can't be easily transformed to ES6 right now, therefore this patch explicitly configures to use the global RequireJS instance. The ext:form JavaScript is currently not written in TypeScript and will therefore not be automatically transformed from AND to ES6 when updating tsconfig.json to emit ES6 modules. Therefore requirejs is uses. This partially reverts #96326 which changed some require() calls to import() syntax too early. New npm dependencies: --------------------- # For module-postprocessing in Gruntfile # This is the same parser as used for the # frontend polyfill es-module-shims yarn add --dev es-module-lexer # A rollup bundle for unit testing in karma is created # usin a karma preprocessor yarn remove karma-requirejs yarn add --dev karma-rollup-preprocessor rollup-plugin-glob-import # Update grunt-terser to support es2020 syntax # (uses terser v5 which we already depended on, but grunt v1 # used the older v4 version) yarn add --dev grunt-terser@^2.0.0 Releases: main Resolves: #96511 Related: #96510 Related: #96323 Change-Id: Id1a6d414c1e9b2e39227d0b6ce9e79333a372349 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72637 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 19 Jan, 2022 1 commit
-
-
We're not actively testing Microsoft SQL Server anymore. The functional test related group annotation not-mssql can be removed, along with the docker container setup. Resolves: #96591 Releases: main Change-Id: Ida5ce97fbab3c19e7e7a0b2548b03fa758f48bb0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73069 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 17 Jan, 2022 1 commit
-
-
Christian Kuhn authored
The created reports.xml when running acceptance tests is used for nothing in CI and just uploaded as artifact along with the other reports. When ac tests fail, the generally useful file is reports.html together with the screenshots. Creating the xml file is skipped now. Users who still want to create the xml file when running the acceptanc test suite can do so by adding the "extra" argument to runTests.sh: > Build/Scripts/runTests.sh -s acceptance -e '--xml reports.xml' Resolves: #96557 Releases: main, 11.5, 10.4 Change-Id: Ic385e307bb48702bc9269e42960fc76f1aa0be41 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73039 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 15 Dec, 2021 1 commit
-
-
Add support for sqlite acceptance testing to 'Build/Scripts/runTests.sh'. Run acceptance/sqlite testing with PHP 8.1 in nightly as a first execution implementation, which could be reshuffled when minimum PHP requirements have been decided. Furthermore two acceptance tests are marked as skipped when executed with sqlite, which should be fixed in dedicated patches: * MaintenanceCest.php->analyzeDatabaseStructureWorks() Skipped, as database compare is never clean and ends in endless loop with sqlite, when ext:indexed_search is installed. This is a general issue, existing at least since v10.4. Needs investigation and a dedicated patch. * UpgradeCest.php->seeUpgradeWizard() Skipped, as utf-8 charset upgrade wizard is not visible for sqlite dbms backend, thus rendering this test obsolete with sqlite. Needs another update wizard test and possibly a dedicated patch. Resolves: #96340 Releases: main Change-Id: I74c8f1156d98a5419309e110ed761e3de21fa37a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72446 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 06 Dec, 2021 1 commit
-
-
Christian Kuhn authored
The patch changes runTests.sh and the container definition to avoid mounting users home, /etc/passwd and /etc/group. yarn based setups need some special treatment but in the end bow to shell power, too. Change-Id: I4e5665d31c5bef4e046e992eddd534ae597cce31 Resolves: #96253 Releases: main, 11.5, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72487 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 03 Dec, 2021 1 commit
-
-
Add versions to repo instead of exposing the root version as env var, when composer installing on CI. This has the benefit, that these versions can be automatically changed by darth (https://github.com/TYPO3/darth/pull/18/commits/083016b43a6ab5860b5a680cbab7d25a890ea0b6) and that all installs, even the ones where the env vars are not exposed, use consistent versions. Releases: main Resolves: #96102 Change-Id: Ic0f3d77fe21f47b1d3b09041800018885bfb4409 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72406 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 30 Nov, 2021 2 commits
-
-
Christian Kuhn authored
Build/Scripts/runTests.sh -s composerTestDistribution needs COMPOSER_ROOT_VERSION set in CI. Change-Id: I42fca3da99f6d92d15714f0966c0c81449eec236 Resolves: #96102 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72405 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Since branching is finished, the dev-master alias is obsolete and can be removed. Used composer command: > composer up --lock Releases: main Resolves: #96102 Change-Id: I3ef3f546bb705b2fda4040b6cb8092b46bde76a9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72379 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org>
-
- 17 Nov, 2021 1 commit
-
-
docker on mac and windows WSL2 encapsulate a VM into the system. The current xdebug remote config does not work in those cases since the host IP can not be determined with the current solution. Switching to host.docker.internal works for macOS and WSL2, and works for linux too in combination with an extra_hosts setting. This requires linux to use at least docker 20.10, which shouldn't be a huge issue with casual developer machines. Resolves: #95999 Resolves: #94932 Releases: master, 10.4 Change-Id: I02acfeefc08f338841b4fecdb952c7da37ff65e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72194 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 09 Nov, 2021 1 commit
-
-
Christian Kuhn authored
Latest 3.141 again leads to trouble with timeout exceptions. 4.0 seems to behave better ... let's raise again to see if that improves the situation. Change-Id: If04b85cf544c1f95d0d65bc95657d5dbf852dacc Resolves: #95920 Related: #95883 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72094 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 08 Nov, 2021 1 commit
-
-
Resolves: #95883 Releases: master Change-Id: I54cf7f2e0c8e968d8f29151b1621b54357681ab2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72062 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 15 Oct, 2021 1 commit
-
-
Christian Kuhn authored
With functional tests now failing on warnings and notices and *showing* deprecations, the next step is to make sure the functional test suite does not trigger deprecated code anymore. The strategy is similar to "UnitDeprecated": All functional tests that actively test deprecated code are moved to a dedicated test suite that *does not* fail on deprecations, while the main functional test suite *does* fail on deprecations. This helps to ensure core code does not call deprecated functionality. The patch: * Adds a FunctionalDeprecated test suite as new home for tests that test deprecated subjects like the deprecated extbase ObjectManager. * Moves and splits existing tests to FunctionalDeprecated, including fixtures as needed. * Adds the test suite to runTests.sh and adapts the docker setup accordingly. * Adds FunctionalDeprecated suite to gitlab-ci pre-merge and nightly in various php / dbms combinations. * Enables convertDeprecationsToExceptions="true" for the main functional test suite and "false" for the new FunctionalDeprecated suite. Change-Id: I74559efc5a3f95d105e3979669a7fda7f13c931a Resolves: #95668 Related: #95659 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71832 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 11 Sep, 2021 1 commit
-
-
Christian Kuhn authored
We're delivering a "test distribution" composer.json in Build/composer since #94996. The patch adds "runTests.sh -s composerTestDistribution" that "composer update" this project and adds it to pre-merge and nightly integrity suite. This verifies core dependencies are fine at all times. Main difference to the monorepo: This composer setup has no dev dependencies that influence version decisions. Resolves: #95188 Related: #94996 Releases: master Change-Id: I04084a2a44a69903d523b5c4740d62d7dc46c1f1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71030 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 29 Aug, 2021 1 commit
-
-
This minor version raise brings significant performance improvements for functional tests, especially with mysql/mariadb & sqlite. composer req --dev typo3/testing-framework:^6.10.0 Change-Id: I09f8a673f55710b8d237faa280121853dcabc378 Resolves: #95028 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70806 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 25 Aug, 2021 1 commit
-
-
Now that we have frontend tests in the Backend suite the name Backend for acceptance suite does not fit anymore. So the suite name was changed from Backend to Application. Resolves: #94864 Releases: master Change-Id: Ib52053f6dbbfad9b7fef1ff11e81110cffa010b2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70550 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 13 Aug, 2021 1 commit
-
-
Test methods are not allowed to have a prefix "test". Use the annotation "@test" in phpDoc instead. Integration into pre-merge and nightly gitlab-ci suites. Note we now have multiple tests based on nikic/php-parser. Those should be rewritten to use one parser instance with multiple visitors to scan php code only once. The exception code checker should be rewritten to use the parser, too. This will be done with a dedicated patch. Resolves: #94859 Releases: master Change-Id: I43ba692eaf2a342a2e0ed3d8978386ea5719183f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70524 Tested-by:
waldhacker <hello@waldhacker.dev> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
waldhacker <hello@waldhacker.dev> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 06 Aug, 2021 2 commits
-
-
Christian Kuhn authored
We have the annotationChecker and the ever growing phpstan ruleset that scan our codebase for code and documentation code block violations. For the additional script docBlockChecker.php it's unclear what it actually does and when it should fail. It never went red to my knowledge. The patch author didn't know what was going on and I've been unable to make the script fail with local tests. The mentioned phpdocumentor/phpdocumentor seems to have never materialized in our world, and tools like api.typo3.org rely on doxygen. The patch drops that integrity test script and removes usages in runTests.sh and gitlab-ci. Resolves: #94735 Related: #89023 Releases: master Change-Id: Id7744780cd50e2009d59bd0f040799f8081924e7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70277 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Christian Kuhn authored
typo3/testing-framework ships default .xml and bootstrap files for phpunit unit and functional tests. They are however quite hard to maintain since the testing-framework supports multiple core versions at once, but core occassionally needs version specific settings. The patch copies the files from the testing-framework to Build/phpunit and adapts core usages. The files within testing-framework will be kept, but will receive an additional "these are boilerplates, consider copying them to your extension" hint for extension developers. The local .xml files are now: * Compatible with phpunit 9 * Let tests fail if phpunit marks a test with warning. With this enabled, we would have seen the issues fixed with #94724 and #94723 with initial #94706 already. Good to do that now. Resolves: #94725 Related: #94706 Related: #94723 Related: #94724 Releases: master Change-Id: I9fef75a972759d26d4e0e3286142cacf181c33d2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70239 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 05 Aug, 2021 1 commit
-
-
Christian Kuhn authored
Acceptance test docker image selenium/standalone-chrome:3.141 is re-tagged upstream to latest releases. Latest release 3.141.59-20210729 tagged as 3.141 has issues as shown by styleguide recently. To not run into this within core tests, the patch pins previous version 3.141.59-20210713 for now. Resolves: #94712 Releases: master Change-Id: I90f7e548c9a1a38616452ae29e566a9ae33c9fc3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70198 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 22 Jul, 2021 1 commit
-
-
docker-compose.yml is now working with v2.0.0beta. Restored old behavior to retrieve the actual CORE_ROOT path using "realpath" which also works on MacOS. Resolves: #94612 Releases: master, 10.4, 9.5 Change-Id: I62ab40870e285b3533a259105dac241e3c4a6af2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70023 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 25 May, 2021 1 commit
-
-
Resolves: #94189 Releases: master, 10.4 Change-Id: Idd70dda6b26c4e6462b351d61ac03e76b7fd9533 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69256 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 04 May, 2021 1 commit
-
-
Benni Mack authored
This change raises the dev dependency PHP-CS-Fixer to 2.19 (forward-compatible to 3.0) and 3.0, allowing to run PHP-CS-Fixer with PHP8. This change adapts the config file to use the latest syntax. Using PSR-12 will be handled in a separate followup. Used composer commands: - composer req friendsofphp/php-cs-fixer:"^2.19 || ^3.0" --dev - composer req friendsofphp/php-cs-fixer:"^2.19 || ^3.0" -d typo3/sysext/core --dev --no-update Resolves: #94053 Releases: master, 10.4 Change-Id: I47d4ca1b09728599782883fb4958908446fd7cfe Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68989 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 24 Mar, 2021 1 commit
-
-
Georg Ringer authored
Update all XLIFF files to use version 1.2, which makes it possible to use a validation schema. Also drop the TYPO3-specific XLIFF file IDs (together with the reference to the corresponding XML namespace) as those are not needed anymore, but prevented XML validation. Also drop checking the XLIFF file IDs from the CI jobs as this does not make sense anymore now. This change does not fix the discovered validation errors in the XLIFF files. This will come later in a separate change. Resolves: #93594 Releases: master, 10.4 Change-Id: I1f263b0a5a7f170e90a906d7992d7bbf08503f7d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68169 Tested-by:
core-ci <typo3@b13.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 14 Mar, 2021 1 commit
-
-
Honor -x option for acceptance tests: Both 'Tester' and 'System under test' allow break points with -s acceptance and -s install. Resolves: #93734 Releases: master Change-Id: Ia3f5a518089be675e33ddc673ebd4c99b2dbfaf6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68380 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 12 Mar, 2021 1 commit
-
-
Allow a call like Build/Scripts/runTests.sh -s phpstan typo3/sysext/linkvalidator Change-Id: Ic7bdc943ab203b34b8710bf95468b9335c6e31ae Resolves: #93710 Release: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68357 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 01 Mar, 2021 2 commits
-
-
The acceptance test suite for the stand alone install tool can easily coexist with the other backend related tests, there is no good reason for the overhead of a separate suite. So it gets merged into the backend suite. Resolves: #93621 Releases: master, 10.4 Change-Id: I460596985cd992c4f7d59df989c7992590e479d8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68158 Tested-by:
core-ci <typo3@b13.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Richard Haeser <richard@richardhaeser.com>
-
The Pagetree suite for acceptance tests was set up as a separate suite in the beginning due to a necessary fixture set of pages, that all the other tests don't need. The overhead of having separate suite is higher than the additional fixture set, so the suites are merged. Resolves: #93614 Releases: master, 10.4 Change-Id: I70a3f1dd68bb07c0dc505eaadb3d240e81639add Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68151 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Richard Haeser <richard@richardhaeser.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 27 Feb, 2021 1 commit
-
-
Christian Kuhn authored
Adapt testing related docker-compose.yml to properly work with xdebug 3.0. This is packaged in the testing container images already and is the only version compatible with PHP 8. To spice up developers life, xdebug 3.0 drops important config options in a non b/w compatible way, introduces new ones, where some of them overwrite others, and does further stuff like changing the default step debugger port for no apparent reason. Since xdebug can be such a pain, runTests.sh comes with -x option, so it (hopefully) 'just works' for devs using the script in testing context. The setup of course breaks with xdebug 3.0 and is fixed with the patch. As single advantage, it is now easier to disable xdebug, so the 'prepared php.ini file without xdebug' hack in the test container images can be dropped. Change-Id: Id5810a5a6d988bfe5e814a6781d12d93baa97972 Resolves: #93599 Releases: master, 10.4, 9.5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68137 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 24 Feb, 2021 2 commits
-
-
The acceptance and functional test splitter scripts from typo3/testing-framework are tailored for core specific needs and of rather little use for non-core. For the sake of a more clean typo3/testing-framework, the patch merges the scripts into core mono-repo. Change-Id: Iefb576bb52c238ccca7b618fa6f9ea0d5718d0f9 Resolves: #93586 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68098 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
This brings a recent chrome version. Some tests need minor adaptions to deal with changed exceptions and behaviour. Change-Id: I1644a90ee09c98721ad8246988709461248c66a4 Resolves: #93575 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67964 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Richard Haeser <richard@richardhaeser.com>
-
- 17 Feb, 2021 1 commit
-
-
All exception codes of the current TYPO3 version can be output to stdout without checking for missing and duplicate exception codes. Therefore, the patch adds the `-p` option to the duplicateExceptionCodeCheck.sh: Build/Scripts/duplicateExceptionCodeCheck.sh -p It is also added to runTests.sh: Build/Scripts/runTests.sh -s listExceptionCodes Resolves: #93499 Releases: master, 10.4, 9.5 Change-Id: I088d53bfbd8b5255b6516de3f546f3f914871ee1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67913 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 15 Feb, 2021 2 commits
-
-
Check for user in /etc/passwd, if it does not exist create a temporary passwd to get values from. Resolves: #93372 Releases: master, 10.4, 9.5 Change-Id: I60c9d2a10a0da155354546d57c823961bc39f014 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67539 Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Plus: No variable fallback magick in docker-compose.yml, this belongs to runTests.sh Change-Id: I9ec8d1ecba695061155807fd44d0a3cb3f342cfd Resolves: #93514 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67919 Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Richard Haeser <richard@richardhaeser.com>
-
- 01 Feb, 2021 1 commit
-
-
Christian Kuhn authored
Allow mysql & postgres for acceptance tests in addition to default mariadb: * Build/Script/runTests.sh -s acceptance -d mysql * Build/Script/runTests.sh -s acceptance -d postgres Change-Id: If65f1d8d8b4443107d655948ce87af4390d9681f Resolves: #93405 Releases: master, 10.4, 9.5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67623 Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-