[rpms/JUnitParams] epel10: Added the README

[releng bot <admin+relengbot@fedoraproject.org>]

A new commit has been pushed.

Repo   : rpms/JUnitParams
Branch : epel10
Commit : a9da7377a9bee89e7c6feab38f002177d0c8b917
Author : releng bot <admin+relengbot@fedoraproject.org>
Date   : 2023-12-04T16:02:27+00:00
Stats  : +19/-0 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/JUnitParams/c/a9da7377a9bee89e7c6feab38f002177d0c8b917?branch=epel10

Log:
Added the README

---
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..9d0feaf
--- /dev/null
+++ b/README.md
@@ -0,0 +1,19 @@
+# JUnitParams
+
+The [JUnitParams project](https://pragmatists.github.io/JUnitParams/) adds a
+new runner to [JUnit](https://junit.org/junit4/) and provides much easier and
+more readable parameterized tests for JUnit >= 4.12.
+
+The main differences with the standard JUnit
+[Parameterized](https://github.com/junit-team/junit4/wiki/Parameterized-tests)
+runner are:
+- more explicit &mdash; params are in test method params, not class fields
+- less code &mdash; 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)
\ No newline at end of file