Testing Framework Extraction - Next Steps - Result


There was little feedback in the discussion of the testing framework, therefor I’ll just put the voting together. You can read up on the full discussion on Testing Framework Extraction - Next Steps - Discuss Topics - TYPO3 Decisions


Keep basic files like UnitTests.xml or Bootstrap.js in the testing framework as living examples.

  • Yes
  • No
0 voters

Introduce src/res folder to distinguish code and resources as:

Discussion result:

  • will only be used in TYPO3 Context
  • rest of the world uses res/src
  • src/res would be in line with rest of the world
  • Classes/Resources would be in line with TYPO3 general naming conventions
  • src/res
  • Classes/Resources
0 voters

Remove the CMS part from the namespace:

Current namespace is: TYPO3/CMS/Components/TestingFramework
Proposed namespace is: TYPO3/Components/TestingFramework

  • change namespace and drop CMS
  • leave namespace as it is
0 voters

Subtree split: One-time split and later maintenance on github or split for every release and maintain as part of the core?

  • Moving to github would make work on this part as separate package easier and more independent from the rest of the core
  • If we have changes spanning the testing framework and the core we’d need to change it in two repositories
  • Subtree split once and maintain as separate package
  • Regularly split before a release but maintain as part of the core
0 voters

Release as composer only package or as composer package and TYPO3 extension

  • composer only would teach/force people to use composer for testing
  • composer only
  • composer package and TYPO3 extension
0 voters

This topic was automatically closed after 7 days. New replies are no longer allowed.