The /testforblock command is not correctly validating block states; a successful output is given despite the actual condition of the block when the command is run.
Steps to Reproduce
Place any block with unique block states (e.g. a button)
Use the /testforblock command to check the block for any block state that is unique to the current state
Expected Outcome
The command should provide an error message stating that the state of the block does not match
Actual Outcome
The command provides a successful output, ignoring the block state given
This issue is being tracked at MCPE-194284.