On 7/23/2020 8:07 PM, Stephen Russell wrote:
Pretty much for anything that is repetitive in nature. All apps yes. I
have the instances set to not allow homemade sql except for some of our new
stuff in R, or my certificate report that passes SQL to include all of the
Lot Numbers needed. It is
Pretty much for anything that is repetitive in nature. All apps yes. I
have the instances set to not allow homemade sql except for some of our new
stuff in R, or my certificate report that passes SQL to include all of the
Lot Numbers needed. It is on a separate sql server and operates very
Stephen -- Are you still using stored procedures for all your CRUD?
On 7/23/2020 5:54 PM, Stephen Russell wrote:
I only see it as testing a connection to a defined data source. You
have creds that work for a positive test. You have creds that fail to
notify you that no connection was made.
I only see it as testing a connection to a defined data source. You
have creds that work for a positive test. You have creds that fail to
notify you that no connection was made.
If your function receives params for the actual source you are just
changing the params you pass back, or where they
On 7/23/2020 2:12 PM, Christof Wollenhaupt wrote:
For projects that use a more object oriented approach I use foxmock to
simulate data. Most times what I really need isn't the actual data
access, because I know that these classes work, rather I have to test
the code that accesses data. foxmock
> I still have trouble conceptualizing how to write unit tests for data
> access.
I have a function that reads a table and recreates the same structure as an
empty cursor with all indexes, and such. Optionally, it appends the existing
content of the table. In my unit test I can then make
On Jul 23, 2020, at 12:17, Garrett Fitzgerald wrote:
>
> I still have trouble conceptualizing how to write unit tests for data
> access.
That’s good, because once you exercise anything outside of the “unit”, it’s no
longer a unit test.
What you generally do is mock the database call,
I still have trouble conceptualizing how to write unit tests for data
access.
On Thu, Jul 23, 2020, 11:37 MB Software Solutions, LLC <
mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote:
> I have done it that way before, and it works well. I wrote the DataObj
> and BizObj first before the UI
I have done it that way before, and it works well. I wrote the DataObj
and BizObj first before the UI for those purposes. But alas, those are
mere validation and data access classes; those are not Unit Tests, by my
definition anyway. Ever since I did this n-tier design after watching
Bob
9 matches
Mail list logo
