A table test separates a collection of cases from the loop that runs them. Give each case a name, an input and an expected result, then report the case name when it fails. In a normal package you would place a Test function in a file ending _test.go and run go test; this editor calls a local validator instead of providing that command. The reasoning is the same. A test must accept a correct implementation as well as reject a plausible bug. Testing only ordinary positive inputs can leave zero values, duplicates and boundary comparisons untested. You will write validators for small candidate functions, then run them against both correct and deliberately flawed versions.
A correct absolute-value function must pass.