I don't if I understand the test cases too well, but I think I found a issues with the test generated:
@project_test(PROJECT_NAME) @pytest.mark.parametrize( ("in_params", "expected"), [ pytest.param('"4, 5, 3, 1, 2"', "1, 2, 3, 4, 5", id="sample input"), pytest.param( '"4, 5, 3, 1, 4, 2"', "1, 2, 3, 4, 4, 5", id="sample input: with duplicate" ), pytest.param( '"1, 2, 3, 4, 5"', "1, 2, 3, 4, 5", id="sample input: already sorted" ), pytest.param( '"9, 8, 7, 6, 5, 4, 3, 2, 1"', "1, 2, 3, 4, 5, 6, 7, 8, 9", id="sample input: reverse sorted", ), ], )

I believe my issues with the test stem from that the extra (') in the in_param, because I do know if manual type all the test case on my local build they sort, but the test report that my code doesn't pass.

I was wondering where can I go about modifying the test_sleep_sort.py file, because when I modify it directly, it regenerate to before modification after running the glotter test command

The in_params are correct. They work for every other language that has implemented Sleep Sort. The purpose of the single quotes around the double quotes is just how glotter handle passing command line arguments into the docker container that it runs to run the sample for each test.

If you are running glotter locally, when prompted for the parameter, do not use the single quote. For example, you would enter "9, 8, 7, 6, 5, 4, 3, 2, 1".

According to this article, using Future with synchronized can lead to undefined behavior. I'm wondering if something like a common mutex could be used instead of synchronized.

You might want to take a look at this. I know this is Java, not Scala, but from this it looks like that should be used instead of the Scala class.

One final comment, when you are ready to do the final submission, please remove all the commented out code. It adds clutter.