tSQLt - Database Unit Testing for SQL Server

Database Unit Testing for SQL Server

  • Home
  • Docs
    • Documents
    • Quick Start
    • Articles
  • Training
  • Downloads
tSQLt » Release Notes » Page 2

tSQLt – V1.0.7682.21917 – Release Notes

01.13.2021 by Sebastian // Leave a Comment

Release: V1.0.7682.21917

BUG FIXES:

  1. Fix sysname casing for case-sensitive databases. Fixed by Trygve Wastvedt (https://github.com/twastvedt).
  2. Fixed issue in tSQLt.Private_GetFullTypeName not handling fractional seconds precision on date and time types. Fixed by saperry (https://github.com/saperry).

NEW FEATURES:

  1. FakeFunction now accepts non-functions as data sources for example tables or SELECT statements. Contributed by Dmitrij Kultasev (https://github.com/dkultasev).

MISCELLANEOUS:

  1. For tSQLt contributors: allow SQL Server Authentication for build

Share and Enjoy:
  • FacebookFacebook
  • TwitterTwitter
  • LinkedInLinkedIn
  • RedditReddit
  • StumbleUponStumbleUpon
  • TechnoratiTechnorati
  • PrintPrint

Categories // Release Notes

tSQLt – V1.0.7597.5637 – Release Notes

10.21.2020 by Sebastian // Leave a Comment

Release: V1.0.7597.5637

BUG FIXES:

N/A

NEW FEATURES:

  1. The tSQLt CLR is now signed with a new key:

    Public key (hash algorithm: sha1):
    0024000004800000940000000602000000240000525341310004000001000100b9af416ad8dfedec08a5652fa257f1242bf4ed60ef5a7b84a429604d62c919c5663a9c7710a7c5df9953b69ec89fce85d71e051140b273f4c9bf890a2bc19c48f22d7b1f1d739f90eebc5729555f7f8b63ed088bbb083b336f7e38b92d44cfe1c842f09632b85114772ff2122bc638c78d497c4e88c2d656c166050d6e1ef394
     
    Public key token is e8fff6f136d7b53e
  2. Several improvements to the build process, including switching from NAnt to Ant
  3. New prepare server process (this fixes all installation issues with 2017 and 2019) Before installing tSQLt, you can now run the PrepareServer.sql that is part of the tSQLt.zip download.
    It automatically enables CLR and installs a server certificate that allows the installation of the CLR.
    There is no need to disable strict CLR security on the server nor do you need to modify database security settings.
    Executing the script requires SA permissions, but needs to be done only once per server. Reminder: If you are using the tSQLt.NewConnection feature,
    you need to execute tSQLt.EnableExternalAccess after each installation of tSQLt.
  4. Annotations tSQLt now allows for test case annotations to modify test behavior. The annotations implemented so far are:

    --[@tSQLt:MaxSqlMajorVersion](@MaxVersion)
    Skips the test if the major version of SQL Server is > @MaxVersion

    --[@tSQLt:MinSqlMajorVersion](@MinVersion)
    Skips the test if the major version of SQL Server is < @MinVersion

    --[@tSQLt:SkipTest](@SkipReason)
    Skips the test and reports @SkipReason as reason in the output
  5. Implemented a CI pipeline for tSQLt itself in Azure DevOps
Share and Enjoy:
  • FacebookFacebook
  • TwitterTwitter
  • LinkedInLinkedIn
  • RedditReddit
  • StumbleUponStumbleUpon
  • TechnoratiTechnorati
  • PrintPrint

Categories // Release Notes

tSQLt – V1.0.5873.27393 – Release Notes

01.31.2016 by Sebastian // Leave a Comment

Release: V1.0.5873.27393 – 2016-01-31

BUG FIXES

  1. tSQLt.DropClass now handles already quoted names correctly.
  2. Fixed error message in tSQLt.FakeTable procedure.

NEW FEATURES

  1. The tSQLt CLR is now signed with a new key:
       Public Key Token = 0x7722217d36028e4c
       Public Key = 0x0602000000240000525341310004000001000100F7D9A45F2B508C2887A8794B053CE5DEB28743B7C748FF545F1F51218B684454B785054629C1417D1D3542B095D80BA171294948FCF978A502AA03240C024746B563BC29B4D8DCD6956593C0C425446021D699EF6FB4DC2155DE7E393150AD6617EDC01216EA93FCE5F8F7BE9FF605AD2B8344E8CC01BEDB924ED06FD368D1D0
    
    The password required to sign an assembly with this key is no longer part of the code base. This was necessary to be able to provide a secure method of installing tSQLt not requiring the database to be set to TRUSTWORTHY anymore.
  2. tSQLt.Info() now returns the public key token of the assembly’s signing key in the CLRSigningKey column.
  3. tSQLt.RunNew executes all tests in test classes (schemata) that were created with tSQLt.NewTestClass after the last call to tSQLt.Reset was executed.
  4. tSQLt.InstallExternalAccessKey installs the required objects in the master database to allow tSQLt to execute with EXTERNAL_ACCESS without the database being TRUSTWORTHY.
  5. tSQLt.RemoveExternalAccessKey removes those objects from the master database.
  6. tSQLt.EnableExternalAccess can be used to manually enable and disable EXTERNAL_ACCESS.
  7. tSQLt automatically tries to enable EXTERNAL_ACCESS, each time any “run” method is called. Enabling EXTERNAL_ACCESS is possible when either the database is TRUSTWORTHY and owned by a server principal with EXTERNAL_ACCESS_ASSEMBLY permission, or if tSQLt.InstallExternalAccessKey has been executed before on the server.
    This feature establishes backward compatibility, but comes at a performance cost. It might therefore be removed in a future version.
  8. tSQLt detects at the beginning of each execution, if the requirements to enable EXTERNAL_ACCESS are not any longer fulfilled. If the assembly is still marked as EXTERNAL_ACCESS, the execution is halted immediately, and an error is reported back to the caller.
  9. tSQLt checks at the beginning of each execution, if the installed assembly’s version matches the version of the T-SQL code. If a mismatch is detected, the execution is immediately halted and an error is reported back to the caller.
  10. tSQLt.Run now allows a test result formatter to be passed in in the @TestResultFormatter parameter. If that parameter is omitted or NULL, the default result formatter is used.

OTHER

  1. Cleaned up several procedures and tests.
  2. Removed extraneous DROP statements from tSQLt install file.
Share and Enjoy:
  • FacebookFacebook
  • TwitterTwitter
  • LinkedInLinkedIn
  • RedditReddit
  • StumbleUponStumbleUpon
  • TechnoratiTechnorati
  • PrintPrint

Categories // Release Notes

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • …
  • 9
  • Next Page »

Navigation

  • Join the conversation
  • Downloads
  • New Logo
  • Sponsors & Contributors
  • Release Notes
  • Articles
  • Training
  • How to get more out of tSQLt
  • Why you should use the tSQLt framework
  • Why you should unit test SQL Server Code
  • Full user guide
  • Documents
    • Quick Start
    • tSQLt Tutorial
    • tSQLt Keyboard Shortcuts
    • Test Creation and Execution
      • NewTestClass
      • DropClass
      • RunAll
      • Run
      • RenameClass
    • Assertions
      • AssertEmptyTable
      • AssertNotEquals
      • AssertObjectDoesNotExist
      • AssertEqualsTableSchema
      • AssertEquals
      • AssertEqualsString
      • AssertEqualsTable
      • AssertObjectExists
      • AssertResultSetsHaveSameMetaData
      • Fail
      • AssertLike
    • Expectations
      • ExpectException
      • ExpectNoException
    • Isolating Dependencies
      • FakeFunction
      • RemoveObjectIfExists
      • ApplyConstraint
      • SpyProcedure
      • FakeTable
      • ApplyTrigger
      • RemoveObject

Links

  • tSQLt on GitHub
  • tSQLt Mailing List
  • twitter hashtag (#tsqlt)
  • tSQLt tag on stackoverflow.com
  • SQL Server Community on Slack (#tsqlt)
  • #tSQLtLive on YouTube

Sponsors

sqlity.net
redgate.com

A sqlity.net llc Web Property. | ©2010 - 2020, All Rights Reserved. | Privacy Policy | Terms of Use