How to Use the Command 'tmt try' (with Examples)

The tmt try command is a versatile tool designed to facilitate quick testing and development of software projects. It allows developers to easily experiment with different tests, environments, and configurations. This command is extremely useful for testing across varied systems, giving developers immediate feedback on their code changes. Whether you’re a seasoned developer or a newcomer trying to validate your software in different environments, tmt try offers a streamlined way to conduct tests without setting up extensive testing architectures. Below are several examples illustrating different use cases of the tmt try command.

Use case 1: Quickly Experiment with the Default Provision Method

Code:

tmt try

Motivation:
This basic command is ideal for developers who want to start a quick experiment using the default provisioning method offered by the Test Management Tool (tmt). It serves as a preliminary check to ensure everything is set up correctly in the environment.

Explanation:
This command uses the default configuration with no specific tests in the current working directory (CWD). It provides a simple way to verify connectivity, dependencies, and basic environment setup without any additional parameters or configurations.

Example Output:

Discovering tests...
Running tests...
No tests found to execute.

Use case 2: Run a Test in the Current Working Directory

Code:

cd path/to/test && tmt try

Motivation:
Running tests in a particular directory is crucial when focusing on specific segments of a project. This command allows developers to conduct tests directly in the directory where the test files reside, avoiding the need for additional path specifications.

Explanation:
By navigating to the specific directory (cd path/to/test), you set the working context for the tmt try command. This means it will look for and execute tests found in the present directory, using its default provisioning settings.

Example Output:

Discovering tests...
found: /tests/test1
Running '/tests/test1'...
...
Test results: 1 test run, 1 test passed

Use case 3: Use a Specific Operating System

Code:

tmt try fedora-41

Motivation:
It is often necessary to validate that software behaves correctly across different operating systems. This command lets you specify a particular operating system, helping ensure compatibility and stability on Fedora 41.

Explanation:
The command tmt try fedora-41 specifies ‘fedora-41’ as the OS to provision during the testing process. The system uses this OS to provision and run the tests, guaranteeing that the environment aligns with this specific OS version’s attributes.

Example Output:

Provisioning test environment with fedora-41...
Discovering tests...
Running tests...
...
All tests completed successfully on fedora-41.

Use case 4: Select Both Custom Image and Provision Method

Code:

tmt try fedora@container

Motivation:
Deploying to containers is a common scenario in modern software development. This example is tailored for situations where you want to test how the application performs in a container running Fedora.

Explanation:
The command uses the fedora@container argument to specify that the testing should be conducted in a Fedora container. This integrates Fedora as the operating system with a containerized provision method, reflecting an increasingly common deployment practice in the industry.

Example Output:

Provisioning Fedora container...
Discovering tests...
Running tests...
...
Tests executed successfully in Fedora container.

Use case 5: Select Tests with a Custom Filter

Code:

tmt try --test feature

Motivation:
Filtering by specific tests can speed up the process when only a subset of tests is relevant. Developers working on a particular feature can utilize this filter to run only those tests that are tagged or named accordingly.

Explanation:
The --test feature option filters tests based on the keyword ‘feature’. This command will search for and execute tests that match the provided filter criterion, enhancing efficiency and precision in test execution.

Example Output:

Discovering tests...
selected: /tests/feature1
Running '/tests/feature1'...
...
1 test selected based on filter 'feature'
1 test passed

Use case 6: Provision Guest and Wait for Instructions

Code:

tmt try --ask

Motivation:
This use case is helpful during exploratory testing or debugging under a tailored environment setup. Developers can provide real-time input or run manual commands after environment provisioning.

Explanation:
The --ask argument initiates the provisioning and then pauses, prompting the user for further instructions or commands. This is useful for manual interventions or adjustments in the testing setup.

Example Output:

Provisioning environment...
Environment ready. Waiting for further instructions...

Use case 7: Directly Log Into the Guest Without Asking

Code:

tmt try --login

Motivation:
When a quick login to the test environment is needed, such as for debugging purposes or executing manual tests, this command provides direct access without the need for additional confirmation.

Explanation:
The --login flag triggers an automatic login to the guest system created during the provisioning phase. This allows immediate hands-on interventions without intermediate prompts.

Example Output:

Provisioning environment...
Logging into provisioned environment...
Last login: ...
[root@guest ~]#

Use case 8: Display Help

Code:

tmt try --help

Motivation:
Accessing help documentation is often necessary to understand command options or for refreshing knowledge on specific command functionalities. This command provides an overview of available options and usage.

Explanation:
Using the --help option prompts the command-line tool to display documentation regarding its usage, including descriptions of available options and examples, providing a valuable resource for new and existing users.

Example Output:

Usage: tmt try [options]
Options:
  --test [name]  Specify tests to run
  --ask          Provision guest and wait for instructions
  --login        Directly log into the guest
  ...
For more information, visit: https://tmt.readthedocs.io/en/stable/stories/cli.html#try

Conclusion:

tmt try is a powerful yet straightforward tool that simplifies the testing process across diverse environments. By offering a range of options for provisioning systems, running tests, and modifying behaviors, it offers developers flexibility and speed in their testing workflows. These examples demonstrate the command’s utility in various scenarios, making it an invaluable asset for modern software development practices.