tSQLt - Database Unit Testing for SQL Server

Database Unit Testing for SQL Server

tSQLt » Sebastian » Page 3

tSQLt – V1.0.5873.27393 – Release Notes

by // 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:

tSQLt – V1.0.5793.20044 – Release Notes

by // Leave a Comment

Release: V1.0.5793.20044 – 2015-11-11

BUG FIXES

  1. AssertEqualsTableSchema now handles gaps in column_id values correctly (thanks Greg L.)
  2. Fixed handling of empty messages in AssertEmptyTable

NEW FEATURES

  1. AssertStringIn asserts that a string value is element of a set of string values
  2. ApplyConstraint can now apply cascading actions on foreign keys
  3. FakeTable can now fake synonyms of tables and views (in the same database only, for now)

OTHER

  1. The official tSQLt source code repository is now on GitHub: https://github.com/tSQLt-org/tSQLt
Share and Enjoy:

tSQLt – V1.0.5686.18945 – Release Notes

by // Leave a Comment

Release: V1.0.5686.18945 – 2015-07-27

BUG FIXES

  1. The XML output now validates against the JUnit test result XML schema at
    https://raw.githubusercontent.com/windyroad/JUnit-Schema/master/JUnit.xsd
    While there is no “official” JUnit schema, the above is the one that is
    referenced most often online.
  2. tSQLt.DropClass now handles XML schemata correctly.
  3. All tSQLt assertions can now be called with a @Message parameter. In case of a
    failure, the value of that parameter will be output before the default failure
    message.
    For backward compatibility, tSQLt.AssertEqualsTable still has a @FailMsg
    parameter. Its use is now deprecated.

NEW FEATURES

  1. tSQLt.Info() now returns the version and build of the SQL Server Instance it is installed on: 
       SELECT * FROM tSQLt.Info() AS I;

   Version        ClrVersion     SqlVersion SqlBuild
   -------------- -------------- ---------- --------
   1.0.5479.30419 1.0.5479.30419      12.00  4213.00
  2. Verbose execution mode
    Executing EXEC tSQLt.SetVerbose @Verbose = 1; before running the tests will cause
    tSQLt to output the test name at the beginning and the end of each test’s execution.
    That makes it easier in large test suites to find the output of a particular test.
  3. tSQLt.RunC
    The new procedure tSQLt.RunC behaves identical to tSQLt.Run. However, instead of
    expecting the test (class) name in a parameter, it parses the INPUTBUFFER and
    extracts the name from a specially formed comment:

       
   EXEC tSQLt.RunC;--Run_Methods_Tests.[test tSQLt.RunC calls tSQLt.Run with everything after ;-- as @TestName]

    This makes for a more powerful SQL Query shortcut in SSMS as test names now do not have to be quoted anymore.

  4. tSQLt.AssertEqualsTableSchema
    tSQLt.AssertEqualsTableSchema is called like tSQLt.AssertEqualsTable. Instead of
    the table contents, it compares the columns including name, datatype, collation,
    NULL-ability and identity property.
  5. The test runner now captures start and end time for each test. This information
    is included in the XML output. The default output contains the execution duration
    for each test.
  6. Both tSQLt.SpyProcedure and tSQLt.FakeFunction now handle table type parameters.
    The content of a table type parameter in a spied procedure is converted into
    XML and included in the _SpyProcedureLog table.

OTHER

  1. Farewell Sourceforge
    Because of several issues over the last months and because of even more complaints
    about Sourceforge’s business practices by tSQLt users, we decided to find a more appropriate space.
    The official downloads are now available directly on tSQLt.org. The source code
    repository will find its new home either on github or bitbucket over the next few days.
  2. The fail message of tSQLt.AssertEqualsString is now broken into two lines
    with aligned string values for easier comparison.
  3. The installation script now prints a welcome message.
Share and Enjoy: