Skip to content

docs: add manual test report for issue #394#437

Open
rutvikraut16 wants to merge 1 commit into
jvondermarck:mainfrom
rutvikraut16:test-report-394
Open

docs: add manual test report for issue #394#437
rutvikraut16 wants to merge 1 commit into
jvondermarck:mainfrom
rutvikraut16:test-report-394

Conversation

@rutvikraut16

Copy link
Copy Markdown

Summary

Performed manual testing of Dinosaur Explorer and documented the results.

Features Tested

  • Game Launch
  • Player Movement
  • Shooting System
  • Enemy Collision
  • Lives System
  • Score System
  • Coin Collection
  • Shield Feature
  • Game Over Screen
  • Restart Functionality

Result

No critical issues were identified during testing.

Related to Issue #394.

@vercel

vercel Bot commented Jun 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
dinosaur-exploder Ignored Ignored Preview Jun 7, 2026 9:51am

@github-actions

github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

✅ Code Formatting Check Passed!

badge

Great job! 🎉 Your code follows the Google Java Style Guide.


🤖 The DinoBot Team 🦖

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 Hello @rutvikraut16, thank you for submitting in Dinosaur Exploder 🦖 PR! To allow your work to be integrated as seamlessly as possible, we advise you to:

  • ✅ Verify your PR is up-to-date with the repository /dinosaur-exploder main branch. If your PR is behind you can update your code by clicking the 'Update branch' button or by running git pull and git merge master locally.
  • ✅ Verify all Dinosaur Exploder Continuous Integration (CI) checks are passing.
  • ✅ Verify that you have well fill out the different checkboxes in the PR template.
  • ⚠️ Check that your code is clean: no code redundancy, variable and method names are correct, your code is understandable to everyone, and so on.
  • 💡 Reduce changes to the absolute minimum required for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

@sonarqubecloud

sonarqubecloud Bot commented Jun 7, 2026

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Build preview 🚀

badge

Thanks for your contribution to this open-source project! ❤️

A new build has been generated for this pull request:

  • 🎮 Game Artifacts: 🐧 Linux / 🍎 macOS / 🪟 Windows
  • 🧪 Workflow Run: View Logs
  • 🔖 Commit: cd31fd36f39e26c2f8a8acf3e0e86b771859ea46

Tip

This JAR lets you test the latest version of the game from this PR.

Note: Artifacts auto-expire after ~90 days.

Happy testing & enjoy the game! 🎮

The DinoBot Team 🦖

@rutvikraut16 rutvikraut16 changed the title Add manual test report for issue #394 docs: add manual test report for issue #394 Jun 7, 2026

@jvondermarck jvondermarck left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's very interesting, thanks a lot!
I need to think how to handle each manual test report from each contributor, like if we merge this kind of doc, or no. But I will keep your PR open until I think of a solution, thanks!!
if you find any issue, feel free to create an Issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: in-review PR currently in review

Projects

Development

Successfully merging this pull request may close these issues.

2 participants