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.
We’ll keep an eye out for similar reports - haven’t seen anyone else mention this so far (checked forum + the in-app feedback).
Hi Same issue is faced by me
[tester::#MG5] Running tests for Stage #MG5 (The type builtin: executable files)
[tester::#MG5] Running ./your_program.sh
[your-program] $ type cat
[your-program] cat is a shell builtin
[tester::#MG5] Output does not match expected value.
[tester::#MG5] Expected: “cat is /bin/cat”
[tester::#MG5] Received: “cat is a shell builtin”
[your-program] $
[tester::#MG5] Assertion failed.
[tester::#MG5] Test failed
Hi @AryanJindal7, looks like you’ve got past this stage — do you happen to remember what was wrong? Would love to see if we can improve the tester / instructions.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.