# Generated from assert_generator-0.1.5.gem by gem2rpm -*- rpm-spec -*-
%global gem_name assert_generator

Name: rubygem-%{gem_name}
Version: 0.1.5
Release: 1%{?dist}
Summary: An assert generating gem
License: MIT
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
# BuildRequires: rubygem(minitest) >= 5.0
# BuildRequires: rubygem(minitest) < 6
# BuildRequires: rubygem(mocha) >= 1.9
# BuildRequires: rubygem(mocha) < 2
# BuildRequires: rubygem(shoulda) >= 3.6
# BuildRequires: rubygem(shoulda) < 4
# BuildRequires: rubygem(binding_of_caller)
# BuildRequires: rubygem(rubocop) >= 0.76
# BuildRequires: rubygem(rubocop) < 1
# BuildRequires: rubygem(simplecov) >= 0.17
# BuildRequires: rubygem(simplecov) < 1
# BuildRequires: rubygem(simplecov) >= 0.17.1
BuildArch: noarch

%description
Generate assert code from a result inside a unit or integration test.
This is useful if you have code that you've spiked or eyeballed as 'working'
and you'd like to produce some assertions,
without editing the output of pretty-inspect manually or making it all up.


%package doc
Summary: Documentation for %{name}
Requires: %{name} = %{version}-%{release}
BuildArch: noarch

%description doc
Documentation for %{name}.

%prep
%setup -q -n %{gem_name}-%{version}

%build
# Create the gem as gem install only works on a gem file
gem build ../%{gem_name}-%{version}.gemspec

# %%gem_install compiles any C extensions and installs the gem into ./%%gem_dir
# by default, so that we can move it into the buildroot in %%install
%gem_install

%install
mkdir -p %{buildroot}%{gem_dir}
cp -a .%{gem_dir}/* \
        %{buildroot}%{gem_dir}/



%check
pushd .%{gem_instdir}
# ruby -e 'Dir.glob "./test/**/*_test.rb", &method(:require)'
popd

%files
%dir %{gem_instdir}
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}


%changelog
* Sun Sep 12 2021 mockbuilder - 0.1.5-1
- Initial package