Teams for Education unit tests don't work with Nix

[mariogreco]

Bug description:
Whenever one of my Teams for Education excercise programs get upgraded to Nix, the Unit Tests feature appears to stop working, and asserts that nothing is being outputted in the “actual output”, when in reality there is an output.

Expected vs Current Behavior:
The unit tests should pass when the code is correct, however they fail while falsely asserting that the program isn’t outputting anything.

Steps to reproduce:

1. Open an exercise through Teams for Education, one which has been created with Unit Tests.
2. Refresh the page so that it automatically gets upgraded to Nix.
3. Complete the program and run the unit tests.
4. Unit tests will fail, while falsely asserting that there was nothing in the actual output.

Bug appears at this link: https://replit.com/@Chun-ICS3C-Sem1-2023-2024/Hello-World

Screenshot(s)/Screen Recording:

Browser/OS/Device: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36

Replit Profile: https://replit.com/@mariogreco

Thank you.

[NuclearPasta0]

Hello, this is a known issue and has been reported before:

Help with a simple test

Hi! I am trying to set up some simple coding assignments for students and I’m trying to use the Input/Output testing but must be doing something wrong as it seems to disregard the printed output from the program and treats the user input as the output. The program takes a given integer and prints Even or Odd depending on the number, works as expected when run but tests fail. [test result] It seems so simple to set up but I must be going wrong somewhere?

Note that you are describing problems with Input Output Tests, not Unit Tests, though both are experiencing problems.

Help with a simple test

Hey all! We are still working on a solution to this issue. I will follow up in this thread once we release a fix.

There are workarounds for both I/O tests and unit tests.
Open this post for the fix for I/O tests. This fix also fixes unit tests.

Help with a simple test

While there is an easy fix for unit tests, the one for I/O tests is cumbersome. My guess is that it the removal of something called prybar is the reason for I/O test problems. If you could try and see if I/O tests work using the prybar template, that would be great. The current solution for fixing I/O tests is just to replace the contents for both the .replit and replit.nix files (provided in the post below): Note that this might break code intelligence, and using an older template is obviou…