# Generated from mockley_crew-1.3.9.gem by gem2rpm -*- rpm-spec -*-
%global gem_name mockley_crew

Name: rubygem-%{gem_name}
Version: 1.3.9
Release: 1%{?dist}
Summary: Rock your API integration tests by mocking data into multiple SQLite3 instances
License: MIT
URL: https://github.com/arielschvartz/mockley_crew
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
# BuildRequires: rubygem(sqlite3) = 1.3.13
# BuildRequires: rubygem(pry-rails)
# BuildRequires: rubygem(timecop)
# BuildRequires: rubygem(rspec-rails) >= 3.2
# BuildRequires: rubygem(rspec-rails) < 4
BuildArch: noarch

%description
With Mockley Crew, you can create fake databases to use from your API
consumer. This way, you can isolate the consumer tests by having multiple data
scenarios built on your API.


%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}
# Run the test suite.
popd

%files
%dir %{gem_instdir}
%license %{gem_instdir}/MIT-LICENSE
%{gem_instdir}/app
%{gem_instdir}/config
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%doc %{gem_instdir}/README.md
%{gem_instdir}/Rakefile

%changelog
* Tue Sep 14 2021 mockbuilder - 1.3.9-1
- Initial package