Sha256: 115d41ccb156b82b7c854a4253c07bc361a34ab3a7f2b9482704aec8f7db8fb0
Contents?: true
Size: 1.63 KB
Versions: 14
Compression:
Stored size: 1.63 KB
Contents
@active Feature: Initialization As a user, when I initialize PinPress, I should be guided through the process as necessary. Scenario: Basic Initialization Given no file located at "/tmp/pp/.pinpress" When I run `pinpress init` interactively And I type "" And I type "bachya:12345" Then the exit status should be 0 And a valid configuration file should exist at "/tmp/pp/.pinpress" Scenario: Reinitialization (refuse) Given an existing current configuration file located at "/tmp/pp/.pinpress" When I run `pinpress init` interactively And I type "" Then the exit status should be 0 Scenario: Reinitialization (accept) Given an existing current configuration file located at "/tmp/pp/.pinpress" When I run `pinpress init` interactively And I type "y" And I type "" And I type "bachya:12345" Then the exit status should be 0 And a valid configuration file should exist at "/tmp/pp/.pinpress" Scenario: Reinitialization (accept) Given an existing current configuration file located at "/tmp/pp/.pinpress" When I run `pinpress init -s` interactively And I type "" And I type "bachya:12345" Then the exit status should be 0 And a valid configuration file should exist at "/tmp/pp/.pinpress" Scenario: Update out-of-date configuration file Given an existing old configuration file located at "/tmp/pp/.pinpress" When I run `pinpress init` interactively And I type "" And I type "" And I type "bachya:12345" Then the exit status should be 0 And a valid configuration file should exist at "/tmp/pp/.pinpress"
Version data entries
14 entries across 14 versions & 1 rubygems