Skip to content
This repository has been archived by the owner on Mar 8, 2020. It is now read-only.

Refactor tests #12

Open
4 of 6 tasks
mark-wiemer opened this issue Aug 2, 2019 · 1 comment
Open
4 of 6 tasks

Refactor tests #12

mark-wiemer opened this issue Aug 2, 2019 · 1 comment
Labels
refactor Refactor existing system

Comments

@mark-wiemer
Copy link
Owner

mark-wiemer commented Aug 2, 2019

Tests are currently not very granular and, in general, poorly organized.

Acceptance Criteria:

  • MainTests.assertCreatesGame becomes two methods: one for the scanner, one for CLA
  • Stay DRY with fixture-like functionality
  • Remove printing from passing tests (Remove printing from passing tests #41)
  • IoUtils interface becomes instance-based, not static, is improved (see IoUtils improvements #17)
  • Remove redundant tests (LevelTests is redundant, already tested within PlayTests)
  • Tests are at top of class
@mark-wiemer mark-wiemer added the refactor Refactor existing system label Aug 2, 2019
@mark-wiemer
Copy link
Owner Author

Really good information about parametrizing tests with JUnit 5: https://www.baeldung.com/parameterized-tests-junit-5

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
refactor Refactor existing system
Projects
None yet
Development

No branches or pull requests

1 participant