Allow for custom test class names

[artamonovkirill]

Not all tests are executed (the @Ignore annotation is not removed) if the test class name is different from the slug name. For example, for linked-list the expected slug-based test class name is LinkgedListSpec, and the actual test class name is DoubleLinkedListSpec
This PR changes the logic to try fetching the class name from .meta/config.json first and fall back to the slug-derived test class name if it fails.

Similar to exercism/scala-test-runner#38

[github-actions]

Hello. Thanks for opening a PR on Exercism 🙂

We ask that all changes to Exercism are discussed on our Community Forum before being opened on GitHub. To enforce this, we automatically close all PRs that are submitted. That doesn't mean your PR is rejected but that we want the initial discussion about it to happen on our forum where a wide range of key contributors across the Exercism ecosystem can weigh in.

You can use this link to copy this into a new topic on the forum. If we decide the PR is appropriate, we'll reopen it and continue with it, so please don't delete your local branch.

If you're interested in learning more about this auto-responder, please read this blog post.

---

Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

[vaeng]

I don't know enough groovy to do more than reopening this pr. If you have not done so already you might find some better informed maintainers on the forums.

[artamonovkirill]

I don't know enough groovy to do more than reopening this pr. If you have not done so already you might find some better informed maintainers on the forums.

The only Groovy code is an equivalent of assert false (= always fail) test; the rest is bash script changes. Maybe @IsaacG can share some improvements? 🙏

[IsaacG]

Is there any particular reason this uses sh and not bash?

[artamonovkirill]

🤷 gradlew is a wrapper file generated by Gradle; I just copied and pasted the existing one from other directories.
But your question got me wondering if we need any gradle files in the tests/ subfolders - as the test runner uses Maven, not Gradle. Let me try removing the wrappers with build.gradle files - it might be just some remaining artifacts from earlier development.

[artamonovkirill]

I think it indeed is:

• artamonovkirill@2b536e5 added the gradle files
• artamonovkirill@2b536e5 later switched to maven

[artamonovkirill]

Tested locally without gradle files - it works, as expected; push the commit to this PR

[artamonovkirill]

@IsaacG sorry I didn't mention anywhere that gradlew is an autogenerated file that I copy-pasted from the other test, and you had to review it 😞
Here's the source of it: https://github.com/gradle/gradle/blob/master/gradlew (although the one in the test runner was probably a way older version)

[IsaacG]

@IsaacG sorry I didn't mention anywhere that gradlew is an autogenerated file that I copy-pasted from the other test, and you had to review it 😞

Not a big deal :)

[IsaacG]

Approved. Let me know if you lack merge permissions and need help.

[artamonovkirill]

Approved. Let me know if you lack merge permissions and need help.

Thank you 🙌 I indeed do not have merge permissions 😞