Document tag and name filter interaction

As noted in cucumber/docs#1023 it is not
documented how tag and name filters interact.

Author: mpkorstanje

cucumber-core/README.md

@@ -37,11 +37,13 @@ cucumber.features=              # comma separated list of feature paths.
                                 # example: path/to/features, classpath:com/example/features, path/to/example.feature:42, @path/to/rerun.txt
   
 cucumber.filter.name=           # a regular expression
-                                # only scenarios with matching names are executed. 
-                                # example: ^Hello (World|Cucumber)$     
+                                # only scenarios with matching names are executed.
+                                # combined with cucumber.filter.tags using "and" semantics. 
+                                # example: ^Hello (World|Cucumber)$
 
 cucumber.filter.tags=           # a cucumber tag expression. 
-                                # only scenarios with matching tags are executed. 
+                                # only scenarios with matching tags are executed.
+                                # combined with cucumber.filter.name using "and" semantics.
                                 # example: @Cucumber and not (@Gherkin or @Zucchini)
 
 cucumber.glue=                  # comma separated package names. 

cucumber-core/src/main/java/io/cucumber/core/options/Constants.java

@@ -88,9 +88,10 @@ public final class Constants {
      * <p>
      * Filters scenarios by name based on the provided regex pattern e.g:
      * {@code ^Hello (World|Cucumber)$}. Scenarios that do not match the
-     * expression are not executed.
+     * expression are not executed. Combined with
+     * {@value FILTER_TAGS_PROPERTY_NAME} using "and" semantics.
      * <p>
-     * By default all scenarios are executed
+     * By default, all scenarios are executed
      */
     public static final String FILTER_NAME_PROPERTY_NAME = "cucumber.filter.name";
 
@@ -99,9 +100,10 @@ public final class Constants {
      * <p>
      * Filters scenarios by tag based on the provided tag expression e.g:
      * {@code @Cucumber and not (@Gherkin or @Zucchini)}. Scenarios that do not
-     * match the expression are not executed.
+     * match the expression are not executed. Combined with
+     * {@value FILTER_NAME_PROPERTY_NAME} using "and" semantics.
      * <p>
-     * By default all scenarios are executed
+     * By default, all scenarios are executed
      */
     public static final String FILTER_TAGS_PROPERTY_NAME = "cucumber.filter.tags";
 

cucumber-core/src/main/resources/io/cucumber/core/options/USAGE.txt

@@ -137,10 +137,12 @@ cucumber.features=              # comma separated paths to feature files.
 
 cucumber.filter.name=           # a regular expression
                                 # only scenarios with matching names are executed.
+                                # combined with cucumber.filter.tags using "and" semantics.
                                 # example: ^Hello (World|Cucumber)$
 
 cucumber.filter.tags=           # a cucumber tag expression.
                                 # only scenarios with matching tags are executed.
+                                # combined with cucumber.filter.name using "and" semantics.
                                 # example: @Cucumber and not (@Gherkin or @Zucchini)
 
 cucumber.glue=                  # comma separated package names.

cucumber-junit-platform-engine/README.md

@@ -331,6 +331,7 @@ cucumber.ansi-colors.disabled=                                 # true or false.
        
 cucumber.filter.name=                                          # a regular expression.
                                                                # only scenarios with matching names are executed.
+                                                               # combined with cucumber.filter.tags using "and" semantics.
                                                                # example: ^Hello (World|Cucumber)$
                                                                # note: To ensure consistent reports between Cucumber and
                                                                # JUnit 5 prefer using JUnit 5s discovery request filters
@@ -349,6 +350,7 @@ cucumber.features=                                             # comma separated
 
 cucumber.filter.tags=                                          # a cucumber tag expression.
                                                                # only scenarios with matching tags are executed.
+                                                               # combined with cucumber.filter.name using "and" semantics.                                                               
                                                                # example: @Cucumber and not (@Gherkin or @Zucchini)
                                                                # note: To ensure consistent reports between Cucumber and
                                                                # JUnit 5 prefer using JUnit 5s discovery request filters