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 slowly if I use a where in with code that executed at the calling server.
Why would you NOT use sprocs is my #1 question?
On Thu, Jul 23, 2020 at 5:30 PM MB Software Solutions, LLC < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
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.
If your function receives params for the actual source you are just changing the params you pass back, or where they are coming back from.
Proving something didn't work helps you catch errors nicely and deal with them.
For my coding style, I have a function that may be overloaded 2-3-+ ways. All of them need to be tested.
On Thu, Jul 23, 2020 at 12:18 PM Garrett Fitzgerald <
sarekofvulcan@gmail.com>
wrote:
I still have trouble conceptualizing how to write unit tests for data access.
On Thu, Jul 23, 2020, 11:37 MB Software Solutions, LLC < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
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 Lee's WhilFest presentation in 2003, it's worked out great. It's much easier to connect the UI to those processes. But my comment still stands: I bet less than 5% of VFP devs write unit tests in their apps.
On 7/21/2020 8:09 PM, Stephen Russell wrote:
Why not?
Design by Test. You create your functionality in TESTS and then use
those
functions in a UI.
On Tue, Jul 21, 2020 at 5:53 PM MB Software Solutions, LLC < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
I would wager that less than 5% of devs (in VFP anyway) have unit
tests
in their solution setup.
On 7/21/2020 10:04 AM, Johan Nel wrote: > Ah my child, I have to confess I have never in my complete
development
> career had a plan or unit test done... > > On 2020/07/21 15:13, Eric Selje wrote: >> Forgive me father, for I have started coding without having a plan
or
>> even >> a unit test written first. It's been 51 years since my last
confession.
>> On Sat, Jul 18, 2020 at 1:57 PM Dennis Schuette dennis@cbsds.com >> wrote: >> >>> That's such an easy change, I won't even bill you for it. >>> >>> 1 hour of programming, 5 hours of debugging, and 3 customer
requested
>>> enhancements later, I'm almost done! >>> >>> Customized Business Services, LLC (928) 580-6352 >>> Dennis Schuette Primary: >>> dennis@cbsds.com >>> 49 NW 130 Avenue Alternate: >>> Schuette.dennis@gmail.com >>> Great Bend, KS 67530 >>> >>> -----Original Message----- >>> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf
Of
>>> Stephen Russell >>> Sent: Friday, July 17, 2020 11:06 AM >>> To: profoxtech@leafe.com >>> Subject: [NF] I will ..... >>> >>> Alright, I'm not a priest, but I am a programmer. >>> >>> Confess to me your programming sins, and I shall absolve you. >>> >>> >>> >>> -- >>> Stephen Russell >>> Sr. Analyst >>> Ring Container Technology >>> Oakland TN >>> >>> 901.246-0159 cell >>> >>> >>> --- StripMime Report -- processed MIME parts ---
multipart/alternative
>>> text/plain (text body -- kept) >>> text/html >>> --- >>>
[excessive quoting removed by server]