Exclude specific features for Redmine 4.2

Author: Art4

README.md

@@ -35,7 +35,7 @@ that receive security updates.
 - Redmine 4.2.x
 
 Nevertheless, you can also use this library for all older Redmine versions.
-In this case, however, be aware that some features may not yet be supported by your Redmine server.
+In this case, however, be aware that some features might not be supported by your Redmine server.
 
 If a new Redmine version enables new features that are not yet supported with this library,
 you are welcome to [create an issue](https://github.com/kbsali/php-redmine-api/issues).

tests/Behat/README.md

@@ -0,0 +1,90 @@
+# Behaviour tests
+
+This folder contains BDD tests using Docker and Behat.
+
+## How to run the tests
+
+Pull the Redmine docker images and start them by running:
+
+```bash
+docker compose up -d
+```
+
+Now you can run the tests:
+
+```bash
+docker compose exec php composer behat
+```
+
+## Redmine specific features
+
+Some Redmine features are specific for a Redmine version. There are two ways to handle this situations.
+
+### Modified Rest-API Responses
+
+It is possible that a new Redmine version returns new or changed elements in a response.
+This can be handled on the `step` layer:
+
+```
+        And the returned data "projects.0" property has only the following properties with Redmine version ">= 5.1.0"
+            """
+            id
+            name
+            identifier
+            description
+            homepage
+            status
+            is_public
+            inherit_members
+            created_on
+            updated_on
+            """
+        But the returned data "projects.0" property has only the following properties with Redmine version "< 5.1.0"
+            """
+            id
+            name
+            identifier
+            description
+            status
+            is_public
+            inherit_members
+            created_on
+            updated_on
+            """
+```
+
+### Modified Rest-API Endpoints
+
+A new Redmine version could be introduce new REST-API endpoints that are missing in the older version.
+This can be handled on the `scenario` or `feature` layer.
+
+1. Tag features or scenarios e.g. with `@since50000`.
+
+```
+@since50000
+Feature: Interacting with the new REST API endpoint
+    [...]
+```
+
+or
+
+```
+    @since50000
+    Scenario: Using a new feature
+        Given I have a "NativeCurlClient" client
+        And I create a project with name "Test Project" and identifier "test-project"
+        [...]
+```
+
+2. Exclude the tag from the specific suite in the `behat.yml` (note the `~` prefix):
+
+```
+default:
+    suites:
+        [...]
+        redmine_40210:
+            [...]
+            filters:
+                tags: "~@since50000"
+
+```

tests/Behat/behat.yml

@@ -18,3 +18,5 @@ default:
             contexts:
                 - Redmine\Tests\Behat\Bootstrap\FeatureContext:
                     redmineVersion: '4.2.10'
+            filters:
+                tags: "~@since50000"

tests/Behat/features/projects.feature

@@ -167,7 +167,7 @@ Feature: Interacting with the REST API for projects
         And the response has the content ""
         And the returned data is exactly ""
 
-    @project
+    @project @since50000
     Scenario: Closing a project
         Given I have a "NativeCurlClient" client
         And I create a project with name "Test Project" and identifier "test-project"
@@ -181,7 +181,7 @@ Feature: Interacting with the REST API for projects
             | property          | value                |
             | status            | 5                    |
 
-    @project
+    @project @since50000
     Scenario: Reopening a project
         Given I have a "NativeCurlClient" client
         And I create a project with name "Test Project" and identifier "test-project"
@@ -196,7 +196,7 @@ Feature: Interacting with the REST API for projects
             | property          | value                |
             | status            | 1                    |
 
-    @project
+    @project @since50000
     Scenario: Archiving a project
         Given I have a "NativeCurlClient" client
         And I create a project with name "Test Project" and identifier "test-project"
@@ -206,7 +206,7 @@ Feature: Interacting with the REST API for projects
         And the response has the content ""
         And the returned data is true
 
-    @project @error
+    @project @since50000 @error
     Scenario: Showing an archived project is not possible
         Given I have a "NativeCurlClient" client
         And I create a project with name "Test Project" and identifier "test-project"
@@ -217,7 +217,7 @@ Feature: Interacting with the REST API for projects
         And the response has the content ""
         And the returned data is false
 
-    @project
+    @project @since50000
     Scenario: Unarchiving a project
         Given I have a "NativeCurlClient" client
         And I create a project with name "Test Project" and identifier "test-project"