How to Install and Uninstall opentest4j Package on openSuSE Tumbleweed
Last updated: February 16,2025
1. Install "opentest4j" package
Learn how to install opentest4j on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
opentest4j
Copied
2. Uninstall "opentest4j" package
This guide covers the steps necessary to uninstall opentest4j on openSuSE Tumbleweed:
$
sudo zypper remove
opentest4j
Copied
3. Information about the opentest4j package on openSuSE Tumbleweed
Information for package opentest4j:
-----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : opentest4j
Version : 1.3.0-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 27.1 KiB
Installed : No
Status : not installed
Source package : opentest4j-1.3.0-1.3.src
Upstream URL : https://github.com/ota4j-team/opentest4j
Summary : Open Test Alliance for the JVM
Description :
Open Test Alliance for the JVM is a minimal common foundation for
testing libraries on the JVM. The primary goal of the project is to
enable testing frameworks like JUnit, TestNG, Spock, etc. and
third-party assertion libraries like Hamcrest, AssertJ, etc. to use a
common set of exceptions that IDEs and build tools can support in a
consistent manner across all testing scenarios -- for example, for
consistent handling of failed assertions and failed assumptions as
well as visualization of test execution in IDEs and reports.
-----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : opentest4j
Version : 1.3.0-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 27.1 KiB
Installed : No
Status : not installed
Source package : opentest4j-1.3.0-1.3.src
Upstream URL : https://github.com/ota4j-team/opentest4j
Summary : Open Test Alliance for the JVM
Description :
Open Test Alliance for the JVM is a minimal common foundation for
testing libraries on the JVM. The primary goal of the project is to
enable testing frameworks like JUnit, TestNG, Spock, etc. and
third-party assertion libraries like Hamcrest, AssertJ, etc. to use a
common set of exceptions that IDEs and build tools can support in a
consistent manner across all testing scenarios -- for example, for
consistent handling of failed assertions and failed assumptions as
well as visualization of test execution in IDEs and reports.