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
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,7 @@ This extension contributes the following settings:
65
65
-`ruby-spec-runner.clearTerminalOnTestRun`: Clear the terminal before running a test command
66
66
-`ruby-spec-runner.rubyDebugger`: Select which debugging extension to use
67
67
-`ruby-spec-runner.rewriteTestPaths`: Change the test path that is run. See [Rewriting the test file path](#rewriting-the-test-file-path) for more info.
68
+
-`ruby-spec-runner.outputFilePath`: Specify the test output file path. Having a predictable path can allow for test runs to be triggered by other programs (eg guard)
Copy file name to clipboardExpand all lines: package.json
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
},
10
10
"icon": "images/icon.png",
11
11
"license": "MIT",
12
-
"version": "4.0.1",
12
+
"version": "4.1.0",
13
13
"engines": {
14
14
"vscode": "^1.94.0"
15
15
},
@@ -270,6 +270,12 @@
270
270
}
271
271
}
272
272
}
273
+
},
274
+
"ruby-spec-runner.outputFilePath": {
275
+
"type": "string",
276
+
"default": "",
277
+
"markdownDescription": "Specify the absolute path (e.g. `/path/to/my/rspec-results.json`) for the test result output. Useful for triggering rspec manually (eg from Guard).\n\nUses a temp file if left blank. **Changes require vscode restart**",
0 commit comments