Comments
Sort by recent activity
Well, my next script worked flawlessly, so, I copied the content of the failing script to a new script, and it worked too. Deleted the old. Renamed the new, working version. I'm good to go now. / comments
Well, my next script worked flawlessly, so, I copied the content of the failing script to a new script, and it worked too. Deleted the old. Renamed the new, working version. I'm good to go now.
Thanks for the reply. I did install the tSQLt VS Test Adapter, and the runsettings connection did match (up through the Integrated Security parameter). But, I added the rest just to make them match 100% ";Persist Security Info=False;Pooling=False;MultipleActiveResultSets=False;Connect Timeout=10;Encrypt=False;TrustServerCertificate=True" I did notice however that my runsettings was named as <solution>.runsettings (in the solution folder.) I saved a copy as <database>.runsettings. Restarted Visual Studio. Ran all tests. Same messages as before. Rechecked the documentation; Selected the <database>.runsettings file in "Test->Test Settings->Select Test Settings File" Restarted Visual Studio. Ran all tests. Same messages as before. / comments
Thanks for the reply. I did install the tSQLt VS Test Adapter, and the runsettings connection did match (up through the Integrated Security parameter). But, I added the rest just to make them mat...