From 9b84a8d24b190592fee99331c1cd9ec135ca899c Mon Sep 17 00:00:00 2001 From: Muhammad Salman <151463017+SalmanDeveloperz@users.noreply.github.com> Date: Sun, 6 Oct 2024 06:28:35 +0500 Subject: [PATCH] Delete Documentation/TestingFramework.rst Just drop this document (and the reference to it) altogether. --- Documentation/TestingFramework.rst | 55 ------------------------------ 1 file changed, 55 deletions(-) delete mode 100644 Documentation/TestingFramework.rst diff --git a/Documentation/TestingFramework.rst b/Documentation/TestingFramework.rst deleted file mode 100644 index ec378f4..0000000 --- a/Documentation/TestingFramework.rst +++ /dev/null @@ -1,55 +0,0 @@ -.. include:: /Includes.rst.txt - -.. _testing-framework: - -================= -Testing framework -================= - -Extensions usually need to support two LTS versions of TYPO3 in parallel, -assuming that they should support all currently supported TYPO3 LTS versions. -To achieve this, there are two different approaches, which also affect the -choice of a testing framework for unit and functional tests. - -.. contents:: Table of Contents: - :backlinks: top - :class: compact-list - :depth: 2 - :local: - -.. _testing-framework-approach-many-versions: - -Approach 1: One branch for many TYPO3 LTS versions -================================================== - -With this approach, there is one main branch that gets new features. It needs to -support two TYPO3 LTS versions in parallel. - -The downside is that this slightly increases code complexity as -version-dependent code switches might be necessary. The upside is that there -is only one branch to maintain, which makes adding new features (and all other -code changes) a lot less of a hassle. - -For this approach, the -`TYPO3 testing framework `__ -- which supports multiple TYPO3 versions at a time - will work just fine. - -This is the approach that we have chosen for this extension as we do not want -to maintain two branches in parallel. - -.. _testing-framework-approach-one-version: - -Approach 2: One branch per TYPO3 LTS version -============================================ - -With this approach, there are two main branches that get new features in -parallel. Each branch supports exactly one TYPO3 LTS version. - -The upside is that this slightly decreases code complexity as -version-dependent code switches are not necessary. The downside is that there -are two branches to maintain, which makes adding new features (and all other -code changes) more of a hassle. - -For this approach, the -`TYPO3 testing framework `__ -- which supports only one TYPO3 LTS version at a time - will work just fine.