Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Remove functional test database configuration fallback #538

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

sbuerk
Copy link
Collaborator

@sbuerk sbuerk commented Jan 31, 2024

Functional tests per nature speaks with a concrete database service,
which can be configured using a et of environment variables.
However, historically a fallback to typo3conf/LocalConfiguration.php
or the root project has been used if no environment variable has been
provided.

This broke already in early TYPO3 v12 development cycle with the
move towards configuration files outside of the public root folder
in a composer based installation.

Because of today usage of the testing-framework and the broader
acceptance of ci/cd pipelines the environment variables are the
recommended configuration option. Remove the broken fallback now.

Resolves: #474
Releases: main

Functional tests per nature speaks with a concrete database service,
which can be configured using a et of `environment variables`.
However, historically a fallback to `typo3conf/LocalConfiguration.php`
or the root project has been used if no environment variable has been
provided.

This broke already in early TYPO3 v12 development cycle with the
move towards configuration files outside of the public root folder
in a composer based installation.

Because of today usage of the testing-framework and the broader
acceptance of ci/cd pipelines the environment variables are the
recommended configuration option. Remove the broken fallback now.

Resolves: #474
Releases: main
@sbuerk sbuerk changed the title [!!!][TASK] Remove functional test database configuration fallback [TASK] Remove functional test database configuration fallback Jan 31, 2024
@sbuerk sbuerk merged commit 7f4a539 into main Jan 31, 2024
4 checks passed
@sbuerk sbuerk deleted the issue-474 branch January 31, 2024 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Decide what to do with outdated configuration path
2 participants