Fix handling some SQL Assessment warnings (#1114)

* Some new SQL Assessment warnings may have Check property set to null. Handle the warnings with no exception.
* Make names of SQL Assessment test methods more informative.
This commit is contained in:
Aleksei Guzev
2020-11-04 22:13:46 +03:00
committed by GitHub
parent 954df47ec9
commit 11960fd904
3 changed files with 14 additions and 14 deletions

View File

@@ -126,14 +126,14 @@ INSERT INTO [dbo].[AssessmentResult] ([CheckName],[CheckId],[RulesetName],[Rules
) rpt([CheckName],[CheckId],[RulesetName],[RulesetVersion],[Severity],[Message],[TargetPath],[TargetType],[HelpLink],[Timestamp])";
[Test]
public void GenerateScriptTest()
public void GenerateSqlAssessmentScriptTest()
{
var scriptText = GenerateScriptOperation.GenerateScript(SampleParams, CancellationToken.None);
Assert.AreEqual(SampleScript, scriptText);
}
[Test]
public void ExecuteTest()
public void ExecuteSqlAssessmentScriptTest()
{
var subject = new GenerateScriptOperation(SampleParams);
var taskMetadata = new TaskMetadata();