%global _empty_manifest_terminate_build 0 Name: python-qecore Version: 3.18 Release: 1 Summary: DesktopQE Tool for unified test execution License: GPLv3 URL: https://gitlab.com/dogtail/qecore Source0: https://mirrors.aliyun.com/pypi/web/packages/a1/30/bcc8b685721ffbd778787d96b9e46bf986297f6aa52500b9ec4d17d6d7fc/qecore-3.18.tar.gz BuildArch: noarch Requires: python3-behave Requires: python3-behave-html-formatter Requires: python3-behave-html-pretty-formatter Requires: python3-dasbus Requires: python3-termcolor %description ## qecore [![Build Status](https://img.shields.io/gitlab/pipeline/dogtail/qecore)](https://gitlab.com/dogtail/qecore/-/pipelines) [![PyPI Version](https://img.shields.io/pypi/v/qecore)](https://pypi.org/project/qecore/) The future goal for qecore is for it to become project template for automation testing. As of now the qecore provides a lot of quality of life features for GNOME Desktop testing. It can be described as a sandbox of sorts for test execution. Paired with behave and dogtail this project serves as a useful tool for test execution with minimal required setup. [Project Documentation in gitlab Pages](https://dogtail.gitlab.io/qecore/index.html) - build by CI pipelines on every change ### Execute unit tests Execute the tests (from the project root directory) on machine with dogtail: ```bash rm -f /tmp/qecore_version_status.txt rm -f dist/*.whl python3 -m build python3 -m pip install --force-reinstall --upgrade dist/qecore*.whl sudo -u test scripts/qecore-headless "behave -f html-pretty -o /tmp/report_qecore.html -f plain tests/features" ``` You can use `-f pretty` instead of `-f plain` to get colored output. The standard output should not contain any python traceback, produced HTML should be complete (after first scenario there is `Status`). %package -n python3-qecore Summary: DesktopQE Tool for unified test execution Provides: python-qecore BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-qecore ## qecore [![Build Status](https://img.shields.io/gitlab/pipeline/dogtail/qecore)](https://gitlab.com/dogtail/qecore/-/pipelines) [![PyPI Version](https://img.shields.io/pypi/v/qecore)](https://pypi.org/project/qecore/) The future goal for qecore is for it to become project template for automation testing. As of now the qecore provides a lot of quality of life features for GNOME Desktop testing. It can be described as a sandbox of sorts for test execution. Paired with behave and dogtail this project serves as a useful tool for test execution with minimal required setup. [Project Documentation in gitlab Pages](https://dogtail.gitlab.io/qecore/index.html) - build by CI pipelines on every change ### Execute unit tests Execute the tests (from the project root directory) on machine with dogtail: ```bash rm -f /tmp/qecore_version_status.txt rm -f dist/*.whl python3 -m build python3 -m pip install --force-reinstall --upgrade dist/qecore*.whl sudo -u test scripts/qecore-headless "behave -f html-pretty -o /tmp/report_qecore.html -f plain tests/features" ``` You can use `-f pretty` instead of `-f plain` to get colored output. The standard output should not contain any python traceback, produced HTML should be complete (after first scenario there is `Status`). %package help Summary: Development documents and examples for qecore Provides: python3-qecore-doc %description help ## qecore [![Build Status](https://img.shields.io/gitlab/pipeline/dogtail/qecore)](https://gitlab.com/dogtail/qecore/-/pipelines) [![PyPI Version](https://img.shields.io/pypi/v/qecore)](https://pypi.org/project/qecore/) The future goal for qecore is for it to become project template for automation testing. As of now the qecore provides a lot of quality of life features for GNOME Desktop testing. It can be described as a sandbox of sorts for test execution. Paired with behave and dogtail this project serves as a useful tool for test execution with minimal required setup. [Project Documentation in gitlab Pages](https://dogtail.gitlab.io/qecore/index.html) - build by CI pipelines on every change ### Execute unit tests Execute the tests (from the project root directory) on machine with dogtail: ```bash rm -f /tmp/qecore_version_status.txt rm -f dist/*.whl python3 -m build python3 -m pip install --force-reinstall --upgrade dist/qecore*.whl sudo -u test scripts/qecore-headless "behave -f html-pretty -o /tmp/report_qecore.html -f plain tests/features" ``` You can use `-f pretty` instead of `-f plain` to get colored output. The standard output should not contain any python traceback, produced HTML should be complete (after first scenario there is `Status`). %prep %autosetup -n qecore-3.18 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-qecore -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Jun 09 2023 Python_Bot - 3.18-1 - Package Spec generated