Without understanding how it works, it is difficult to effectively store and retrieve the data in Delphi applications.
SQLITE STORED PROCEDURES XOJO HOW TO
The topic explains how it works and how to control it. SQLite Encrypted Database: the database encryption is one of the important SQLite features.Using SQLite Database: explains how to create, connect to, and manage the SQLite database in Delphi application.Introduction to SQLite: reviews SQLite features, missed features, possible applications, and applications not for SQLite.Because of features and capability like this, IMHO, tSQLt framework is the best utility to create SQL unit tests.This reference article has several sections: Above all, we can create isolated, induvial and independent SQL unit tests. SpyProcedure provides a huge advantage and adds flexibility for our unit tests. The tSQLt framework allows us various method to achieve this idea us, however in this article particularly we learned how to mock stored procedure and usage of the SpyProcedure method. The idea behind of the mocking object is very basic, the database objects should be tested without their dependencies, so it means that the dependencies must be eliminated in the unit tests. According to the SQL unit test cases, you can determine usage method of the SpyProcedure. In the first one, we isolated the dependency and in the second one, we manipulated the output of the mocked stored procedure. We compare the expected and actual message value so that the test result occursĪs a result, we completed two different examples to test the usage of the SpyProcedure. AssertEquals expectedmessage, actualmessage You can check it with the following query, but do not disable it in the production environment without being sure.ĮXECUTE tSQLt. Note: In the following test scenario, we are supposing that the Database Mail configuration is disabled. At the same time, SpyProcedure stores the parameter values in a special table. During the SQL unit test mock procedure sit in for the original one and imitate it. SpyProcedure method creates a mock or in other words spy (( Test spy allow us to store methods execution for the later verification) procedure. TSQLt framework provides us a fantastic method which is called as SpyProcedure. Now, let’s learn how to deal with this issue in tSQLt framework For this reason, we will learn how to eliminate these type of dependencies in the tSQLt framework. Certainly, these type of unit test designs are located opposed side to the unit test design concept.īriefly, if a stored procedure, to be tested, invokes another one and the invoked stored procedure result has an influence upon the unit test, we must isolate it in the unit test. On the other hand, unit test maintenance and management operations will require more effort than usual. It would be really tedious to struggle this type of SQL unit test. There is no doubt in that, if we try to write a unit test without eliminating the dependency issue, it might create a more complicated and fragile SQL unit test. Also, the result of the stored procedure which is invoked can directly influence the unit test result. The crucial point here is that, the stored procedure to be tested might depend on the invoked one. In some cases, a stored procedure, which we want to test, includes and invokes another stored procedure(s). Note : I want to suggest that if you don’t have any knowledge or idea about SQL unit testing please read the SQL unit testing with the tSQLt framework for beginners article and also you can take glance at other articles for more details ( see the TOC at the bottom) about SQL unit testing and tSQLt framework. In this article, we will continue to learn how to mock stored procedures in the tSQLt framework and we will provide it with two examples.
SQLITE STORED PROCEDURES XOJO SERIES
In the previous articles of this series (see the TOC at the bottom), we mentioned about SQL unit testing essentials and designing approaches as well and then we reinforce these notions with various tSQLt framework practical examples. In this SQL Unit testing article, we will continue our journey with SQL unit testing.
0 kommentar(er)
