[WIP][TASK] Refactor tests #470
Draft
+58
−147
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The tests used a php mocking system, which did not respect the TYPO3 configurations for HTTP and used the functionality of cURL requests instead of the TYPO3 RequestFactory, which respects all settings. This has bad impacts on testing, in special for proxy and building correct requests against the DeepL API. Therefore, the AbstractDeepLTestCase is refactored using proper TYPO3 configuration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tests used a php mocking system, which did not respect the TYPO3 configurations for HTTP and used the functionality of cURL requests instead of the TYPO3 RequestFactory, which respects all settings.
This has bad impacts on testing, in special for proxy and building correct requests against the DeepL API. Therefore, the AbstractDeepLTestCase is refactored using proper TYPO3 configuration.