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: tests/fsharp/Compiler/Language/SpanTests.fs
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -176,7 +176,7 @@ type T(span: Span<byte>) = struct end
176
176
"""
177
177
[||]
178
178
179
-
[<Test>]
179
+
[<Fact>]
180
180
let``A byref struct with custom attr can be passed as typar``()=
181
181
CompilerAssert.TypeCheckWithErrors """
182
182
namespace System.Runtime.CompilerServices
@@ -193,4 +193,4 @@ module WhatEver =
193
193
let processT (a: Action<T>, ie: seq<T>, asList: list<T>) = ()
194
194
"""
195
195
[| FSharpDiagnosticSeverity.Error,3300,(13,45,13,51),"The parameter 'asList' has an invalid type 'T list'. This is not permitted by the rules of Common IL."|]
Copy file name to clipboardExpand all lines: tests/fsharp/readme.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,15 @@
2
2
3
3
## Layout
4
4
5
-
The tests are NUNIT test cases. They test a very wide range of compiler, interactive and FSharp.Core scenarios.
5
+
The tests are xUnit test cases. They test a very wide range of compiler, interactive and FSharp.Core scenarios.
6
6
7
7
The bulk of the test cases are enumerated in tests.fs, these are the old cambridge test suite. They build on a test-suite ported from windows batch files. They run the compiler and fsi as separate processes, when built for the coreclr it runs the coreclr versions using dotnet.exe
8
8
9
9
The framework and utilities can be found in test-framework.fs, single-test.fs.
10
10
11
11
test cases look similar to:
12
12
````
13
-
[<Test>]
13
+
[<Fact>]
14
14
let ``array-FSI`` () = singleTestBuildAndRun "core/array" FSI
15
15
````
16
16
This test case builds and runs the test case in the folder core/array
@@ -20,7 +20,7 @@ __#if !NETCOREAPP__
20
20
21
21
There are some older tests in this section that looks similar to:
22
22
````
23
-
[<Test>]
23
+
[<Fact>]
24
24
let events () =
25
25
let cfg = testConfig "core/events"
26
26
fsc cfg "%s -a -o:test.dll -g" cfg.fsc_flags ["test.fs"]
@@ -34,11 +34,11 @@ There are some older tests in this section that looks similar to:
34
34
````
35
35
These tests build, compile, peverify and run fsi.
36
36
37
-
Below the Compiler directory there is a set of tests built on the compiler service. They are nunit and instead of executing the compiler and fsi using files on disk the tests are built from memory. These tests use the CompilerAssert framework and look similar to:
37
+
Below the Compiler directory there is a set of tests built on the compiler service. They are xUnit and instead of executing the compiler and fsi using files on disk the tests are built from memory. These tests use the CompilerAssert framework and look similar to:
38
38
39
39
This test verifies that a warning is produces when a value is implicitly discarded. The line ````x = 20``` looks like an assignment but in F# is a test for equality it yields and discards the value false.
40
40
````
41
-
[<Test>]
41
+
[<Fact>]
42
42
let ``Unused compare with immutable when assignment might be intended``() =
43
43
CompilerAssert.TypeCheckSingleError
44
44
"""
@@ -62,4 +62,4 @@ When a test is run, .err/.vserr output files are created and compared to their m
62
62
63
63
Refer to [Test Guide](../../TESTGUIDE.md#baselines) to know more about how to update them.
64
64
65
-
Tests are organized under modules as functions bearing NUnit`[<Test>]` attribute and can be run from an IDE or the command line (see the [Test Guide](../../TESTGUIDE.md)).
65
+
Tests are organized under modules as functions bearing xUnit`[<Fact>]` attribute and can be run from an IDE or the command line (see the [Test Guide](../../TESTGUIDE.md)).
0 commit comments