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

Allow configuration to be mocked for behat tests #4423

Closed
bwaidelich opened this issue Jul 28, 2023 · 2 comments
Closed

Allow configuration to be mocked for behat tests #4423

bwaidelich opened this issue Jul 28, 2023 · 2 comments
Assignees
Labels

Comments

@bwaidelich
Copy link
Member

For the routing Behat tests, we already allow to "simulate" custom site configurations.

For CR core tests, we allow custom Node Types to be configured.

Both approaches only work for the current request though.
It should be possible to change configuration for the whole lifecycle though, including sub requests (i.e. projections and catch up hooks)

@bwaidelich
Copy link
Member Author

As discussed in our Neos 9 weekly, for Flow we might be able to actually store *.yaml files in a cache directory (for the current Application context) and make the Configuration Manager read those via Objects.yaml

@bwaidelich bwaidelich moved this from Todo to Prioritized 🔥 in Neos 9.0 Release Board Sep 30, 2023
@ahaeslich ahaeslich moved this from Prioritized 🔥 to Todo in Neos 9.0 Release Board Apr 10, 2024
@bwaidelich
Copy link
Member Author

This will become obsolete with #4746

@github-project-automation github-project-automation bot moved this from Todo to Done ✅ in Neos 9.0 Release Board Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

1 participant