Check/fix spec test vs user test run on unsaved code.
It should run on the saved code in both cases.
From mattermost channel:Submitted by Elmer van Chastelet on 9 October 2018 at 11:19
In the R&L weblab project, I have received a comment about “first save before spec test”. In short, when running Spec Tests, the saved code is being used instead of the (current) unsaved code. In contrary, normal tests are ran on this unsaved code. Is this by design, or is this a bug?