Open shawnlaffan opened 7 years ago
You have to change the framework to "Custom" to be able to change the command. This is by design.
Thanks for clarifying.
There's no mention of custom in the docs. http://docs.komodoide.com/Manual/unittest
Maybe this would be clearer if there were a tooltip or similar?
I think this is confusing too. If I know I'm using Perl prove (or any other support suite) then I wouldn't think to select a Custom command when I should "clearly" select Perl prove. Seems unnecessary to disable the Command field.
I'll add a description under the command field "You can customize the command by using a custom framework", or something along those lines.
@shawnlaffan sorry about that, I will update the docs tomorrow.
No worries @naatan
Regards, Shawn.
Short Summary
Unable to change the command arguments in the Unittest Config window.
My use case is Perl using prove. I have main tests under the t/ dir, author tests under xt/, as well as some others in subdirs under etc/. I only want to run those in t/, but the -r option being on by default finds and runs all test files under the target dir.
Setting the target dir to t/ is a workaround for now (although then I hit issues with loss of responsiveness and high CPU usage, but that's for a separate issue).
Steps to Reproduce
Open the Unittest Config dialog, use settings similar to those in the image below.
Expected results
Should be able to edit the command args in the Advanced section.
Actual results
The command option in the Advanced section is greyed out.
Also applies under SafeMode.
Platform Information
Komodo IDE Komodo 10.2 Windows 10
Additional Information