title: How to run tests for a specific suite from included module configurations?
body: <p>I have a codeception.yml on my projects root folder.
  This has an include config directive to other codeception yml for my different modules</p>
  
  <pre><code>include:
      - tests/Modules/*
  </code></pre>
  
  <p>This is described here in the codeception doc as a multiple application setup</p>
  
  <p><a href="https://codeception.com/docs/08-Customization#One-Runner-for-Multiple-Applications" rel="nofollow noreferrer">https://codeception.com/docs/08-Customization#One-Runner-for-Multiple-Applications</a></p>
  
  <p>These sub-configs have different suite configs described in their own codeception.yml like this one in </p>
  
  <blockquote>
    <p>tests/Modules/Frontend/codeception.yml</p>
  </blockquote>
  
  <pre><code>suites:
      Presentation:
          path: Presentation
          class_name: PresentationTester
          modules:
  ...
  </code></pre>
  
  <p>The problem: In my project root folder i cant run a specific suite for all included modules via </p>
  
  <pre><code>vendor/bin/codecept run Presentation
  </code></pre>
  
  <p>It says </p>
  
  <blockquote>
    <p>Suite 'Presentation' could not be found</p>
  </blockquote>
  
  <p>Running it pointing to a certain config does work</p>
  
  <pre><code>vendor/bin/codecept run Presentation -c tests/Modules/Frontend
  </code></pre>
  
  <p>But it just runs this one module. I want to run certain suites of all modules with one command. </p>
  
  <p>Running a group (-g) does also work, so this indicates that the configs are loaded correctly.</p>
  
  <p>Why does this not work for suites? All configs are included in my main yml, so the suites must be found in my opinion.</p>
  
  <p>Whats the sense of having a setup like this, when no suites can be run from a central point?</p>
  
  <p>Any ideas?</p>