Implement NLog in unit test project

[hyzx86]

Currently, unit tests catch very limited exception information,
Many exceptions that occur during the installation process are ignored
Can I use the log function to quickly locate anomalies?

[hishamco]

Could you please ellaborate?

[hyzx86]

Some exceptions during migration will not directly cause process interruption, but once an exception occurs, it will have a serious impact on the integrity of system functions

Just like , the exception caused by the MySql /Postgresql syntax problem mentioned earlier did not interrupt the migration process

#14338

#11359

It may be due to some considerations that the change exception is not thrown, but if we can also work with log file scanning to eliminate some errors that are not easy to find, it is also a good way

And CI/CD will be able to find these errors automatically

[hyzx86]

Just use below code . Maybe there should be a better way

        [Fact]
        public async Task ValidateLogErrors()
        {

            using var context = new ScriptQueryContext();
            //初始化测试环境
            await context.InitializeAsync();
            await context.UsingTenantScopeAsync(scope =>
            {
                var fileTarget = (FileTarget)LogManager.Configuration.FindTargetByName("file");
                var logFilePath = fileTarget.FileName.Render(new LogEventInfo { TimeStamp = DateTime.Now });

                Assert.True(File.Exists(logFilePath));

                var hasError = AppFileHelper.ReadLines(logFilePath).Any(x => x.Contains("|ERROR|"));
                Assert.False(hasError);

                return Task.CompletedTask;
            });
        }

[sebastienros]

Like a functional test to catch exceptions during setup that might get through otherwise.