Tests are contradictory

Stage MG5 and NI6 are contradictory. MG5 uses common shell command names to search in provided path and expects a different response than a shell built-in. However, in NI6 one of these commands (cat) ends up becoming a shell built-in. Ideally, ‘is a shell built in’ should be the expected type command response for cat, but the earlier MG5 tests expect it to be different (cat is /path/to/cat).

This should be fixed IMO.

Could you clarify where it says that cat is expected to be a shell built-in? Iirc the tester always expects cat to be an executable.

It doesn’t but it is also not clearly mentioned to treat it as an executable. I realized that in subsequent stages (which I completed just now) but initially assumed it to be a new command to support and read the files provided in its arguments manually.