Uploaded image for project: 'eZ Platform Enterprise Edition'
  1. eZ Platform Enterprise Edition
  2. EZEE-3466

Loading Features hardcoded in test

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • 3.2.4, 3.3.0-rc2
    • Installation
    • None
    • APP_ENV=test

    Description

      After the installation of Ibexa, we can configure some other environments.

       

      We can see in that file https://github.com/ezsystems/ezplatform-kernel/blob/master/eZ/Bundle/EzPublishCoreBundle/DependencyInjection/EzPublishCoreExtension.php that features_context.yml is loaded if the environment is either behat or test.

       

      This would be better if that behavior was not automatically added to test environement as it can be used without behat.

       

      I guess the same applies to this file also : vendor/ezsystems/ezplatform-content-forms/src/bundle/DependencyInjection/EzPlatformContentFormsExtension.php

       

      I've seen in many other places that the code does not do an in_array check but a simple if env = 'behat'. It could be applied to these 2 files also.

      Attachments

        Activity

          People

            Unassigned Unassigned
            8bc12bd8-4b86-4b97-8f96-13978c04c7fa@accounts.ibexa.co Jérémy Poulain
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: