How to Install and Uninstall opentest4j.noarch Package on Oracle Linux 9
Last updated: November 25,2024
1. Install "opentest4j.noarch" package
Please follow the instructions below to install opentest4j.noarch on Oracle Linux 9
$
sudo dnf update
Copied
$
sudo dnf install
opentest4j.noarch
Copied
2. Uninstall "opentest4j.noarch" package
Please follow the steps below to uninstall opentest4j.noarch on Oracle Linux 9:
$
sudo dnf remove
opentest4j.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the opentest4j.noarch package on Oracle Linux 9
Last metadata expiration check: 3:54:34 ago on Thu Feb 15 07:50:05 2024.
Available Packages
Name : opentest4j
Version : 1.2.0
Release : 9.el9
Architecture : noarch
Size : 30 k
Source : opentest4j-1.2.0-9.el9.src.rpm
Repository : ol9_appstream
Summary : Open Test Alliance for the JVM
URL : https://github.com/ota4j-team/opentest4j
License : ASL 2.0
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.
Available Packages
Name : opentest4j
Version : 1.2.0
Release : 9.el9
Architecture : noarch
Size : 30 k
Source : opentest4j-1.2.0-9.el9.src.rpm
Repository : ol9_appstream
Summary : Open Test Alliance for the JVM
URL : https://github.com/ota4j-team/opentest4j
License : ASL 2.0
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.