forked from apiaryio/drafter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathparse.feature
45 lines (29 loc) · 1.5 KB
/
parse.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Feature: Parse a blueprint
Scenario: Parse a blueprint file into YAML
When I run `drafter -t ast blueprint.apib`
Then the output should contain the content of file "ast.yaml"
Scenario: Parse a blueprint input into YAML
When I run `drafter -t ast` interactively
When I pipe in the file "blueprint.apib"
Then the output should contain the content of file "ast.yaml"
Scenario: Parse a blueprint file into JSON
When I run `drafter -t ast -f json blueprint.apib`
Then the output should contain the content of file "ast.json"
Scenario: Parse a blueprint input into JSON
When I run `drafter -t ast -f json` interactively
When I pipe in the file "blueprint.apib"
Then the output should contain the content of file "ast.json"
Scenario: Parse a blueprint file into Refract YAML
When I run `drafter blueprint.apib`
Then the output should contain the content of file "refract.yaml"
Scenario: Parse a blueprint input into Refract YAML
When I run `drafter` interactively
When I pipe in the file "blueprint.apib"
Then the output should contain the content of file "refract.yaml"
Scenario: Parse a blueprint file into Refract JSON
When I run `drafter -f json blueprint.apib`
Then the output should contain the content of file "refract.json"
Scenario: Parse a blueprint input into Refract JSON
When I run `drafter -f json` interactively
When I pipe in the file "blueprint.apib"
Then the output should contain the content of file "refract.json"