-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathyaml.feature
More file actions
58 lines (50 loc) · 1.91 KB
/
yaml.feature
File metadata and controls
58 lines (50 loc) · 1.91 KB
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
46
47
48
49
50
51
52
53
54
55
56
57
58
@yaml @cats
Feature: clowder yaml
@help
Scenario: yaml help in empty directory
Given test directory is empty
When I run 'clowder yaml -h' and 'clowder yaml --help'
Then the commands succeed
@help
Scenario: yaml help with invalid clowder.yaml
Given cats example is initialized
And has invalid clowder.yml
When I run 'clowder yaml -h' and 'clowder yaml --help'
Then the commands succeed
@help
Scenario: yaml help with valid clowder.yaml
Given cats example is initialized
When I run 'clowder yaml -h' and 'clowder yaml --help'
Then the commands succeed
Scenario: yaml
Given cats example is initialized and herded
When I run 'clowder yaml | tee output.txt'
Then the command succeeds
And file output.txt matches contents of clowder.yml test file
Scenario: yaml resolved
Given cats example is initialized and herded
When I run 'clowder yaml -r | tee output.txt'
Then the command succeeds
And file output.txt matches contents of resolved.clowder.yml test file
@subdirectory
Scenario: yaml subdirectory
Given cats example is initialized and herded
When I change to directory black-cats/kishka
And I run 'clowder yaml | tee output.txt'
Then the command succeeds
And file black-cats/kishka/output.txt matches contents of clowder.yml test file
@fail
Scenario Outline: yaml resolved with missing repos
Given cats example is initialized
And <directory> doesn't exist
When I run 'clowder yaml -r'
Then the command fails
And project at <directory> doesn't exist
Examples:
| directory |
| mu |
| duke |
| black-cats/kishka |
| black-cats/kit |
| black-cats/sasha |
| black-cats/june |