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
version: 1 test runners are quite basic, and only detect if either all tests passed or not. These test runners capture the console output of the test runner and output that. They do not include details on individual tests passing/failing
version: 2 test runners contain detailed information on individual tests passing/failing. We've recently added a required field named test_code, which contains the code the test ran to verify the behavior (see the spec for the test_code property).
The test runner's output is currently what I refer to as version 1.5: it contains the individual test information, but does not yet contain the test_code key. If possible, the test runner should be updated to also include the test code.
We've recently updated the test runner interface specification to allow for two types of test runners, identified via a new
version
property in theresults.json
file (see the spec for the version property):version: 1
test runners are quite basic, and only detect if either all tests passed or not. These test runners capture the console output of the test runner and output that. They do not include details on individual tests passing/failingversion: 2
test runners contain detailed information on individual tests passing/failing. We've recently added a required field namedtest_code
, which contains the code the test ran to verify the behavior (see the spec for the test_code property).The test runner's output is currently what I refer to as version 1.5: it contains the individual test information, but does not yet contain the
test_code
key. If possible, the test runner should be updated to also include the test code.There is an existing TODO in the code where the test code is written: https://github.com/exercism/scala-test-runner/blob/main/src/main/scala/Application.scala#L63 You are completely free on how you want to extract the test code, either via the AST or via finding the test code in the source code text via string manipulation. Whatever is most convenient.
Let me know if there are any questions.
The text was updated successfully, but these errors were encountered: