Skip to content

Commit bfbdad3

Browse files
vincentchalamonvincentchalamon
committed
chore: remove @V3 tag from Behat feature files + clean feature files
1 parent 21cdc1f commit bfbdad3

19 files changed

+120
-135
lines changed

‎features/graphql/authorization.feature

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,6 @@ Feature: Authorization checking
152152
And the JSON node "data.securedDummy.relatedDummy" should exist
153153
And the JSON node "data.securedDummy.relatedDummy" should not be null
154154

155-
@v3
156155
@createSchema
157156
Scenario: A user can't access a secured collection relation
158157
Given there are 1 SecuredDummy objects owned by dunglas with related dummies
@@ -176,7 +175,6 @@ Feature: Authorization checking
176175
And the header "Content-Type" should be equal to "application/json"
177176
And the JSON node "data.securedDummy.relatedDummies" should be null
178177

179-
@v3
180178
Scenario: A user can't access a secured relation
181179
When I add "Authorization" header equal to "Basic ZHVuZ2xhczprZXZpbg=="
182180
And I send the following GraphQL request:
@@ -234,7 +232,6 @@ Feature: Authorization checking
234232
And the JSON node "errors[0].message" should be equal to "Access Denied."
235233
And the JSON node "data.relatedSecuredDummies" should be null
236234

237-
@v3
238235
Scenario: A user can access a secured collection relation
239236
When I add "Authorization" header equal to "Basic ZHVuZ2xhczprZXZpbg=="
240237
And I send the following GraphQL request:
@@ -256,7 +253,6 @@ Feature: Authorization checking
256253
And the header "Content-Type" should be equal to "application/json"
257254
And the JSON node "data.securedDummy.relatedSecuredDummies" should have 1 element
258255

259-
@v3
260256
Scenario: A user can access a secured relation
261257
When I add "Authorization" header equal to "Basic ZHVuZ2xhczprZXZpbg=="
262258
And I send the following GraphQL request:
@@ -275,7 +271,6 @@ Feature: Authorization checking
275271
And the JSON node "data.securedDummy.relatedSecuredDummy" should exist
276272
And the JSON node "data.securedDummy.relatedSecuredDummy" should not be null
277273

278-
@v3
279274
Scenario: A user can access a non-secured collection relation
280275
When I add "Authorization" header equal to "Basic ZHVuZ2xhczprZXZpbg=="
281276
And I send the following GraphQL request:
@@ -297,7 +292,6 @@ Feature: Authorization checking
297292
And the header "Content-Type" should be equal to "application/json"
298293
And the JSON node "data.securedDummy.publicRelatedSecuredDummies" should have 1 element
299294

300-
@v3
301295
Scenario: A user can access a non-secured relation
302296
When I add "Authorization" header equal to "Basic ZHVuZ2xhczprZXZpbg=="
303297
When I send the following GraphQL request:
@@ -388,7 +382,6 @@ Feature: Authorization checking
388382
And the response should be in JSON
389383
And the JSON node "data.securedDummies.edges[2].node.ownerOnlyProperty" should be equal to "it works"
390384

391-
@v3
392385
Scenario: An admin can't create a secured resource with an owner-only property if they won't be the owner
393386
When I add "Authorization" header equal to "Basic YWRtaW46a2l0dGVu"
394387
And I send the following GraphQL request:
@@ -472,7 +465,6 @@ Feature: Authorization checking
472465
And the JSON node "data.securedDummy.adminOnlyProperty" should exist
473466
And the JSON node "data.securedDummy.adminOnlyProperty" should not be null
474467

475-
@v3
476468
Scenario: A user can't see a secured admin-only property on an object they own
477469
When I add "Authorization" header equal to "Basic ZHVuZ2xhczprZXZpbg=="
478470
And I send the following GraphQL request:
@@ -535,7 +527,6 @@ Feature: Authorization checking
535527
And the response should be in JSON
536528
And the JSON node "data.securedDummy.ownerOnlyProperty" should be equal to the string "updated"
537529

538-
@v3
539530
Scenario: An admin can't see a secured owner-only property on an object they don't own
540531
When I add "Authorization" header equal to "Basic YWRtaW46a2l0dGVu"
541532
And I send the following GraphQL request:

‎features/graphql/collection.feature

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
Feature: GraphQL collection support
2+
23
@createSchema
34
Scenario: Retrieve a collection through a GraphQL query
45
Given there are 4 dummy objects with relatedDummy and its thirdLevel

‎features/graphql/mutation.feature

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -663,7 +663,6 @@ Feature: GraphQL mutation support
663663
And the JSON node "data.createDummyGroup.clientMutationId" should be equal to "myId"
664664

665665
@createSchema
666-
@v3
667666
Scenario: Use serialization groups with relations
668667
Given there is 1 dummy object with relatedDummy and its thirdLevel
669668
And there is a RelatedDummy with 2 friends

‎features/graphql/query.feature

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
Feature: GraphQL query support
2+
23
@createSchema
34
Scenario: Execute a basic GraphQL query
45
Given there are 2 dummy objects with relatedDummy

‎features/graphql/type.feature

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
Feature: GraphQL type support
2+
23
@createSchema
34
Scenario: Use a custom type for a field
45
Given there are 2 dummy objects with dummyDate

‎features/hydra/collection.feature

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -328,6 +328,7 @@ Feature: Collections support
328328
"hydra:next":"/dummies?page=4"
329329
}
330330
"""
331+
331332
Scenario: Filter with exact match
332333
When I send a "GET" request to "/dummies?id=8"
333334
Then the response status code should be 200

‎features/hydra/error.feature

Lines changed: 30 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -86,42 +86,42 @@ Feature: Error handling
8686
And the JSON node "hydra:description" should exist
8787
And the JSON node "trace" should exist
8888

89-
Scenario: Get an error during update of an existing resource with a non-allowed update operation
90-
When I add "Content-Type" header equal to "application/ld+json"
91-
And I send a "POST" request to "/dummies" with body:
89+
Scenario: Get an error during update of an existing resource with a non-allowed update operation
90+
When I add "Content-Type" header equal to "application/ld+json"
91+
And I send a "POST" request to "/dummies" with body:
9292
"""
9393
{
9494
"@id": "/dummies/1",
9595
"name": "Foo"
9696
}
9797
"""
98-
Then the response status code should be 400
99-
And the response should be in JSON
100-
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
101-
And the JSON node "@context" should be equal to "/contexts/Error"
102-
And the JSON node "@type" should be equal to "hydra:Error"
103-
And the JSON node "hydra:title" should be equal to "An error occurred"
104-
And the JSON node "hydra:description" should be equal to "Update is not allowed for this operation."
105-
And the JSON node "trace" should exist
98+
Then the response status code should be 400
99+
And the response should be in JSON
100+
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
101+
And the JSON node "@context" should be equal to "/contexts/Error"
102+
And the JSON node "@type" should be equal to "hydra:Error"
103+
And the JSON node "hydra:title" should be equal to "An error occurred"
104+
And the JSON node "hydra:description" should be equal to "Update is not allowed for this operation."
105+
And the JSON node "trace" should exist
106106

107-
@createSchema
108-
Scenario: Populate database with related dummies. Check that id will be "/related_dummies/1"
109-
Given I add "Content-Type" header equal to "application/ld+json"
110-
And I send a "POST" request to "/related_dummies" with body:
107+
@createSchema
108+
Scenario: Populate database with related dummies. Check that id will be "/related_dummies/1"
109+
Given I add "Content-Type" header equal to "application/ld+json"
110+
And I send a "POST" request to "/related_dummies" with body:
111111
"""
112112
{
113113
"@type": "https://schema.org/Product",
114114
"symfony": "laravel"
115115
}
116116
"""
117-
Then the response status code should be 201
118-
And the response should be in JSON
119-
And the JSON node "@id" should be equal to "/related_dummies/1"
120-
And the JSON node "symfony" should be equal to "laravel"
117+
Then the response status code should be 201
118+
And the response should be in JSON
119+
And the JSON node "@id" should be equal to "/related_dummies/1"
120+
And the JSON node "symfony" should be equal to "laravel"
121121

122-
Scenario: Do not get an error during update of an existing relation with a non-allowed update operation
123-
When I add "Content-Type" header equal to "application/ld+json"
124-
And I send a "POST" request to "/relation_embedders" with body:
122+
Scenario: Do not get an error during update of an existing relation with a non-allowed update operation
123+
When I add "Content-Type" header equal to "application/ld+json"
124+
And I send a "POST" request to "/relation_embedders" with body:
125125
"""
126126
{
127127
"anotherRelated": {
@@ -131,11 +131,11 @@ Feature: Error handling
131131
}
132132
}
133133
"""
134-
Then the response status code should be 201
135-
And the response should be in JSON
136-
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
137-
And the JSON node "@context" should be equal to "/contexts/RelationEmbedder"
138-
And the JSON node "@type" should be equal to "RelationEmbedder"
139-
And the JSON node "@id" should be equal to "/relation_embedders/1"
140-
And the JSON node "anotherRelated.@id" should be equal to "/related_dummies/1"
141-
And the JSON node "anotherRelated.symfony" should be equal to "phalcon"
134+
Then the response status code should be 201
135+
And the response should be in JSON
136+
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
137+
And the JSON node "@context" should be equal to "/contexts/RelationEmbedder"
138+
And the JSON node "@type" should be equal to "RelationEmbedder"
139+
And the JSON node "@id" should be equal to "/relation_embedders/1"
140+
And the JSON node "anotherRelated.@id" should be equal to "/related_dummies/1"
141+
And the JSON node "anotherRelated.symfony" should be equal to "phalcon"

‎features/jsonapi/pagination.feature

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Feature: JSON API pagination handling
3636
Scenario: Get an error when provided page number is not valid
3737
When I send a "GET" request to "/dummies?page[page]=0"
3838
Then the response status code should be 400
39-
39+
4040
Scenario: Get an error when provided page number is too large
4141
When I send a "GET" request to "/dummies?page[page]=9223372036854775807"
4242
Then the response status code should be 400

‎features/jsonld/context.feature

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -48,12 +48,12 @@ Feature: JSON-LD contexts generation
4848
}
4949
"""
5050

51-
Scenario: Retrieve context of an object with an embed relation
52-
When I send a "GET" request to "/contexts/RelationEmbedder"
53-
Then the response status code should be 200
54-
And the response should be in JSON
55-
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
56-
And the JSON should be equal to:
51+
Scenario: Retrieve context of an object with an embed relation
52+
When I send a "GET" request to "/contexts/RelationEmbedder"
53+
Then the response status code should be 200
54+
And the response should be in JSON
55+
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
56+
And the JSON should be equal to:
5757
"""
5858
{
5959
"@context": {
@@ -67,12 +67,12 @@ Feature: JSON-LD contexts generation
6767
}
6868
"""
6969

70-
Scenario: Retrieve Dummy with extended jsonld context
71-
When I send a "GET" request to "/contexts/JsonldContextDummy"
72-
Then the response status code should be 200
73-
And the response should be in JSON
74-
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
75-
And the JSON should be equal to:
70+
Scenario: Retrieve Dummy with extended jsonld context
71+
When I send a "GET" request to "/contexts/JsonldContextDummy"
72+
Then the response status code should be 200
73+
And the response should be in JSON
74+
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
75+
And the JSON should be equal to:
7676
"""
7777
{
7878
"@context": {

‎features/jsonld/input_output.feature

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,7 @@ Feature: JSON-LD DTO input and output
275275
"""
276276

277277
@createSchema
278-
Scenario: Initialize input data with a DataTransformerInitializer
278+
Scenario: Initialize input data with a DataTransformerInitializer
279279
Given there is an InitializeInput object with id 1
280280
When I send a "PUT" request to "/initialize_inputs/1" with body:
281281
"""
@@ -302,15 +302,15 @@ Feature: JSON-LD DTO input and output
302302
"""
303303
{
304304
"foo": "test",
305-
"bar": "test"
305+
"bar": "test"
306306
}
307307
"""
308308
Then the response status code should be 400
309309
And the response should be in JSON
310310
And the JSON node "hydra:description" should be equal to "The input data is misformatted."
311311

312312
@!mongodb
313-
Scenario: Reset password through an input DTO without DataTransformer
313+
Scenario: Reset password through an input DTO without DataTransformer
314314
When I send a "POST" request to "/user-reset-password" with body:
315315
"""
316316
{
@@ -323,7 +323,7 @@ Feature: JSON-LD DTO input and output
323323
And the JSON node "email" should be equal to "[email protected]"
324324

325325
@!mongodb
326-
Scenario: Reset password with an invalid payload through an input DTO without DataTransformer
326+
Scenario: Reset password with an invalid payload through an input DTO without DataTransformer
327327
And I send a "POST" request to "/user-reset-password" with body:
328328
"""
329329
{

0 commit comments

Comments
 (0)