You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the tests (bin/test) are really slow as they start a new sbt shell for each exercise. In the CI this takes around 20 minutes (!).
Ideally this should be refactored so the sbt is initialized only once and each exercise is its own submodule.
In addition current testing approach has following problems:
It's not portable, the bin/test doesn't work on Mac.
Uses sed for stripping out pending from all exercises. Perhaps we can somehow do it from the Scala side instead and in general rethink our approach here (see forum thread)
I believe it to be a blocker for further development of the track, since it makes the dev feedback loop very slow.
The text was updated successfully, but these errors were encountered:
Currently, the tests (
bin/test
) are really slow as they start a new sbt shell for each exercise. In the CI this takes around 20 minutes (!).Ideally this should be refactored so the sbt is initialized only once and each exercise is its own submodule.
In addition current testing approach has following problems:
sed
for stripping outpending
from all exercises. Perhaps we can somehow do it from the Scala side instead and in general rethink our approach here (see forum thread)I believe it to be a blocker for further development of the track, since it makes the dev feedback loop very slow.
The text was updated successfully, but these errors were encountered: