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

Bug/Discuss: Clear Flow/Neos cache in @BeforeScenario hook to make behat scenarios isolated from each other #10

Open
erickloss opened this issue Jun 2, 2022 · 3 comments
Labels
bug Something isn't working help wanted Extra attention is needed question Further information is requested

Comments

@erickloss
Copy link
Contributor

Problem:
When executing multiple scenarios in a row that import node data fixtures, the Neos/Fusion cache is not invalidated after rendering a page in a scenario. That makes the scenarios interdependent in some way.

image

Let's discuss if there is a more fancy solution than that. Tests slow down more ofc with a fresh cache.

@erickloss erickloss added bug Something isn't working help wanted Extra attention is needed question Further information is requested labels Jun 2, 2022
@klfman
Copy link

klfman commented Jun 8, 2022

I think that flushing the cache is a good idea. The performance problems could be mitigated a bit by flushing individual caches, for example the fusion cache, if the tests are only about rendering.

@skurfuerst
Copy link
Member

I would not clear the code cache of flow; but it definitely makes sense to clear the fusion content cache :):)

@skurfuerst
Copy link
Member

(not clearing the code cache because it makes the system a lot a lot slower)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants