Calling `invoke` directly in RSpec breaks with required class_options, even when they are provided.

[WriterZephos]

I am trying to test my Thor tasks and running into an issue. I have the following option defined on my Thor class:

class_option :file_path, required: true, type: :string, aliases: :f

and in my tests I have:

  let(:options){
    {
      :file_path => "v_1.0.0/chapter_1/content.md"
    }
  }
  
  ...
  
  
    it "does a dry run render of html" do
      expect{ ::MyThorTask.new.invoke(:foo, [], options) }.to output(...).to_stdout
    end

Which give me this error:

     Thor::RequiredArgumentMissingError:
       No value provided for required options '--file-path'

But I can run the Thor task in the terminal just fine, so I think there is something broken with invoke.

[kumar1202]

Facing the same issue for this scenario, I had to set the required parameter for that option as false, and add a custom validation logic to check if all of my required parameters were passed correctly to avoid this spec issue.

Let me try to find more about the root cause.

[JoelTowell]

I believe that there is at least one significant issue with calling:

::MyThorTask.new.invoke(:foo, [], options)

The problem is that you are initialising the class before providing the required class_option. The result is that the presence of the option is validated before the command can be invoked, which is why you are seeing this error.

If you want to invoke MyThorTask from another Thor command, you can use:

invoke MyThorTask, :foo, [], options

In a spec, it is probably better to use:

MyThorTask.new([], options).foo

Or, if you want to test the CLI dispatch path:

MyThorTask.start(["foo", "--file-path", path])

I don't think this is actually a bug, and the issue should probably be closed.