How to override Policyfile run_list in Test-Kitchen (.kitchen.yml)?
Is there a way to force Test-Kitchen to honor the .kitchen.yml run-list while still using Policyfiles?
Why Is Test-Kitchen ignoring my Run-list?

This is about Policyfiles and how to test specific recipes or different run-lists in Test Kitchen.

If you are moving from Berkshelf to Policyfiles, you’ve likely encountered a frustrating hurdle: you define a run_list in your .kitchen.yml, but Test-Kitchen completely ignores it, opting instead for the run-list defined in your Policyfile.rb.

Transitioning to Policyfiles: Why Is Test-Kitchen Ignoring My Run-list?

If you are moving from Berkshelf to Policyfiles, you’ve likely encountered a frustrating hurdle: you define a run_list in your .kitchen.yml, but Test-Kitchen completely ignores it, opting instead for the run-list defined in your Policyfile.rb.

This isn't a bug, it’s a fundamental shift in how Chef manages the "node state." In the Berkshelf workflow, the run-list was dynamic and assembled at runtime. With Policyfiles, the Policyfile is designed to be an immutable "lockfile" for both dependencies and the run-list.

When you tell Test-Kitchen to use a Policyfile, the kitchen-chef provisioner assumes that the Policyfile is the sole source of truth. It compiles the cookbooks and the run-list into a single archive. If the provisioner sees a Policyfile, it treats the .kitchen.yml run-list as secondary or irrelevant.

1. The Recommended way is - Use named_run_lists
   1. Policyfiles allow you to define alternative run-lists within the Policyfile.rb. This is the "native" way to handle different test suites.

   2. In your Policyfile.rb:

      name 'my_cookbook'
      run_list 'my_cookbook::default'
      
      # Define a specific list for your test suite
      named_run_list :test_feature, 'my_cookbook::default', 'my_cookbook::client_config'
      

      c. In your .kitchen.yml:

      suites:
        - name: feature
          provisioner:
            named_run_list: test_feature
      

       

2.  The "Hybrid Way" (Separate Test Policyfiles)
   1. Sometimes you need a run-list that includes "test-only" cookbooks (like inspec or netstat) that you don't want in your production Policyfile. In this case, create a dedicated Policyfile for testing.

1. • Create test/policyfiles/default.rb.
   • Point your suite to it in .kitchen.yml:

suites:
  - name: default
    provisioner:
      policyfile_path: test/policyfiles/default.rb

Overall, the shift to Policyfiles requires moving your logic out of the YAML and into the Ruby Policyfile. While it feels less flexible at first, it ensures that what you test in Kitchen is exactly what will run in production.

References :
About Policyfiles - https://docs.chef.io/policyfile/
Test Kitchen - https://kitchen.ci