jettypod 3.0.2 → 4.0.0

package/SYSTEM-BEHAVIOR.md

@@ -1,16 +1,17 @@
 # JettyPod System Behaviors
 
-*Auto-generated from test scenarios on 2025-11-06*
+*Auto-generated from test scenarios on 2025-11-10*
 
 ## Summary
 
-- **13** features
-- **65** test scenarios
-- **312** test steps
+- **14** features
+- **73** test scenarios
+- **360** test steps
 
 ## Table of Contents
 
-- [Auto-generate production chores on external transition](#auto-generate-production-chores-on-external-transition) (1 scenarios)
+- [Auto-Generate Production Chores at End of Stable Mode](#auto-generate-production-chores-at-end-of-stable-mode) (6 scenarios)
+- [Backlog Command](#backlog-command) (3 scenarios)
 - [Git Hook Integration](#git-hook-integration) (4 scenarios)
 - [Git Hooks Integration](#git-hooks-integration) (1 scenarios)
 - [JettyPod update command](#jettypod-update-command) (5 scenarios)
@@ -30,14 +31,46 @@
 
 This documentation is derived from actual passing tests. It describes the verified behaviors of the system.
 
-### Auto-generate production chores on external transition
+### Auto-Generate Production Chores at End of Stable Mode
 
-*Related features: Auto-generate production chores on external transition*
+*Related features: Auto-Generate Production Chores at End of Stable Mode*
 
 **Verified behaviors:**
 
-- **User transitions project to external with stable features**
-  When I have a project with 3 features in stable mode, the project state is "internal", I transition the project to external → the project state is set to "external" and a "Feature Production Readiness" epic is created and 3 production chores are created for each stable feature and the chores are grouped under the epic and I see a summary of created chores
+- **Generate production chores after stable mode completes (external project)**
+  When I have a feature with all stable mode scenarios passing, the project state is "external", the stable mode skill has hot context from implementation, the stable mode skill completes and I confirm the production chores → it analyzes the implementation files for production gaps and it proposes specific production chores with file references and it shows a preview of the production chores and it asks for confirmation and it creates the production chores in production mode and the chores are visible in the backlog and the feature transitions to production mode and I see "✅ Created N production chores. Feature elevated to production mode."
+
+- **User declines production chore creation**
+  When I have a feature with all stable mode scenarios passing, the project state is "external", the stable mode skill has hot context from implementation, the stable mode skill completes and it proposes production chores and I decline the production chores → no production chores are created and the feature remains in stable mode and I see "⏭️  Skipped production chore creation"
+
+- **No implementation files found in git history**
+  When I have a feature with all stable mode scenarios passing, the feature has no git commits, the stable mode skill completes → it warns "No git commits found for this feature" and it creates generic production chores and the feature transitions to production mode
+
+- **Internal project state (feature elevated to production mode)**
+  When I have a feature with all stable mode scenarios passing, the project state is "internal", the stable mode skill completes → it creates production chores and the feature transitions to production mode and I see "Created 3 production chores. Feature elevated to production mode."
+
+- **No production gaps found**
+  When I have a feature with all stable mode scenarios passing, the implementation has no security, scale, or compliance gaps, the stable mode skill completes → it creates generic production chores as placeholders and the feature transitions to production mode
+
+- **Feature already in production mode**
+  When I have a feature already in production mode, I try to complete a stable mode chore → the system does not trigger production chore generation and I see a warning "Feature is already in production mode"
+
+---
+
+### Backlog Command
+
+*Related features: Backlog Command*
+
+**Verified behaviors:**
+
+- **User views active backlog items**
+  When I have work items in various statuses, I run "jettypod backlog" → I see only active work items (backlog, todo, in_progress) and I see the items in a tree hierarchy and completed items are hidden
+
+- **User views all work items including completed**
+  When I have work items in various statuses, I run "jettypod backlog all" → I see all work items regardless of status and I see the items in a tree hierarchy
+
+- **User views only completed items**
+  When I have work items in various statuses, I run "jettypod backlog completed" → I see only completed work items (done, cancelled) and I see the items in a tree hierarchy
 
 ---
 
@@ -246,7 +279,7 @@ This documentation is derived from actual passing tests. It describes the verifi
   When jettypod is initialized, jettypod is initialized, I create a chore "Test Chore" without mode and I create a feature "Test Feature" with mode "<mode>" → the work item is created successfully and the work item has NULL mode and the work item is created successfully and the work item has mode "<mode>"
 
 - **Epic with children in different modes**
-  When jettypod is initialized, I create an epic "Test Epic" without mode, I create a feature "Speed Feature" with mode "speed" and parent epic, I create a bug "Stable Bug" with mode "stable" and parent epic, I create a chore "Test Chore" without mode and parent epic, I view the work tree → I see the epic without mode indicator and I see the feature with mode "speed" and I see the bug with mode "stable" and I see the chore without mode indicator
+  When jettypod is initialized, I create an epic "Test Epic" without mode, I create a feature "Speed Feature" with mode "speed" and parent epic, I create a bug "Stable Bug" with mode "stable" and parent epic, I create a chore "Test Chore" without mode and parent epic, I view the backlog → I see the epic without mode indicator and I see the feature with mode "speed" and I see the bug with mode "stable" and I see the chore without mode indicator
 
 - **Create multiple items with same title but different modes**
   When jettypod is initialized, I create a feature "Duplicate" with mode "speed" and I create a feature "Duplicate" with mode "stable" → both work items are created successfully and they have different modes
@@ -331,25 +364,143 @@ This documentation is derived from actual passing tests. It describes the verifi
 
 ## Detailed Feature Specifications
 
-### Auto-generate production chores on external transition
+### Auto-Generate Production Chores at End of Stable Mode
 
-When transitioning to external, automatically create production chores for all stable features Approach: Silent Auto-Generation
+When stable mode completes all scenarios for a feature, the skill analyzes the implementation with hot context and generates specific, actionable production chores. Chore visibility depends on project state (external vs internal). Epic: Production Mode Approach: Preview-and-Confirm (Transparent)
 
-#### User transitions project to external with stable features
+#### Generate production chores after stable mode completes (external project)
 
 **Context:**
-- I have a project with 3 features in stable mode
+- I have a feature with all stable mode scenarios passing
+- the project state is "external"
+- the stable mode skill has hot context from implementation
+
+**Action:**
+- the stable mode skill completes
+- I confirm the production chores
+
+**Expected outcome:**
+- it analyzes the implementation files for production gaps
+- it proposes specific production chores with file references
+- it shows a preview of the production chores
+- it asks for confirmation
+- it creates the production chores in production mode
+- the chores are visible in the backlog
+- the feature transitions to production mode
+- I see "✅ Created N production chores. Feature elevated to production mode."
+
+#### User declines production chore creation
+
+**Context:**
+- I have a feature with all stable mode scenarios passing
+- the project state is "external"
+- the stable mode skill has hot context from implementation
+
+**Action:**
+- the stable mode skill completes
+- it proposes production chores
+- I decline the production chores
+
+**Expected outcome:**
+- no production chores are created
+- the feature remains in stable mode
+- I see "⏭️  Skipped production chore creation"
+
+#### No implementation files found in git history
+
+**Context:**
+- I have a feature with all stable mode scenarios passing
+- the feature has no git commits
+
+**Action:**
+- the stable mode skill completes
+
+**Expected outcome:**
+- it warns "No git commits found for this feature"
+- it creates generic production chores
+- the feature transitions to production mode
+
+#### Internal project state (feature elevated to production mode)
+
+**Context:**
+- I have a feature with all stable mode scenarios passing
 - the project state is "internal"
 
 **Action:**
-- I transition the project to external
+- the stable mode skill completes
+
+**Expected outcome:**
+- it creates production chores
+- the feature transitions to production mode
+- I see "Created 3 production chores. Feature elevated to production mode."
+
+#### No production gaps found
+
+**Context:**
+- I have a feature with all stable mode scenarios passing
+- the implementation has no security, scale, or compliance gaps
+
+**Action:**
+- the stable mode skill completes
+
+**Expected outcome:**
+- it creates generic production chores as placeholders
+- the feature transitions to production mode
+
+#### Feature already in production mode
+
+**Context:**
+- I have a feature already in production mode
+
+**Action:**
+- I try to complete a stable mode chore
+
+**Expected outcome:**
+- the system does not trigger production chore generation
+- I see a warning "Feature is already in production mode"
+
+---
+
+### Backlog Command
+
+Enhanced command to view work items with built-in filters Approach: Enhanced backlog with filters (backlog, backlog all, backlog completed)
+
+#### User views active backlog items
+
+**Context:**
+- I have work items in various statuses
+
+**Action:**
+- I run "jettypod backlog"
+
+**Expected outcome:**
+- I see only active work items (backlog, todo, in_progress)
+- I see the items in a tree hierarchy
+- completed items are hidden
+
+#### User views all work items including completed
+
+**Context:**
+- I have work items in various statuses
+
+**Action:**
+- I run "jettypod backlog all"
+
+**Expected outcome:**
+- I see all work items regardless of status
+- I see the items in a tree hierarchy
+
+#### User views only completed items
+
+**Context:**
+- I have work items in various statuses
+
+**Action:**
+- I run "jettypod backlog completed"
 
 **Expected outcome:**
-- the project state is set to "external"
-- a "Feature Production Readiness" epic is created
-- 3 production chores are created for each stable feature
-- the chores are grouped under the epic
-- I see a summary of created chores
+- I see only completed work items (done, cancelled)
+- I see the items in a tree hierarchy
 
 ---
 
@@ -947,7 +1098,7 @@ As a developer I want new work items to default to discovery mode So I can start
 - I create a chore "Test Chore" without mode and parent epic
 
 **Action:**
-- I view the work tree
+- I view the backlog
 
 **Expected outcome:**
 - I see the epic without mode indicator

package/docs/COMMAND_REFERENCE.md

@@ -9,8 +9,8 @@ Complete reference for all JettyPod commands as of 2025-10-31.
 1. [Initialization & Setup](#initialization--setup)
 2. [Project Discovery](#project-discovery)
 3. [Work Item Management](#work-item-management)
-4. [Epic Discovery](#epic-discovery)
-5. [Feature Discovery](#feature-discovery)
+4. [Epic Planning](#epic-planning)
+5. [Feature Planning](#feature-planning)
 6. [Work Status & Navigation](#work-status--navigation)
 7. [Mode Management](#mode-management)
 8. [Decisions](#decisions)
@@ -119,7 +119,7 @@ jettypod work create epic "Real-time Updates" "Live data sync" --needs-discovery
 
 **What it creates:**
 - Epic work item in database
-- Entry in work tree
+- Entry in backlog
 - Triggers epic discovery prompt if `--needs-discovery` flag set
 
 ---
@@ -183,14 +183,14 @@ jettypod work create bug "Memory leak in dashboard" --parent=10
 
 ---
 
-## Epic Discovery
+## Epic Planning
 
-### `jettypod work epic-discover <epic-id>`
+### `jettypod work epic-planning <epic-id>`
 
-Start architectural discovery for an epic.
+Start architectural planning for an epic.
 
 ```bash
-jettypod work epic-discover 5
+jettypod work epic-planning 5
 ```
 
 **Prerequisites:**
@@ -198,7 +198,7 @@ jettypod work epic-discover 5
 - Epic must be in backlog/todo status
 
 **What it does:**
-- Activates epic-discover skill in Claude Code
+- Activates epic-planning skill in Claude Code
 - Guides through architectural decision process
 - Helps identify key technical decisions needed
 
@@ -253,11 +253,11 @@ jettypod work epic-implement 5 \
 
 ---
 
-## Feature Discovery
+## Feature Planning
 
 ### `jettypod work discover <feature-id>`
 
-Start UX discovery for a feature.
+Start UX planning for a feature.
 
 ```bash
 jettypod work discover 12
@@ -268,7 +268,7 @@ jettypod work discover 12
 - Feature must be in "discovery" phase
 
 **What it does:**
-- Activates feature-discover skill
+- Activates feature-planning skill
 - Guides through UX approach exploration
 - Generates BDD scenarios
 - Helps create discovery checkpoints
@@ -326,20 +326,20 @@ Focus: Happy path only, single file when possible
 
 ## Work Status & Navigation
 
-### `jettypod work tree [flags]`
+### `jettypod backlog [flags]`
 
 Display hierarchical tree of all work items.
 
 ```bash
 # Collapsed view (default)
-jettypod work tree
+jettypod backlog
 
 # Expand specific items
-jettypod work tree --expand=1
-jettypod work tree --expand=1,5,10
+jettypod backlog --expand=1
+jettypod backlog --expand=1,5,10
 
 # Expand all items
-jettypod work tree --expand-all
+jettypod backlog --expand-all
 ```
 
 **Flags:**
@@ -773,9 +773,9 @@ JettyPod uses SQLite with the following main tables:
 ├── work.db              # SQLite database
 ├── current-work.json    # Active work item
 ├── config.json          # Project configuration
-└── skills/              # Discovery skills for Claude Code
-    ├── epic-discover/
-    └── feature-discover/
+└── skills/              # Planning skills for Claude Code
+    ├── epic-planning/
+    └── feature-planning/
 
 docs/
 └── DECISIONS.md         # Auto-generated decision log
@@ -826,13 +826,13 @@ JettyPod is designed to work seamlessly with Claude Code:
 - Includes mode-specific guidance
 - Shows project state and decisions
 
-### Discovery Skills
-- `epic-discover` - Guides architectural decisions
-- `feature-discover` - Guides UX exploration
+### Planning Skills
+- `epic-planning` - Guides architectural decisions
+- `feature-planning` - Guides UX exploration
 
 ### Automatic Triggers
-- Creating epic with `--needs-discovery` → prompts epic-discover
-- Creating feature → prompts feature-discover
+- Creating epic with `--needs-discovery` → prompts epic-planning
+- Creating feature → prompts feature-planning
 - Starting work → updates Claude context
 
 ---
@@ -864,8 +864,8 @@ JettyPod is designed to work seamlessly with Claude Code:
    - Mark winners with `--winner`
    - Reference in future decisions
 
-6. **Use Work Tree**
-   - `jettypod work tree` for overview
+6. **Use Backlog**
+   - `jettypod backlog` for overview
    - `--expand` to see details
    - Track progress visually
 

package/docs/gap-analysis-current-vs-comprehensive-methodology.md

@@ -551,7 +551,7 @@ CREATE TABLE project_config (
 | `jettypod work create feature` | Create with any mode | Default to 'discovery' phase | 🟡 **HIGH** |
 | `jettypod work start <id>` | Set current + branch | Validate mode progression | 🟡 **HIGH** |
 | `jettypod init` | Initialize discovery mode | Initialize Internal project | 🟡 **HIGH** |
-| `jettypod work tree` | Show work items | Show phase + mode | 🟢 **MEDIUM** |
+| `jettypod backlog` | Show work items | Show phase + mode | 🟢 **MEDIUM** |
 
 ### Commands to DEPRECATE
 
@@ -691,7 +691,7 @@ To reconcile current implementation with comprehensive methodology, execute thes
    - Chore: Default to 'implementation' for backwards compatibility
    - Chore: Create `jettypod work discover <id>` command (features only)
    - Chore: Create `jettypod work implement <id>` command (features only)
-   - Chore: Update `work tree` to show phase
+   - Chore: Update `backlog` to show phase
 
 4. Feature: Multi-level prototype tracking
    - Chore: Add `prototype_files` JSON field to work_items
@@ -771,7 +771,7 @@ To reconcile current implementation with comprehensive methodology, execute thes
 2. Feature: Mode inheritance enforcement
    - Chore: Prevent direct mode assignment to chores
    - Chore: Inherit mode from parent feature
-   - Chore: Update `work tree` to show inherited modes
+   - Chore: Update `backlog` to show inherited modes
    - Chore: Migrate existing chore modes
 
 3. Feature: Bug workflow definition

package/features/auto-generate-production-chores.feature

@@ -1,14 +1,65 @@
-Feature: Auto-generate production chores on external transition
-  When transitioning to external, automatically create production chores for all stable features
+Feature: Auto-Generate Production Chores at End of Stable Mode
+  When stable mode completes all scenarios for a feature, the skill analyzes the
+  implementation with hot context and generates specific, actionable production chores.
+  Chore visibility depends on project state (external vs internal).
 
-  Approach: Silent Auto-Generation
+  Epic: Production Mode
+  Approach: Preview-and-Confirm (Transparent)
 
-Scenario: User transitions project to external with stable features
-  Given I have a project with 3 features in stable mode
+Scenario: Generate production chores after stable mode completes (external project)
+  Given I have a feature with all stable mode scenarios passing
+  And the project state is "external"
+  And the stable mode skill has hot context from implementation
+  When the stable mode skill completes
+  Then it analyzes the implementation files for production gaps
+  And it proposes specific production chores with file references
+  And it shows a preview of the production chores
+  And it asks for confirmation
+  When I confirm the production chores
+  Then it creates the production chores in production mode
+  And the chores are visible in the backlog
+  And the feature transitions to production mode
+  And I see "✅ Created N production chores. Feature elevated to production mode."
+
+# SPEED MODE: Only happy path above
+# STABLE MODE: Add error handling, edge cases, validation scenarios below
+
+Scenario: User declines production chore creation
+  Given I have a feature with all stable mode scenarios passing
+  And the project state is "external"
+  And the stable mode skill has hot context from implementation
+  When the stable mode skill completes
+  And it proposes production chores
+  And I decline the production chores
+  Then no production chores are created
+  And the feature remains in stable mode
+  And I see "⏭️  Skipped production chore creation"
+
+Scenario: No implementation files found in git history
+  Given I have a feature with all stable mode scenarios passing
+  And the feature has no git commits
+  When the stable mode skill completes
+  Then it warns "No git commits found for this feature"
+  And it creates generic production chores
+  And the feature transitions to production mode
+
+Scenario: Internal project state (feature elevated to production mode)
+  Given I have a feature with all stable mode scenarios passing
   And the project state is "internal"
-  When I transition the project to external
-  Then the project state is set to "external"
-  And a "Feature Production Readiness" epic is created
-  And 3 production chores are created for each stable feature
-  And the chores are grouped under the epic
-  And I see a summary of created chores
+  When the stable mode skill completes
+  Then it creates production chores
+  And the feature transitions to production mode
+  And I see "Created 3 production chores. Feature elevated to production mode."
+
+Scenario: No production gaps found
+  Given I have a feature with all stable mode scenarios passing
+  And the implementation has no security, scale, or compliance gaps
+  When the stable mode skill completes
+  Then it creates generic production chores as placeholders
+  And the feature transitions to production mode
+
+Scenario: Feature already in production mode
+  Given I have a feature already in production mode
+  When I try to complete a stable mode chore
+  Then the system does not trigger production chore generation
+  And I see a warning "Feature is already in production mode"

package/features/backlog-command.feature

@@ -0,0 +1,26 @@
+Feature: Backlog Command
+  Enhanced command to view work items with built-in filters
+
+  Approach: Enhanced backlog with filters (backlog, backlog all, backlog completed)
+
+Scenario: User views active backlog items
+  Given I have work items in various statuses
+  When I run "jettypod backlog"
+  Then I see only active work items (backlog, todo, in_progress)
+  And I see the items in a tree hierarchy
+  And completed items are hidden
+
+Scenario: User views all work items including completed
+  Given I have work items in various statuses
+  When I run "jettypod backlog all"
+  Then I see all work items regardless of status
+  And I see the items in a tree hierarchy
+
+Scenario: User views only completed items
+  Given I have work items in various statuses
+  When I run "jettypod backlog completed"
+  Then I see only completed work items (done, cancelled)
+  And I see the items in a tree hierarchy
+
+# SPEED MODE: Only happy path scenarios above
+# STABLE MODE: Will add error handling, edge cases, validation scenarios

package/features/claude-md-protection/steps.js

@@ -35,7 +35,7 @@ Given('a JettyPod project with hook installed', function () {
   execSync('git init', { stdio: 'pipe' });
   execSync('git config user.email "test@test.com"', { stdio: 'pipe' });
   execSync('git config user.name "Test"', { stdio: 'pipe' });
-  execSync(`node ${path.join(originalDir, 'jettypod.js')} init`, { stdio: 'pipe' });
+  execSync(`node ${path.join(originalDir, 'jettypod.js')} init`, { stdio: 'pipe', env: { ...process.env, NODE_ENV: 'test' } });
 
   // Verify hook was installed
   const hookPath = path.join(testDir, '.jettypod', 'hooks', 'protect-claude-md.js');
@@ -113,7 +113,7 @@ Given('a JettyPod project in discovery mode', function () {
   execSync('git init', { stdio: 'pipe' });
   execSync('git config user.email "test@test.com"', { stdio: 'pipe' });
   execSync('git config user.name "Test"', { stdio: 'pipe' });
-  execSync(`node ${path.join(originalDir, 'jettypod.js')} init`, { stdio: 'pipe' });
+  execSync(`node ${path.join(originalDir, 'jettypod.js')} init`, { stdio: 'pipe', env: { ...process.env, NODE_ENV: 'test' } });
 
   // Mode is now managed by work items, not project-level config
   const config = JSON.parse(fs.readFileSync('.jettypod/config.json', 'utf-8'));
@@ -349,7 +349,8 @@ When('Claude Code attempts to Write a new CLAUDE.md file', function () {
 When('I run jettypod command {string}', function (command) {
   const result = execSync(`node ${path.join(originalDir, 'jettypod.js')} ${command.replace('jettypod ', '')}`, {
     stdio: 'pipe',
-    encoding: 'utf-8'
+    encoding: 'utf-8',
+    env: { ...process.env, NODE_ENV: 'test' }
   });
   this.commandOutput = result;
 });
@@ -395,7 +396,8 @@ When('Claude Code tries to change mode to speed by editing CLAUDE.md', function
 
 When('I run jettypod command {string} instead', function (command) {
   execSync(`node ${path.join(originalDir, 'jettypod.js')} ${command.replace('jettypod ', '')}`, {
-    stdio: 'pipe'
+    stdio: 'pipe',
+    env: { ...process.env, NODE_ENV: 'test' }
   });
 });
 

package/features/decisions/index.js

@@ -186,8 +186,8 @@ async function showAllDecisions() {
       } else {
         console.log('No epic decisions yet.');
         console.log('');
-        console.log('💡 Tip: Make architectural decisions during epic discovery:');
-        console.log('   jettypod work epic-discover <epic-id>');
+        console.log('💡 Tip: Make architectural decisions during epic planning:');
+        console.log('   jettypod work epic-planning <epic-id>');
         console.log('');
       }
 
@@ -288,8 +288,8 @@ async function showEpicDecisions() {
       } else {
         console.log('No epic decisions yet.');
         console.log('');
-        console.log('💡 Tip: Make architectural decisions during epic discovery:');
-        console.log('   jettypod work epic-discover <epic-id>');
+        console.log('💡 Tip: Make architectural decisions during epic planning:');
+        console.log('   jettypod work epic-planning <epic-id>');
         console.log('');
       }
 
@@ -319,7 +319,7 @@ async function promptForEpicId() {
         console.log('❌ No epic ID entered');
         console.log('Please run the command again and enter an epic ID');
         console.log('');
-        console.log('💡 Tip: See your epics with: jettypod work tree');
+        console.log('💡 Tip: See your epics with: jettypod backlog');
         console.log('');
         process.exit(1);
       }
@@ -332,7 +332,7 @@ async function promptForEpicId() {
         console.log(`❌ Invalid epic ID: "${trimmed}"`);
         console.log('Please enter a numeric epic ID');
         console.log('');
-        console.log('💡 Tip: See your epics with: jettypod work tree');
+        console.log('💡 Tip: See your epics with: jettypod backlog');
         console.log('');
         process.exit(1);
       }
@@ -386,7 +386,7 @@ async function showDecisionsForEpic(epicId) {
         console.log(`  - Epic #${epicId} does not exist`);
         console.log(`  - Work item #${epicId} is not an epic`);
         console.log('');
-        console.log('💡 Tip: See your epics with: jettypod work tree');
+        console.log('💡 Tip: See your epics with: jettypod backlog');
         console.log('');
         return resolve();
       }
@@ -425,8 +425,8 @@ async function showDecisionsForEpic(epicId) {
         } else {
           console.log('No decisions for this epic yet.');
           console.log('');
-          console.log('💡 Tip: Make architectural decisions during epic discovery:');
-          console.log(`   jettypod work epic-discover ${epicId}`);
+          console.log('💡 Tip: Make architectural decisions during epic planning:');
+          console.log(`   jettypod work epic-planning ${epicId}`);
           console.log('');
         }
 
@@ -470,7 +470,7 @@ function viewDecisionsFile() {
       console.log('   - You make epic architectural decisions');
       console.log('');
       console.log('To make decisions:');
-      console.log('   jettypod work epic-discover <epic-id>');
+      console.log('   jettypod work epic-planning <epic-id>');
       console.log('');
     }
   } catch (err) {

package/features/git-hooks/simple-steps.js

@@ -22,13 +22,13 @@ Given('I initialize a git repo with devpod', function () {
   execSync('git init', { stdio: 'pipe' });
   execSync('git config user.email "test@test.com"', { stdio: 'pipe' });
   execSync('git config user.name "Test"', { stdio: 'pipe' });
-  execSync(`node ${path.join(originalDir, 'jettypod.js')} init`, { stdio: 'pipe' });
+  execSync(`node ${path.join(originalDir, 'jettypod.js')} init`, { stdio: 'pipe', env: { ...process.env, NODE_ENV: 'test' } });
 });
 
 Given('I create and start work on a todo item', function () {
-  execSync(`node ${path.join(originalDir, 'jettypod.js')} work create feature "Test"`, { stdio: 'pipe' });
-  execSync(`node ${path.join(originalDir, 'jettypod.js')} work status 1 todo`, { stdio: 'pipe' });
-  execSync(`node ${path.join(originalDir, 'jettypod.js')} work start 1`, { stdio: 'pipe' });
+  execSync(`node ${path.join(originalDir, 'jettypod.js')} work create feature "Test"`, { stdio: 'pipe', env: { ...process.env, NODE_ENV: 'test' } });
+  execSync(`node ${path.join(originalDir, 'jettypod.js')} work status 1 todo`, { stdio: 'pipe', env: { ...process.env, NODE_ENV: 'test' } });
+  execSync(`node ${path.join(originalDir, 'jettypod.js')} work start 1`, { stdio: 'pipe', env: { ...process.env, NODE_ENV: 'test' } });
   workItemId = 1;
 });