junit-pioneer VS ByteLegend

Schedule (all times UTC): // hosts: 🦁 Ana, 🤖 Nicolai, 🧑🏾‍🏫 Shar // topics: 💻 live code/exploration, 📣 talk, 💬 conversation, 🎮 game: 🤖💻 04:00 working on JUnit Pioneer - https://junit-pioneer.org/ 🤖📣 07:00 "Data-Oriented Programming in Java (21)" 🤖💬 08:00 Gavin Bierman: pattern matching 🤖💻 09:00 exploring JEPs on disallowing dynamic agents (451) and platform integrity (draft 8305968) 🤖💬 10:00 Ron Pressler: platform integrity and the on-ramp 🤖💻 11:00 exploring structured concurrency 🦁📣 12:00 "Growing up with Java" 🦁🎮 13:30 Byte Legend - https://bytelegend.com/ 🧑🏾‍🏫📣 16:00 "Java State of the Union" & "Why Community Matters" 🧑🏾‍🏫💬 17:00 Pratik Patel, Mohammed Aboullaite, Venkat Subramaniam, Andres Almiray, Ixchel Ruiz, Vincent Mayers 🤖💬 19:00 Brian Goetz 🤖💬 20:00 Gunnar Morling 🤖📣 21:00 "Java Next" 🤖💻 22:00 investigating the state of Valhalla 🤖💻 23:00 experimenting with string templates 🤖📣 00:00 talk: "Why don't they just... ?!" 🤖🎮 01:00 Slay the Spire (written in Java!) 🤖💻 02:00 modding Slay the Spire 🤖📣 05:00 "The SolutionFactory To Java's Problems" 🤖📣 06:00 "From Idea to IDE" 🤖💬 07:00 just chatting / AMA 🤖🛏️ 08:00 end

There is a cool library called JUnit Pioneer. It's an extension pack that includes some features that vanilla JUnit lacks. These are cartesian product tests, JSON argument parameterized source, retrying tests and many others. But I'm particularly interested in Issue annotation. Look at the code example below:

junit-pioneer

Schedule (all times UTC): // hosts: 🦁 Ana, 🤖 Nicolai, 🧑🏾‍🏫 Shar // topics: 💻 live code/exploration, 📣 talk, 💬 conversation, 🎮 game: 🤖💻 04:00 working on JUnit Pioneer - https://junit-pioneer.org/ 🤖📣 07:00 "Data-Oriented Programming in Java (21)" 🤖💬 08:00 Gavin Bierman: pattern matching 🤖💻 09:00 exploring JEPs on disallowing dynamic agents (451) and platform integrity (draft 8305968) 🤖💬 10:00 Ron Pressler: platform integrity and the on-ramp 🤖💻 11:00 exploring structured concurrency 🦁📣 12:00 "Growing up with Java" 🦁🎮 13:30 Byte Legend - https://bytelegend.com/ 🧑🏾‍🏫📣 16:00 "Java State of the Union" & "Why Community Matters" 🧑🏾‍🏫💬 17:00 Pratik Patel, Mohammed Aboullaite, Venkat Subramaniam, Andres Almiray, Ixchel Ruiz, Vincent Mayers 🤖💬 19:00 Brian Goetz 🤖💬 20:00 Gunnar Morling 🤖📣 21:00 "Java Next" 🤖💻 22:00 investigating the state of Valhalla 🤖💻 23:00 experimenting with string templates 🤖📣 00:00 talk: "Why don't they just... ?!" 🤖🎮 01:00 Slay the Spire (written in Java!) 🤖💻 02:00 modding Slay the Spire 🤖📣 05:00 "The SolutionFactory To Java's Problems" 🤖📣 06:00 "From Idea to IDE" 🤖💬 07:00 just chatting / AMA 🤖🛏️ 08:00 end

The closest thing that I can think of is https://bytelegend.com/.

Yes, there are tests. They are just not opensource yet. Have you checked the GitHub actions page? Every commit goes through a lot of checks and tests, including unit tests, integration tests, browser tests, and e2e tests. https://github.com/ByteLegend/ByteLegend/actions/workflows/check.yml

> By design, you should be open "IDE" chest to get enough gold to go to Git Island. Didn't you open that chest?

I now see there was a circle with a key that I was supposed to press to open the chest and get the gold. It wasn't obvious and since it didn't hinder progression I didn't realize like I had/should/could click that.

> ``` I'm learning programming in a game, come to JavaIsland coordinate (BJ, 94), open the chest with my invitation code 5ZwPT6OWwipmHRG, you and me can both get 500 gold. Join me at ByteLegend https://bytelegend.com ! ```

Where was I supposed to find this text?

> When you do the challenge, you actually create a pull request on github. There's some comments in the pull request telling you what's the issue in you code. However, I shouldn't have told you this if this is a well-desgined game UI. Thanks for the feedback!

Nothing in the PR comments indicates there is anything wrong:

"Your answer is being tested by CI. Click here to see more details."

"Congrats! Your answer passed our CI test. I will merge the pull request for you. Please keep challenging and enjoy programming!"

https://github.com/ByteLegendQuest/java-fix-method-passing-v...

I could only find the issue by clicking one of links for details and looking into the "check problems with code" logs to find that commit was missing a new line at the end of the file. Seems unlikely a programming beginner would look that far without being prompted.