- Issue created by @catch
- 🇧🇪Belgium kristiaanvandeneynde Antwerp, Belgium
If we start moving more tests to the Umami tests, we might lose track of what the performance of a "clean" Drupal is. Would it make sense to have the same tests run where one is using "demo_umami" and the other is using "standard"? Then with any change to core we can see how it improves performance on a very minimalistic site vs a very realistic one.
- 🇬🇧United Kingdom catch
Given the install profile is a property on the test class it'd probably be easier to duplicate the coverage (or add an extra trait with the test methods), but we can definitely do that and agree it's good to test both cases at least for things that are different. Reminds me we need to add query/cache assertions to all the Umami performance tests now that counts are stabilised etc.
- 🇧🇪Belgium kristiaanvandeneynde Antwerp, Belgium
Reminds me we need to add query/cache assertions to all the Umami performance tests now that counts are stabilised etc.
I think I did the query part already for those tests that were previously checking query counts.
