/// This is the case where at (*TYPING*) we first type 1...N-1 characters of the target custom operation and then invoke the completion list, and we check that the completion list contains the custom operation
assertContainserrors"A unique overload for method 'Do' could not be determined based on type information prior to this program point. A type annotation may be needed. Candidates: member A.Do : a:int * b:'T -> unit, member A.Do : a:int * b:int -> unit"
[<Test>]
[<Test;Category("Expensive")>]
memberpublicthis.``NoErrorInErrList``()=
use_guard=this.UsingNewVS()
letfileContents1="""
...
...
@@ -328,7 +328,7 @@ b.Do(1, 1)
TakeCoffeeBreak(this.VS)
this.VerifyCountAtSpecifiedFile(project,0)
[<Test>]
[<Test;Category("Expensive")>]
memberpublicthis.``NoLevel4Warning``()=
use_guard=this.UsingNewVS()
letfileContents="""
...
...
@@ -557,7 +557,6 @@ but here has type
// In this bug, particular warns were still present after nowarn
[<Test>]
[<Category("PerfCheck")>]
memberpublicthis.``NoWarn.Bug5424``()=
letfileContent="""
#nowarn "67" // this type test or downcast will always hold
["error FS0041: A unique overload for method 'Plot' could not be determined based on type information prior to this program point. A type annotation may be needed. Candidates: member N.M.LineChart.Plot : f:(float -> float) * xmin:float * xmax:float -> unit, member N.M.LineChart.Plot : f:System.Func<double,double> * xmin:float * xmax:float -> unit"])
@@ -1304,7 +1304,7 @@ type UsingMSBuild() as this =
// Compile a script which #loads a source file. The build can't succeed without the loaded file.
[<Test>]
[<Test;Category("Expensive")>]
[<Category("fsx closure")>]
[<Category("fsx compile")>]
memberpublicthis.``Fsx.CompileFsx_2``()=
...
...
@@ -1327,7 +1327,7 @@ type UsingMSBuild() as this =
Assert.IsTrue(build.BuildSucceeded,"Expected build to succeed")
// Compile a script which #loads a source file. The build can't succeed without
[<Test>]
[<Test;Category("Expensive")>]
[<Category("fsx closure")>]
[<Category("fsx compile")>]
memberpublicthis.``Fsx.CompileFsx_3``()=
...
...
@@ -1537,8 +1537,7 @@ type UsingMSBuild() as this =
/// There was a problem in which synthetic tokens like #load were causing asserts
[<Test>]
[<Category("PerfCheck")>]
[<Test;;Category("Expensive")>]
memberpublicthis.``Fsx.SyntheticTokens``()=
Helper.ExhaustivelyScrutinize(
this.TestRunner,
...
...
@@ -1704,12 +1703,10 @@ type UsingMSBuild() as this =
Assert.IsTrue(countInvaldiationHandlersAdded()-countInvaldiationHandlersRemoved()=0,"Check6b2, at end, all invalidation handlers removed after explicit cleraring")
/// FEATURE: Errors in the code are underlined with red squiggles and a clickable description of the error appears in the Error List.
[<Test>]
[<Category("PerfCheck")>]
memberpublicthis.``Basic.Case1``()=
letfileContent="""
let x = 3
...
...
@@ -580,7 +577,6 @@ type X() =
this.VerifySquiggleContainedAtStartOfMarker(fileContent,"(*Mark*)",(Microsoft.VisualStudio.FSharp.LanguageService.Severity.Error,"This value is not a function and cannot be applied"))