Out of curiosity I decided to test how in depth the tests were for the functional tests of the stock price checker project. To do so I simply created five functional tests all aimed at the same endpoint and all calling: assert.isTrue(true, “Testing to see if this works”);
Doing so allowed me to pass the test for “All 5 functional tests passing”
I have a few ideas for possible solutions to this issue:
Have required variable names for the tests
By requiring the learner to use specific variable names in the functional tests the file could be parsed for the correct tests, this would make it significantly harder for the user to simply fake doing the functional tests.
Duplicate tests on server side
Implementing the same tests required for the user to develop on the FCC server side would allow the verification to compare what the user’s tests reported to what the server side tests reported. Doing so would allow any mismatches to raise an alarm of some kind.
Continue with current method
Currently users are required to agree to an Academic Honesty policy. It really wouldn’t be unreasonable to continue with this process and just call out those that do try to pass of faked functional tests as real.
I will leave this version of the project alone in case there is any need to verify how I faked the tests https://replit.com/@MacKeil/boilerplate-project-stockchecker
All in all I just wanted to make sure this was reported at some capacity, and that someone was made aware.