Skip to content

Commit 70270f6

Browse files
authored
Merge branch 'master' into immediate_zip_error
2 parents 70115bb + 7f128da commit 70270f6

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

test-plan.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,15 @@ The easist way to verify that a project was successfully loaded is to open a .cs
9292
* In a project that uses globbing (.NET Core), use the VS Code file explorer to add a new file next to the csproj. Intellisense/sighelp/etc should be available in the new file
9393
* Add a new file and reference a type in it from a different file. Deleting from disk the file containing the referenced type should produce error messages
9494

95-
#### Omnisharp Options
95+
#### OmniSharp Options
9696

97-
#### omnisharp.useMono (for Linux)
97+
#### omnisharp.useGlobalMono (for Linux/Mac)
98+
This option can be set to any of the following values:
99+
* "auto" - Will launch OmniSharp using mono if version>=5.2.0 is installed but will launch using the run script if that is not so.
100+
* "always" - Will launch OmniSharp using mono if version>=5.2.0 is installed and will throw an error otherwise.
101+
* "never" - Launches OmniSharp without using the global mono
102+
103+
The value of OmniSharp path displayed in the OmniSharp log can be used to know if OmniSharp has launched using mono or not. If it is running using global mono, the path will end with "OmniSharp.exe" else the path will end with "run".
98104
For using this option, mono version greater than or equal to 5.2.0 must be installed. If that is not so, setting this option to true, should give an error.
99105
* If the option is not set, the OmniSharp path displayed in the "OmniSharp Log" should end with "run"
100106
* If the option is set, the OmniSharp path as mentioned above should end with "OmniSharp.exe"
@@ -108,6 +114,13 @@ The easist way to verify that a project was successfully loaded is to open a .cs
108114
* All the above configurations should work, with and without setting the useMono option on Linux
109115
* The above behavior should be exhibited when a new vscode window is opened, as well as if the setting is modified and a "Restart OmniSharp"(Ctrl+Shift+P --> OmniSharp: Restart OmniSharp) is performed.
110116

117+
#### Status Bar Item
118+
The status bar item(s) must appear on the left side of the VS Code's status bar
119+
* When the extension is setting up the dependencies, the status bar item should show "Downloading packages"/"Installing packages".
120+
* Once the server has started, there should be two status bar items:
121+
* OmniSharp status Bar item - It should show a green flame (indicating that the OmniSharp server is running) and clicking on it should show the OmniSharp log channel
122+
* Project status bar item - It should show and a folder icon and the name of the currently selected project/solution. Clicking on this element should show a command palette menu to select other projects/solutions in the workspace.
123+
111124
[1] For example,
112125
```
113126
mkdir project

0 commit comments

Comments
 (0)