Trigger coverage about sqlcover HOT 10 OPEN

Hi Hendra,

It is because ApplyTrigger creates a new object and we use an object cache to lookup the name - when we generate the list of names it hasn't been re-created again.

I will try to include the fix to this in an upcoming release.

Ed

from sqlcover.

Hi Ed,

Thanks for your explanation, just looked into tSQLt's ApplyTrigger code and yes you're right it copies the original trigger to apply to target table. I was assuming it use the original trigger, so I thought it was a bug in SQLCover :)

Thanks for considering this as one of feature request as part of the upcoming release. Any ETA? :)

Thanks again,
Hendra

from sqlcover.

I'll have a look and see how easy it will be to add in - which version of sql do you use? It might be easier on newer versions of sql (2012+)

ed

from sqlcover.

Hi,

The database project under test has its compatibility level set to SQL Server 2008. But it always deployed to at least SQL Server 2012+. One of the plan is once we have a good coverage, we can raise the compatibility level to latest version.

But if necessary, I think I can up the compatibility level to SQL Server 2012 for testing purpose.

Hendra

from sqlcover.

I seem to be facing the same problem using SQL Server 2016 in combination with tSQLt.

Is it correct that this issue still exists or is there a fix for this (student here)?

from sqlcover.

This won't be possible until tSQLt adds some code on their side. I have some extra changes I added to tSQLt and SQL Cover to make this work. I have a fork of this project that has these changes and it has been updated to .Net Core 3.1.

I'm just waiting for tSQLt to add their part so I can create a PR into this repo

from sqlcover.

@martinisaksen is this still waiting on tSQLt?

from sqlcover.

I don't remember my PR ever getting merged so it is probably still waiting on that.

from sqlcover.

Hiya @martinisaksen
Seeing as this project seems to be dead, have you moved to another, or still working on your own copy?

We're looking at using this fork https://github.com/sayantandey/SQLServerCoverage

and having triggers covered would be handy!

from sqlcover.

from sqlcover.