40 lines
1.6 KiB
Gherkin
40 lines
1.6 KiB
Gherkin
Feature: Credentials Path Resolution
|
|
As a developer
|
|
I want credentials paths to be resolved correctly
|
|
So that the tracker works with both absolute and relative paths
|
|
|
|
Background:
|
|
Given a temporary credentials directory
|
|
|
|
Scenario: Resolve absolute credentials path
|
|
Given an absolute credentials path
|
|
When I create a tracker with the absolute credentials path
|
|
Then the credentials path should be used as-is
|
|
And the tracker should authenticate successfully
|
|
|
|
Scenario: Resolve relative credentials path
|
|
Given a relative credentials path
|
|
When I create a tracker with the relative credentials path
|
|
Then the credentials path should be resolved relative to project root
|
|
And the tracker should authenticate successfully
|
|
|
|
Scenario: Resolve credentials path from environment variable
|
|
Given environment variable GOOGLE_SHEETS_CREDENTIALS_PATH is set to relative path
|
|
When I create a tracker without explicit credentials path
|
|
Then the credentials path should be resolved from environment variable
|
|
And the tracker should authenticate successfully
|
|
|
|
Scenario: Handle missing credentials path gracefully
|
|
Given no credentials path is provided
|
|
And no environment variable is set
|
|
When I create a tracker
|
|
Then the tracker should initialize without credentials path
|
|
And authentication should fail gracefully
|
|
|
|
Scenario: Resolve credentials path with nested directories
|
|
Given a credentials path in nested directory structure
|
|
When I create a tracker with the nested path
|
|
Then the credentials path should be resolved correctly
|
|
And the tracker should authenticate successfully
|
|
|