public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jerry James <loganjerry@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/JUnitParams] epel10: Reflow the description text
Date: Thu, 16 Jul 2026 21:36:11 GMT [thread overview]
Message-ID: <178423777148.1.5212636004907215613.rpms-JUnitParams-ddb4e6f310f5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/JUnitParams
Branch : epel10
Commit : ddb4e6f310f520fc50b5693048111b84476713fb
Author : Jerry James <loganjerry@gmail.com>
Date : 2026-01-12T13:29:21-07:00
Stats : +9/-10 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/JUnitParams/c/ddb4e6f310f520fc50b5693048111b84476713fb?branch=epel10
Log:
Reflow the description text
---
diff --git a/JUnitParams.spec b/JUnitParams.spec
index abc396b..a0cf00f 100644
--- a/JUnitParams.spec
+++ b/JUnitParams.spec
@@ -43,21 +43,20 @@ BuildArch: noarch
ExclusiveArch: %{java_arches} noarch
%description
-The JUnitParams project adds a new runner to JUnit and provides much
-easier and more readable parameterized tests for JUnit >= 4.12.
+The JUnitParams project adds a new runner to JUnit and provides much easier
+and more readable parameterized tests for JUnit >= 4.12.
The main differences with the standard JUnit Parameterized runner are:
- more explicit - params are in test method params, not class fields
- less code - you don't need a constructor to set up parameters
- you can mix parameterized with non-parameterized methods in one class
-- params can be passed as a CSV string or from a parameters provider
- class
-- parameters provider class can have as many parameters providing
- methods as you want, so that you can group different cases
-- you can have a test method that provides parameters (no external
- classes or statics anymore)
-- you can see actual parameter values in your IDE (in JUnit's
- Parameterized, it's only consecutive numbers of parameters)
+- params can be passed as a CSV string or from a parameters provider class
+- parameters provider class can have as many parameters providing methods as
+ you want, so that you can group different cases
+- you can have a test method that provides parameters (no external classes or
+ statics anymore)
+- you can see actual parameter values in your IDE (in JUnit's Parameterized,
+ it's only consecutive numbers of parameters)
%prep
%autosetup -n %{name}-%{name}-%{version} -p1
reply other threads:[~2026-07-16 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178423777148.1.5212636004907215613.rpms-JUnitParams-ddb4e6f310f5@fedoraproject.org \
--to=loganjerry@gmail.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox