Remove statements that lead to massive test outputs after they have run.

test/EFCore.Jet.FunctionalTests/AssemblyInitialization.cs

@@ -1,29 +0,0 @@
-using System.Data.Common;
-using EntityFrameworkCore.Jet.Data;
-using Microsoft.VisualStudio.TestTools.UnitTesting;
-
-namespace EntityFrameworkCore.Jet.FunctionalTests
-{
-    [TestClass]
-    public class AssemblyInitialization
-    {
-        //public static DbConnection Connection;
-
-        [AssemblyInitialize]
-        public static void AssemblyInitialize(TestContext testContext)
-        {
-            // This is the only reason why we include the Provider
-            JetConfiguration.ShowSqlStatements = true;
-            JetConfiguration.UseConnectionPooling = false;
-
-            //Connection = Helpers.CreateAndOpenJetDatabase(Helpers.DefaultJetStoreName);
-        }
-
-        [AssemblyCleanup]
-        public static void AssemblyCleanup()
-        {
-            //Connection?.Dispose();
-            //Helpers.DeleteJetDatabase(Helpers.DefaultJetStoreName);
-        }
-    }
-}

test/EFCore.Jet.FunctionalTests/Scaffolding/JetDatabaseModelFactoryTest.cs

@@ -36,7 +36,6 @@ namespace EntityFrameworkCore.Jet.FunctionalTests.Scaffolding
             _testOutputHelper = testOutputHelper;
             //Fixture.ListLoggerFactory.Clear();
             Fixture.ListLoggerFactory.SetTestOutputHelper(testOutputHelper);
-            JetConfiguration.ShowSqlStatements = true;
         }
 
         #region Model