Wrapping Up

[stanbsky]

For simplicity's sake, here's a list of all the remaining tasks with programming. Pick one, create an issue for it, own it, link it in the comments and I'll update the list:

UI

• [x] dynamic HP bar in the UI @stanbsky
• [x] subtitle as a persistent UI element with a background and rich icons @stanbsky
• [x] shop menu that displays current gold balance and owned powerups @Kroojel
• [x] rework start/end-of-game screens and buttons to be consistent with current UI and not shit overall @stanbsky

Features

• [x] implement obstacles (free to do whatever so long as it fits the remit!) @stanbsky 581c3e00aa308043991f602df50542af40375580
• [x] implement the ultimate objective aka Boss that wins the game @stanbsky #33
• [x] implement saving/loading the game state @AlexGUni

Testing

• [ ] meta-issue: write out stubs for all the tests we'll need for the game! it'll make other test writers' jobs easier
• [x] meta-issue 2: refactor MainGameScreen and associated bits to make it easy to initialise our static classes without triggering requests for assets, etc during automated testing @stanbsky
• [ ] write out tests for the Functional Requirements
• [ ] write out tests for significant programming logic - whatever you judge that to be, we just need to explain/justify it in the testing report after!
• [ ] generate a test report regarding tests passed and code coverage (should be an intellij/junit feature) and upload to the website, providing the URL in 4 (c)

[stanbsky]

Further to the above:

IMPORTANT:

• [x] exported JAR file crashes with ExceptionIninitializerError upon launch @Kroojel

Reports

• [ ] CI report (5 a & b)
• [ ] Change report (2 a & b) (@stanbsky can help with content for (a) wrt implementation)
• [ ] Implementation comments in the code, should be consistent with change report @stanbsky @Kroojel
• [ ] Implementation explanation of changes and new features @stanbsky
• [ ] Testing report (4 a & b)