Set the damage to 0 or 1 while creating a new move from Move Class Bug.
Opened this issue · 0 comments
wee-zard commented
Arrange:
- Configuring the environment (with for example Gradle v3.3).
- Importing the junit .jar files, so we can run junit test cases.
Act:
- Making an instance of Move Class with the following parameters:
- damage=0
- the other parameters can be anything.
- Store this instance in a variable and call it as "move1".
- Check if the min/max damage is anything else then 0 and 1.
Assert:
- The min/max damage can not be 0 or 1 written by the javadoc to the Move constructor.
Excepting:
- We got an exception or something that warn us that we cannot create a new Move with damage=0 or damage=1.
Actually:
- We can freely make a new "move" with damage=0 and damage=1 without any problem, even if the javadoc said that we cannot do it.