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: DEVGUIDE.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,13 +152,13 @@ components installed into Visual Studio 15. You can revert this step by disabli
152
152
153
153
For **Debug**:
154
154
155
-
1. Ensure that the VSIX package is uninstalled. In VS, select Tools/Extensions and Updates and if the package `VisualStudio.FSharp.EnableOpenSource` is installed, select Uninstall
156
-
1. Run ``debug\net40\bin\EnableOpenSource.vsix``
155
+
1. Ensure that the VSIX package is uninstalled. In VS, select Tools/Extensions and Updates and if the package `Visual F# Tools` is installed, select Uninstall
156
+
1. Run ``debug\net40\bin\VisualFSharpVsix.vsix``
157
157
158
158
For **Release**:
159
159
160
-
1. Ensure that the VSIX package is uninstalled. In VS, select Tools/Extensions and Updates and if the package `VisualStudio.FSharp.EnableOpenSource` is installed, select Uninstall
161
-
1. Run ``release\net40\bin\EnableOpenSource.vsix``
160
+
1. Ensure that the VSIX package is uninstalled. In VS, select Tools/Extensions and Updates and if the package `Visual F# Tools` is installed, select Uninstall
161
+
1. Run ``release\net40\bin\VisualFSharpVsix.vsix``
162
162
163
163
Restart Visual Studio, it should now be running your freshly-built Visual F# IDE Tools with updated F# Interactive.
Copy file name to clipboardExpand all lines: TESTGUIDE.md
+16-18Lines changed: 16 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
3
3
## Prerequisites
4
4
5
-
In order to run the FSharpQA auite, you will need to install [Perl](http://www.perl.org/get.html) (ActiveState Perl 5.16.3 is known to work fine).
6
-
Perl must be included in the `%PATH%` for the below steps to work. It is also recommended that you run tests from an elevated command prompt, as there are a couple of test cases which require administrative privileges.
5
+
In order to run the FSharpQA suite, you will need to install [Perl](http://www.perl.org/get.html) (ActiveState Perl 5.16.3 is known to work fine).
6
+
Perl must be included in the `%PATH%` for the below steps to work. It is also recommended that you run tests from an elevated command prompt, as there are a couple of test cases which require administrative privileges.
7
7
8
8
The Perl requirement is gradually being removed.
9
9
@@ -19,7 +19,7 @@ To run tests, use variations such as the following, depending on which test suit
19
19
build.cmd debug,ci
20
20
build.cmd debug,all
21
21
22
-
Default is ``ci`
22
+
Default is `ci`
23
23
24
24
*``ci`` = the build and tests done by continuous integration
25
25
*``compiler`` = build the compiler
@@ -33,31 +33,30 @@ Default is ``ci`
33
33
34
34
The F# tests are split as follows:
35
35
36
-
*[FSharp Suite](tests\fsharp). Older suite with broad coverage of mainline compiler and runtime scenarios.
36
+
*[FSharp Suite](tests/fsharp) - Older suite with broad coverage of mainline compiler and runtime scenarios.
37
37
38
-
*[FSharpQA Suite](tests\fsharpqa\source) - Broad and deep coverage of a variety of compiler, runtime, and syntax scenarios.
38
+
*[FSharpQA Suite](tests/fsharpqa/Source) - Broad and deep coverage of a variety of compiler, runtime, and syntax scenarios.
39
39
40
-
*[FSharp.Core.Unittests](src\fsharp\FSharp.Core.Unittests) - Validation of the core F# types and the public surface area of `FSharp.Core.dll`.
40
+
*[FSharp.Core.Unittests](src/fsharp/FSharp.Core.Unittests) - Validation of the core F# types and the public surface area of `FSharp.Core.dll`.
41
41
42
-
*[FSharp.Compiler.Unittests](src\fsharp\FSharp.Compiler.Unittests) - Validation of compiler internals.
42
+
*[FSharp.Compiler.Unittests](src/fsharp/FSharp.Compiler.Unittests) - Validation of compiler internals.
43
43
44
-
*[VisualFSharp.UnitTests](vsintegration\src\unittests) - Visual F# Tools IDE Unit Test Suite
44
+
*[VisualFSharp.UnitTests](vsintegration/tests/unittests) - Visual F# Tools IDE Unit Test Suite
45
45
This suite exercises a wide range of behaviors in the F# Visual Studio project system and language service.
46
46
47
-
48
47
## More Details
49
48
50
49
### FSharp Suite
51
50
52
-
This is now compiled usinng[tests\fsharp\FSharp.Tests.fsproj] to a unit test DLL which acts as a driver script.
51
+
This is now compiled using[tests\fsharp\FSharp.Tests.fsproj] to a unit test DLL which acts as a driver script.
53
52
54
-
This compiles and execute the `test.fsx` file using some combination of compiler or fsi flags.
53
+
This compiles and executes the `test.fsx` file using some combination of compiler or FSI flags.
55
54
If the compilation and execution encounter no errors, the test is considered to have passed.
56
55
57
56
### FSharpQA Suite
58
57
59
58
These tests require use of the `RunAll.pl` framework to execute.
60
-
Test area directories in this suite will contain a number of source code files and a single `env.lst` file. The `env.lst` file defines a series of test cases, one per line.
59
+
Test area directories in this suite will contain a number of source code files and a single `env.lst` file. The `env.lst` file defines a series of test cases, one per line.
61
60
Test cases will run an optional "pre command," compile some set of source files using some set of flags, optionally run the resulting binary, then optionally run a final "post command."
62
61
If all of these steps complete without issue, the test is considered to have passed.
63
62
@@ -71,7 +70,7 @@ using the '--x86' flag to `nunit3-console.exe`
71
70
72
71
### RunTests.cmd
73
72
74
-
The script `tests\RunTests.cmd` is used to execute the suites. It's used like this:
73
+
The script `tests\RunTests.cmd` is used to execute the suites. It's used like this:
75
74
76
75
RunTests.cmd <debug|release> fsharp [tags to run] [tags not to run]
77
76
RunTests.cmd <debug|release> fsharpqa [tags to run] [tags not to run]
@@ -103,12 +102,11 @@ From a Powershell environment, make sure the double quotes are passed literally,
103
102
`RunTests.cmd` is mostly just a simple wrapper over `tests\fsharpqa\testenv\bin\RunAll.pl`, which has capabilities not discussed here. More advanced test execution scenarios can be achieved by invoking `RunAll.pl` directly.
104
103
Run `perl tests\fsharpqa\testenv\bin\RunAll.pl -?` to see a full list of flags and options.
105
104
106
-
107
105
### Other Tips
108
106
109
-
* Run as admin, or a handful of tests will fail
107
+
* Run as Administrator, or a handful of tests will fail
110
108
111
109
* Making the tests run faster
112
-
* NGen-ing the F# bits (fsc, fsi, FSharp.Core, etc) will result in tests executing much faster. Make sure you run `src\update.cmd` with the `-ngen` flag before running tests.
113
-
* The Fsharp and FsharpQA suites will run test cases in parallel by default. You can comment out the relevant line in `RunTests.cmd` (look for `PARALLEL_ARG`) to disable this.
114
-
* By default, tests from the FSharpQA suite are run using a persistent, hosted version of the compiler. This speeds up test execution, as there is no need for the `fsc.exe` process to spin up repeatedly. To disable this, uncomment the relevant line in `RunTests.cmd` (look for `HOSTED_COMPILER`).
110
+
* NGen-ing the F# bits (fsc, fsi, FSharp.Core, etc) will result in tests executing much faster. Make sure you run `src\update.cmd` with the `-ngen` flag before running tests.
111
+
* The FSharp and FSharpQA suites will run test cases in parallel by default. You can comment out the relevant line in `RunTests.cmd` (look for `PARALLEL_ARG`) to disable this.
112
+
* By default, tests from the FSharpQA suite are run using a persistent, hosted version of the compiler. This speeds up test execution, as there is no need for the `fsc.exe` process to spin up repeatedly. To disable this, uncomment the relevant line in `RunTests.cmd` (look for `HOSTED_COMPILER`).
0 commit comments