diff --git a/Test-Command-0.11.tar.gz b/Test-Command-0.11.tar.gz
new file mode 100644
index 0000000..c6819b8
Binary files /dev/null and b/Test-Command-0.11.tar.gz differ
diff --git a/perl-Test-Command.spec b/perl-Test-Command.spec
new file mode 100644
index 0000000..d387bf9
--- /dev/null
+++ b/perl-Test-Command.spec
@@ -0,0 +1,51 @@
+Name:           perl-Test-Command
+Version:        0.11
+Release:        1
+Summary:        Test routines for external commands
+License:        GPL+ or Artistic
+URL:            https://metacpan.org/release/Test-Command
+Source0:        https://cpan.metacpan.org/authors/id/D/DA/DANBOO/Test-Command-%{version}.tar.gz
+BuildArch:      noarch
+BuildRequires:  perl-interpreter
+BuildRequires:  perl-generators
+BuildRequires:  perl(base)
+BuildRequires:  perl(Carp)
+BuildRequires:  perl(Config)
+BuildRequires:  perl(ExtUtils::MakeMaker)
+BuildRequires:  perl(File::Temp)
+BuildRequires:  perl(FindBin)
+BuildRequires:  perl(Module::Build)
+BuildRequires:  perl(strict)
+BuildRequires:  perl(Test::Builder::Module)
+BuildRequires:  perl(Test::More)
+BuildRequires:  perl(warnings)
+Requires:       perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))
+
+%description
+Test::Command intends to bridge the gap between the well tested functions
+and objects you choose and their usage in your programs. By examining the
+exit status, terminating signal, STDOUT and STDERR of your program you can
+determine if it is behaving as expected.
+
+%prep
+%setup -q -n Test-Command-%{version}
+
+%build
+%{__perl} Build.PL installdirs=vendor
+./Build
+
+%install
+./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+./Build test
+
+%files
+%doc Changes README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Sun Oct 09 2022 wangziliang <wangziliang@kylinos.cn> - 0.11-1
+- Package init