Code Coverage Error

adam_hafner

I am trying to use SQL Test on the test tSQLt database and the tests complete correctly, but the code coverage errors.  The error is as follows:

System.IO.FileLoadException: The located 
assembly's manifest definition does not match the assembly reference. (Exception 
from HRESULT: 0x80131040) at 
SQLCover.Parsers.StatementParser.GetChildStatements(String script, Boolean 
quotedIdentifier) at SQLCover.Source.DatabaseSourceGateway.GetBatches(List`1 
objectFilter, List`1 filteredObjects) at 
SQLCover.CodeCoverage.GenerateResults(List`1 filter, List`1 xml, List`1 
filteredObjects) at SQLCover.CodeCoverage.Stop() at 
RedGate.SQLTest.tSQLt.Cover.SqlCoverTracker.Stop()

There was a similar issue reported that @Jon_Kirkwood responded to that required a new version of SQL Test (https://forum.red-gate.com/discussion/89558/code-coverage-error#latest).  I have tried uninstalling/reinstalling SQL Test and that had no effect.  

Here are the software versions I am running:

SSMS - 20.2.30.0
SQL Test - 4.1.20.3489

Can you please let me know how to resolve this issue?

Thanks,

--Adam

Jon_Kirkwood

Hi @adam_hafner

Thanks for reaching out on the Redgate forum, and sorry to hear this error is occurring for you. I had a look over my old post and can see the dev fix that was done around then. Hopefully this isn't a regression.

I noticed that there was another recent release of SQL Test - before I escalate to the team, can you patch to
V4.1.21 and confirm that the error is still occurring for you

Download link for that version is available here:
https://download.red-gate.com/checkforupdates/SQLTest/SQLTest_4.1.21.3620.exe

adam_hafner

@Jon_Kirkwood I just updated to 4.1.21 and it's still throwing the same error message for coverage in SQL Test.  Can you escalate to your team to investigate?  Thanks!

Jon_Kirkwood

Thank you for confirming and sorry to hear it is still occurring. 
Shall escalate and come back via this forum post with any updates as they are made available

adam_hafner

@Jon_Kirkwood has there been any discussion internally regarding the future use of SQL Cover for performing the coverage analysis?  If you look at the github repo for SQL Cover (https://github.com/GoEddie/SQLCover) it hasn't been updated since 2019.  This seems concerning as there have been enhancements and such to other products that consume the output of SQL Cover that probably should be implemented.  Also, there have been a few forks from this repo to address enhancements and bug fixes that were done purely because this doesn't seem to be maintained anymore.

Here is one of the forks (https://github.com/sayantandey/SQLServerCoverage)