* CLEAN-UP: Remove unused rake tasks
missing, kitchen and version tasks are not used
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* CLEAN-UP: Remove functional rake test
test:default covers both unit and functional tests
default was introduced to cover both functional and unit in PR #4102
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* CLEAN-UP: Remove unused docs related tasks
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* CLEAN-UP: Remove tasks/* from expeditor config
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* REVERT: Undo deletion of functional test
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* RECOVER: Retain docs:cli task
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* UNDO: Revert changes to config
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* CHORE: Add reference to this PR in note for future use
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
---------
Signed-off-by: Sonu Saha <sonu.saha@progress.com>
* add ruby test 3.1 in verify pipeline
Signed-off-by: jayashri garud <jgarud@msystechnologies.com>
* updating rubygem to 3.3.3
Signed-off-by: jayashri garud <jgarud@msystechnologies.com>
* Test fixture plugin files for ABI 3.1.0
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
* Use kwargs to match new calling style for ERB in ruby 2.7 and 3.0
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
* Allow Date and Time data types, needed for waivers, since safe load is now the default for YAML
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
* Use Time.parse, not Time.new since the rules tightened for what you can pass the constructor for waiver dates
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
* Add ruby platform debug message to test parallel output
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
* Conditionalize permitted_classes in inputs yaml_load for <= 3.1.x only
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
* In ruby 3.1.0 net/pop3 is no more a default gem and that will require us to add it in Gemfile so trying with the byebug gem which we are bundling already
Signed-off-by: Vasu1105 <vasundhara.jagdale@chef.io>
* CFINSPEC-166 Updated url fetcher to handle Net::OpenTimeout Exception on Windows
Signed-off-by: Vasu1105 <vasundhara.jagdale@chef.io>
Co-authored-by: Clinton Wolfe <clintoncwolfe@gmail.com>
Co-authored-by: Vasu1105 <vasundhara.jagdale@chef.io>
The task has been disabled for a while and the docs are totally out of date. Nuke this all and save ourselves some deps in the gemfile.
Signed-off-by: Tim Smith <tsmith@chef.io>
[miah@awakening inspec]$ bundle exec rake
rake aborted!
NameError: uninitialized constant Faraday::Error::ClientError
Did you mean? Faraday::ClientError
/home/miah/projects/github/.gems/inspec/ruby/2.6.0/gems/octokit-4.14.0/lib/octokit/middleware/follow_redirects.rb:14:in `<module:Middleware>'
/home/miah/projects/github/.gems/inspec/ruby/2.6.0/gems/octokit-4.14.0/lib/octokit/middleware/follow_redirects.rb:11:in `<module:Octokit>'
...
/home/miah/projects/github/inspec/tasks/maintainers.rb:27:in `require'
...
(See full trace by running task with --trace)
Signed-off-by: Miah Johnson <miah@chia-pet.org>
Replaces the now-yanked passgen gem with something available in the Ruby
standard library. Why `.alphanumeric(72)`? This method will reliably
crank out 72-character strings that meet the upper, lower, and numeric
requirement of Azure.
From the docs on the Azure terraform provider:
> NOTE: admin_password must be between 6-72 characters long and must
> satisfy at least 3 of password complexity requirements from the
> following:
> 1. Contains an uppercase character
> 2. Contains a lowercase character
> 3. Contains a numeric digit
> 4. Contains a special character
So, this should suffice.
Signed-off-by: Robb Kidd <robb@thekidds.org>
moved lint, and 'test' under the `test:` namespace.
moved 'test' to `test:default`, lint is now `test:lint`.
Signed-off-by: Miah Johnson <miah@chia-pet.org>
Extracted a GLOBS const so it can be reused and only updated in one
place.
Added test:list that prints out all known test files.
Changed test:isolated to use the glob, AND to use system (sh would
fail out on the first failing test, so much of the looping mechanism
was redundant. I also changed the loop to run all of the tests
regardless of outcome, so you can see all the failures.
Signed-off-by: Ryan Davis <zenspider@chef.io>
Before you had to kick off kitchen via Rake as the Rake task build the local gem we injected into the cookbook. Now we do it within Test Kitchen using a feature that didn't exist when this was all written. Also --output is your friend and greatly reduces the complexity of all this.
Signed-off-by: Tim Smith <tsmith@chef.io>
+ Turn off verbosity in Rakefile by default. Use `rake V=1` to turn back on.
+ MiniTest -> Minitest everywhere.
+ MiniTest::Unit::TestCase -> Minitest::Test everywhere.
+ Updated minitest doco urls to official and up-to-date site.
+ Normalize requires. Only needs "minitest/autorun" and "minitest/pride".
Signed-off-by: Ryan Davis <zenspider@chef.io>
