https://www.puppet.com/community logo
Join Slack
Powered by
# testing
  • h
    they work the same, you just don't assign them to a variable
  • l
    right, ruby's return without a keyword syntax 😐
  • l
    possibly my least favorite rubyism
  • h
    Copy code
    let(:pre_condition) do
  <<~'EOF'
  something
  something
  EOF
end
  • h
    yeah, it can be really odd because something is always returned, whether you want it to be or not
  • c
    @bastelfreak's worked. Just needed a comma.
    👍 2
  • h
    nice, I didn't know you could pass multiple args to 
    include
  • l
    I don't ever plan to use it outside testing
  • l
    but good to know
  • c
    yeah, that's all I'm doing
  • r
    I think you can do 
    include $array
    . Why is not clear to me though 😄
  • d
    We did a role and profile pattern where you could manage classes via hiera to make it slightly less rigid for some customers
    b
    r
    • 3
    • 7
  • r
    Anybody here using beaker with Ubuntu-24 ? The 'run_puppet_install_helper' installs the puppet just fine, but then gives me this error: puppet agent -t Last 10 lines of output were: bash: line 1: puppet: command not found Seems a PATH issue, but when I login manually I can't reproduce it, the $PATH has /opt/puppetlabs/bin
    b
    • 2
    • 10
  • r
    Same beaker with Ubuntu-22 runs just fine, somethings changed in Ubuntu-24 seems
  • t
    I have an issue to mock a fact in testing. I am having some code like this in a spec test:
    Copy code
    on_supported_os.each do |os, os_facts|
      context "on #{os}" do
        let(:facts) do
          os_facts.merge(networking: { fqdn: 'my.domain.foo' })
        end
    but 
    $facts{'networking']['fqdn']
    always has the value defined in 
    spec/default_facts.yml
    b
    y
    h
    • 4
    • 35
  • j
    Any beaker geniuses in here?
  • b
    "genius" is a bit much
  • b
    but #C0W1Y5VL0 maintains beaker
  • j
    Trying to add a couple of docker settings like a different network and a bind mount, but can't figure out how to get that into my 
    spec_helper_acceptance.rb
  • j
    So, I should go to that channel?
  • b
    it's worth trying 🙂
  • j
    Thx.
  • t
    in a standard unit test can I access the parameters of the class/defined resource that is currently evaluated?
    y
    h
    • 3
    • 4
  • e
    It’s hard enough to keep modules all up to date without folding in your own changes :)
    👍 1
    b
    • 2
    • 1
  • b
    I'm dong what couldn't be a more simple test on a class module that does concat. It fails with: 
    error during compilation: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, wrong number of arguments (given 3, expected 1..2)
    The class module (if you can call it that) couldn't be more simple: 
    --class manhattan::a {
    concat { '/bin/foo':
    owner => 'root',
    group => 'root',
    mode  => '0755',
    }
    }
    bundle references me to: 
    concat/manifests/init.pp, line: 107, column: 27)
    but for the life of me I can't figure out what's going on. The class module passes all other tests. My .fixtures.yml file references: 
    concat:
    repo: "<https://github.com/puppetlabs/puppetlabs-concat.git>"
    ref: "v9.0.2"
    The spec file is: 
    require 'spec_helper'
    describe 'manhattan::a' do
    it { <http://is_expected.to|is_expected.to> compile }
    end
    It doesn't get much more simple than that. Can anyone shed light on what I might be doing wrong?
    b
    • 2
    • 40
  • b
    IMO the .fixtures.yml should reference the latest branch, not tag
    r
    • 2
    • 1
  • b
    can you show the full error message?
  • y
    JFYI, I spent some time asking qwen.ai about writing unit tests for facts, and it was quite reasonable. At least it was able to answer my question how to mock a 
    kernel
    fact value to make my Linux-confined fact unit test to work on MacOS.
  • y
    It even suggested me to use 
    Facter.clear
    in 
    before :each
    hook, which looks legit but I should recheck the sources/documentation regarding this 🤔
  • y
    ah, when asked about details, it told me that was for Facter 2.x.. so now it’s deprecated 😂