fedora-docs-l10n/ci/master/pages/tests — French @ Fedora Weblate: tests

Zen

Translation

English type: Labeled list

French

Needs editing

Skip

	English	French	Actions
	\|Quick links to automated test reports \|https://fedoraproject.org/wiki/CI/Tests/stat[stat] \|https://fedoraproject.org/wiki/CI/Tests/new-stat[new-stat] \|https://fedoraproject.org/wiki/CI/Tests/stat_atomic[stat atomic] \|https://fedoraproject.org/wiki/CI/Tests/recent_builds[recent builds] \|https://fedoraproject.org/wiki/CI/Tests/stat_everything_subset[stat everything subset] \|https://fedoraproject.org/wiki/CI/Tests/stat_fedoraserver[stat fedoraserver]
	Enabling
	Tests may be written in different ways, but are exposed and invoked in a standard way as defined by the xref:standard-test-interface.adoc[Standard Test Interface] directly in the package https://src.fedoraproject.org/projects/rpms/%2A[git repository]. It is also possible to enable pipeline for the tests namespace, see xref:share-test-code.adoc#_testing_tests[Testing Tests] for details. To start working on tests you can clone a package repo directly:
	git clone https://src.fedoraproject.org/rpms/qrencode.git
	You can also use the `fedpkg` to clone the repo. See the https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/[Package Maintenance Guide] for more info about the tool:
	fedpkg clone -a qrencode
	Tests are enabled by including the `tests.yml` file under the `tests` directory:
	cd qrencode/tests cat tests.yml
	Tests are wrapped or written as http://docs.ansible.com/ansible/playbooks.html[Ansible playbooks]. Here is an example of a simple playbok which enables a single `smoke` test of the `qrencode` package:
	- hosts: localhost roles: - role: standard-test-beakerlib tags: - classic - container - atomic tests: - smoke required_packages: - qrencode - file
	Let's now briefly look at the playbook to see which variables are defined in order to enable the smoke test:
	role	rôle
	this test uses role `standard-test-beakerlib` from xref:standard-test-roles.adoc[Standard Test Roles] to run a BeakerLib test
	tags	tags
	all three test subjects (xref:standard-test-roles.adoc#_classic[classic] rpm, docker xref:standard-test-roles.adoc#_container[container] and xref:standard-test-roles.adoc#_atomic[atomic] host) are relevant for this test
	tests	tests
	list of tests to be executed (here we have just a single smoke test)
	required_packages
	list of rpm packages required for test execution
	It is possible to separate tests into multiple playbooks, each of them can represent a test or a part of a test. Testing system will run each playbook matching the glob `tests/tests*.yml` separately in a clean environment. Optionally you can have multiple playbooks without the `tests` prefix and link them from the `tests.yml` file. Let's have a look at the https://src.fedoraproject.org/rpms/gzip/blob/rawhide/f/tests[gzip] example:
	> fedpkg clone -a gzip Cloning into 'gzip'...
	> cd gzip/tests/ > ls test-simple test_simple.yml tests.yml
	> cat tests.yml
	include: test_simple.yml
	Executing
	Before running tests make sure you have the following dependencies installed on your system:
	dnf install ansible python2-dnf libselinux-python standard-test-roles
	Although some playbooks may function without sudo, tests are always invoked as root. The test itself may set up users and/or drop permissions if a part of that test. But in general be sure to be root when invoking tests.
	Tests may modify or destroy your environment + It's recommended to use a virtual machine for testing to prevent any unwated changes performed by the test to your system.
	Running a test directly on the current system is easy:
	ansible-playbook tests.yml

Loading…

grimst

Translation changed

English

French 1 character edited Current translation Translated

a year ago

grimst

Suggestion accepted

English

French 4 characters edited Translated

a year ago

anonymous

Suggestion added

English

French 4 characters edited

2 years ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	French
No related strings found in the glossary.

797724 String information

Source string description

type: Labeled list

Flags

no-wrap

Source string location

pages/tests.adoc:62

String age

4 years ago

Last updated

a year ago

Source string age

4 years ago

Translation file

po/fr/master/pages/tests.po, string 17

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.