test(integration): add more tags, complete embed feature tests suite, fix order with metadata

test/integration/features/chromium_convert_markdown.feature

@@ -1,6 +1,8 @@
 # TODO:
 # 1. JavaScript disabled on some feature.
 
+@chromium
+@chromium-convert-markdown
 Feature: /forms/chromium/convert/markdown
 
   Scenario: POST /forms/chromium/convert/markdown (Default)
@@ -648,6 +650,7 @@ Feature: /forms/chromium/convert/markdown
       Invalid form data: form field 'metadata' is invalid (got 'foo', resulting to unmarshal metadata: invalid character 'o' in literal false (expecting 'a'))
       """
 
+  @split
   Scenario: POST /forms/chromium/convert/markdown (Split Intervals)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -679,6 +682,8 @@ Feature: /forms/chromium/convert/markdown
       """
 
   # See https://github.com/gotenberg/gotenberg/issues/1130.
+  @split
+  @output-filename
   Scenario: POST /forms/chromium/convert/markdown (Split Output Filename)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -711,6 +716,7 @@ Feature: /forms/chromium/convert/markdown
       Page 3
       """
 
+  @split
   Scenario: POST /forms/chromium/convert/markdown (Split Pages)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -737,6 +743,7 @@ Feature: /forms/chromium/convert/markdown
       Page 3
       """
 
+  @split
   Scenario: POST /forms/chromium/convert/markdown (Split Pages & Unify)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -763,6 +770,7 @@ Feature: /forms/chromium/convert/markdown
       Page 3
       """
 
+  @split
   Scenario: POST /forms/chromium/convert/markdown (Split Many PDFs - Lot of Pages)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -808,6 +816,7 @@ Feature: /forms/chromium/convert/markdown
       Page 12
       """
 
+  @convert
   Scenario: POST /forms/chromium/convert/markdown (PDF/A-1b & PDF/UA-1)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -821,6 +830,8 @@ Feature: /forms/chromium/convert/markdown
     Then the response PDF(s) should be valid "PDF/A-1b" with a tolerance of 1 failed rule(s)
     Then the response PDF(s) should be valid "PDF/UA-1" with a tolerance of 3 failed rule(s)
 
+  @convert
+  @split
   Scenario: POST /forms/chromium/convert/markdown (Split & PDF/A-1b & PDF/UA-1)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -856,6 +867,9 @@ Feature: /forms/chromium/convert/markdown
     Then the response PDF(s) should be valid "PDF/UA-1" with a tolerance of 3 failed rule(s)
 
   # See https://github.com/gotenberg/gotenberg/issues/1130.
+  @convert
+  @split
+  @output-filename
   Scenario: POST /forms/chromium/convert/markdown (Split & PDF/A-1b & PDF/UA-1 & Output Filename)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -892,6 +906,7 @@ Feature: /forms/chromium/convert/markdown
     Then the response PDF(s) should be valid "PDF/A-1b" with a tolerance of 1 failed rule(s)
     Then the response PDF(s) should be valid "PDF/UA-1" with a tolerance of 3 failed rule(s)
 
+  @metadata
   Scenario: POST /forms/chromium/convert/markdown (Metadata)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -928,6 +943,7 @@ Feature: /forms/chromium/convert/markdown
       }
       """
 
+  @flatten
   Scenario: POST /forms/chromium/convert/markdown (Flatten)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -939,6 +955,7 @@ Feature: /forms/chromium/convert/markdown
     Then there should be 1 PDF(s) in the response
     Then the response PDF(s) should be flatten
 
+  @encrypt
   Scenario: POST /forms/chromium/convert/markdown (Encrypt - user password only)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -950,6 +967,7 @@ Feature: /forms/chromium/convert/markdown
     Then there should be 1 PDF(s) in the response
     Then the response PDF(s) should be encrypted
 
+  @encrypt
   Scenario: POST /forms/chromium/convert/markdown (Encrypt - both user and owner passwords)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
@@ -962,8 +980,29 @@ Feature: /forms/chromium/convert/markdown
     Then there should be 1 PDF(s) in the response
     Then the response PDF(s) should be encrypted
 
+  @embed
+  Scenario: POST /forms/chromium/convert/markdown (Embeds)
+    Given I have a default Gotenberg container
+    When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
+      | files                     | testdata/page-1-markdown/index.html | file   |
+      | files                     | testdata/page-1-markdown/page_1.md  | file   |
+      | embeds                    | testdata/embed_1.xml                | file   |
+      | embeds                    | testdata/embed_2.xml                | file   |
+      | Gotenberg-Output-Filename | foo                                 | header |
+    Then the response status code should be 200
+    Then the response header "Content-Type" should be "application/pdf"
+    Then there should be 1 PDF(s) in the response
+    Then there should be the following file(s) in the response:
+      | foo.pdf |
+    Then the response PDF(s) should have the "embed_1.xml" file embedded
+    Then the response PDF(s) should have the "embed_2.xml" file embedded
+
   # FIXME: once decrypt is done, add encrypt and check after the content of the PDF.
-  Scenario: POST /forms/chromium/convert/markdown (PDF/A-1b & PDF/UA-1 & Metadata & Flatten)
+  @convert
+  @metadata
+  @flatten
+  @embed
+  Scenario: POST /forms/chromium/convert/markdown (PDF/A-1b & PDF/UA-1 & Metadata & Flatten & Embeds)
     Given I have a default Gotenberg container
     When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
       | files                     | testdata/page-1-markdown/index.html                                                                                                                                                                                                                                                                       | file   |
@@ -972,15 +1011,19 @@ Feature: /forms/chromium/convert/markdown
       | pdfua                     | true                                                                                                                                                                                                                                                                                                      | field  |
       | metadata                  | {"Author":"Julien Neuhart","Copyright":"Julien Neuhart","CreateDate":"2006-09-18T16:27:50-04:00","Creator":"Gotenberg","Keywords":["first","second"],"Marked":true,"ModDate":"2006-09-18T16:27:50-04:00","PDFVersion":1.7,"Producer":"Gotenberg","Subject":"Sample","Title":"Sample","Trapped":"Unknown"} | field  |
       | flatten                   | true                                                                                                                                                                                                                                                                                                      | field  |
+      | embeds                    | testdata/embed_1.xml                                                                                                                                                                                                                                                                                      | file   |
+      | embeds                    | testdata/embed_2.xml                                                                                                                                                                                                                                                                                      | file   |
       | Gotenberg-Output-Filename | foo                                                                                                                                                                                                                                                                                                       | header |
     Then the response status code should be 200
     Then the response header "Content-Type" should be "application/pdf"
     Then there should be 1 PDF(s) in the response
     Then there should be the following file(s) in the response:
       | foo.pdf |
-    Then the response PDF(s) should be valid "PDF/A-1b" with a tolerance of 7 failed rule(s)
+    Then the response PDF(s) should be valid "PDF/A-1b" with a tolerance of 9 failed rule(s)
     Then the response PDF(s) should be valid "PDF/UA-1" with a tolerance of 2 failed rule(s)
     Then the response PDF(s) should be flatten
+    Then the response PDF(s) should have the "embed_1.xml" file embedded
+    Then the response PDF(s) should have the "embed_2.xml" file embedded
     When I make a "POST" request to Gotenberg at the "/forms/pdfengines/metadata/read" endpoint with the following form data and header(s):
       | files | teststore/foo.pdf | file |
     Then the response status code should be 200
@@ -1025,6 +1068,7 @@ Feature: /forms/chromium/convert/markdown
     Then the Gotenberg container should log the following entries:
       | "trace":"forms_chromium_convert_html" |
 
+  @download-from
   Scenario: POST /forms/chromium/convert/markdown (Download From)
     Given I have a default Gotenberg container
     Given I have a static server
@@ -1035,6 +1079,7 @@ Feature: /forms/chromium/convert/markdown
     Then the file request header "X-Foo" should be "bar"
     Then the response header "Content-Type" should be "application/pdf"
 
+  @webhook
   Scenario: POST /forms/chromium/convert/markdown (Webhook)
     Given I have a default Gotenberg container
     Given I have a webhook server
@@ -1075,20 +1120,3 @@ Feature: /forms/chromium/convert/markdown
       | files | testdata/page-1-markdown/page_1.md  | file |
     Then the response status code should be 200
     Then the response header "Content-Type" should be "application/pdf"
-
-  @embed
-  Scenario: POST /forms/chromium/convert/markdown (Embeds)
-    Given I have a default Gotenberg container
-    When I make a "POST" request to Gotenberg at the "/forms/chromium/convert/markdown" endpoint with the following form data and header(s):
-      | files                     | testdata/page-1-markdown/index.html | file   |
-      | files                     | testdata/page-1-markdown/page_1.md  | file   |
-      | embeds                    | testdata/embed_1.xml                | file   |
-      | embeds                    | testdata/embed_2.xml                | file   |
-      | Gotenberg-Output-Filename | foo                                 | header |
-    Then the response status code should be 200
-    And the response header "Content-Type" should be "application/pdf"
-    And there should be 1 PDF(s) in the response
-    And there should be the following file(s) in the response:
-      | foo.pdf |
-    And the "foo.pdf" PDF should have the "embed_1.xml" file embedded in it
-    And the "foo.pdf" PDF should have the "embed_2.xml" file embedded in it