regtest 2.3.0 → 2.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 84ca27fae1d12f7b8616fa32743dbacccfb64fc25b7783b9ec19e7ddc8c8ef2b
-  data.tar.gz: c414dd15ee7d42cd2717caac6530556232a6930c4c107270a16d2138226947c9
+  metadata.gz: a2c3eae05189bc9397839b3116acbfcfc8669d049a25fe5041f10e2c0d10c710
+  data.tar.gz: 32d1023dcd6cc66eea0bb47ede52a474edc026d8e87cefc2a79a50e3c95f07ef
 SHA512:
-  metadata.gz: 5a43f2252a7cb0993eaef29d017e9132b908930fdc298c599f714331053e900bf602655294cfd8fbd24363e01e7053bea6cff90fd2ff11ba7afcdafa6277bbbf
-  data.tar.gz: b3b77f936f251b850246799aa4a0eb01adead35ad758f9e8fefa6c9d02cc00d4017905af2b08dc822de0ace51e4ebabea1b5c294aaf2d52b86f04183fa2ac48d
+  metadata.gz: 8c47c65c0b8fb2e68b77f742d669f870a665b4777a3466da43c03bee7dc450d1875e67f1fce45098ca2e36d00f30cb7da85043af4c9393095d4d985f85ce0b57
+  data.tar.gz: 8d6afb80fe0584f38783a87b129272c48732d6362a404316afc38c40df6c6b1d8d90c428bebb20e5c881d7766b941f90e982935de2da71953b482443a8451ca5

data/Changelog

@@ -1,3 +1,10 @@
+2.4.1
+Fix a bug when using Regtest::Git.C or Regtest::Git.git_dir with relative
+paths for filenames.
+
+2.4.0
+Add parameter Regtest::Git.C.
+
 2.3.0
 Remove regtest/colorize use regtest/colors instead.
 Add Regtest::Git.work_tree and Regtest::Git.git_dir to be more flexible when

data/README.md

@@ -282,12 +282,14 @@ workflow and environment it should not be checked into your SCM.
 If you use the git plugin (`require 'regtest/git'`) there will be two options
 you can set:
 
+* `Regtest::Git.C`
 * `Regtest::Git.git_dir`
 * `Regtest::Git.work_tree`
 
-which corresponds to the git parameters `--git-dir` and `--work-path`. Which
-could be helpful if you run `regtest` from inside an other git repository than
-your regtest files. Have a look at the git documentation for more details.
+which corresponds to the git parameters `-C`, `--git-dir` and `--work-tree`.
+Which could be helpful if you run `regtest` from inside some other git
+repository than your regtest files. Have a look at the git documentation for
+more details.
 
 As said above: this should also be done in a local `.regtestrc` file.
 

data/lib/regtest/git.rb

@@ -15,6 +15,9 @@ begin
       # Redefine Regtest.check_results.
       def check_results
         output_files = Regtest.results.keys
+        if Git.C || Git.work_tree
+          output_files.map! {|fn| File.expand_path(fn)}
+        end
         if output_files.empty?
           report "\nNothing to do.", type: :success
           return :success
@@ -46,6 +49,9 @@ begin
       end
 
       class << self
+        # git parameter +-C+
+        attr_accessor :C
+
         # git parameter +--work-tree+
         attr_accessor :work_tree
 
@@ -57,11 +63,15 @@ begin
 
       def git_global_args
         args = []
+        if c = Regtest::Git.C
+          args <<  '-C'
+          args << c
+        end
         if wt = Regtest::Git.work_tree
           args << format('--work-tree=%s', wt)
         end
-        if gt = Regtest::Git.git_dir
-          args << format('--git-dir=%s', gt)
+        if gd = Regtest::Git.git_dir
+          args << format('--git-dir=%s', gd)
         end
         args
       end

data/lib/regtest/version.rb

@@ -2,5 +2,5 @@
 # frozen_string_literal: true
 
 module Regtest
-  VERSION = '2.3.0'
+  VERSION = '2.4.1'
 end

data/regtest.gemspec

@@ -1,5 +1,5 @@
 # -*- encoding: utf-8 -*-
-# stub: regtest 2.3.0 ruby lib
+# stub: regtest 2.4.1 ruby lib
 #
 # This file is automatically generated by rim.
 # PLEASE DO NOT EDIT IT DIRECTLY!
@@ -7,12 +7,12 @@
 
 Gem::Specification.new do |s|
   s.name = "regtest"
-  s.version = "2.3.0"
+  s.version = "2.4.1"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]
   s.authors = ["Jan Friedrich"]
-  s.date = "2024-09-12"
+  s.date = "2024-09-14"
   s.description = "This library supports a very simple way to do regression testing with Ruby. It\nis not limited to Ruby projects you can use it also in other contexts where you\ncan extract data with Ruby.\n\nYou write Ruby scripts with samples. Run these and get the sample results as\nresults files besides your scripts. Check both the scripts and the results\nfiles in you Source Code Management System (SCM). When you run the scrips on a\nlater (or even previous) version of your code a simple diff show you if and how\nthe changes in your code or environment impact the results of your samples.\n\nThis is not a replacement for unit testing but a complement: You can produce a\nlot of samples with a small amount of Ruby code (e.g. a large number of\ncombinations of data).\n"
   s.email = "janfri26@gmail.com"
   s.files = ["./.aspell.pws", "Changelog", "Gemfile", "LICENSE", "README.md", "Rakefile", "lib/regtest", "lib/regtest.rb", "lib/regtest/colors.rb", "lib/regtest/git.rb", "lib/regtest/task.rb", "lib/regtest/version.rb", "regtest.gemspec"]

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: regtest
 version: !ruby/object:Gem::Version
-  version: 2.3.0
+  version: 2.4.1
 platform: ruby
 authors:
 - Jan Friedrich
 bindir: bin
 cert_chain: []
-date: 2024-09-12 00:00:00.000000000 Z
+date: 2024-09-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake