Make test configs distinct to verify production fallback

justin808 · claude · justin808 · commit 960b04a953b5 · 2025-10-09T14:00:20.000-10:00
Changed development config to have different values than production so the test actually verifies that staging falls back to production config, not just that it doesn't error. Development config now has: - source_path: app/javascript (vs app/packs) - source_entry_path: packs (vs entrypoints) - compile: true (vs false) This proves the test is actually using production values. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/spec/shakapacker/staging_env_instance_spec.rb b/spec/shakapacker/staging_env_instance_spec.rb
@@ -23,12 +23,13 @@
     let(:config_path) { File.join(Dir.pwd, "spec/fixtures/staging_config.yml") }
 
     before do
-      # Create a minimal config file for testing
+      # Create a minimal config file for testing with distinct values
       FileUtils.mkdir_p(File.dirname(config_path))
       File.write(config_path, <<~YAML)
         development:
-          source_path: app/packs
-          source_entry_path: entrypoints
+          source_path: app/javascript
+          source_entry_path: packs
+          compile: true
         production:
           source_path: app/packs
           source_entry_path: entrypoints
