Testing Framework Extraction - Next Steps
As there was quite a lot of discussion around the first step of the testing framework extraction, I wanted to discuss the next steps with you and figure out some of the details together. On my list is currently:
- Clean-up testing framework parts
1.1. Are the right files in the testing framework, are there other files that should be included?
1.2 Files like the UnitTests.xml / Bootstrap.js etc. are currently mainly provided for convenience and as example even though these are mostly for the core - keep those in the testing framework for documentation purposes or move back to the core?
1.3 Introduce src and res folders for distinguishing between code and resource files.
- Namespace - Currently the namespace is TYPO3/CMS/Components/TestingFramework
2.1 Remove the CMS part?
- Subtree split: TestingFramework stays part of the Core Repository and will be split as own package regularly as part of the release process or will be splitted once and moved to an own repository.
- Release as composer package only or as composer package and typo3 extension?
Remarks and notes
I hope I did not forget anything from the many discussions, if so, I’m sorry and feel free to add it here. Looking forward to your opinions.
As the next stab phase draws near, I’ll change the closing date to a bit shorter timeframe, so I can get most of the things done before the release.
Topic Initiator: Susanne Moog