Does anyone have a best practice for testing withi...
# administration
n
Does anyone have a best practice for testing within a production account, other than deleting transactions after testing is complete? We have a partner who has their own sandbox fees, and it seems silly to pay for those as well.
a
Make sure you use Test entities (customers, vendors, etc.) so you don’t inadvertently send emails to real contacts. Testing in Production is doable, frankly, I even prefer that because it eliminates recreation of additional configs post-testing from Sandbox to Production.
3
k
There are definitely pieces I test in production during an implementation from scratch. No sense configuring big pieces in both places.
I second using test customers.
Might even use test items that post to funny spots on the GL so they stick out if they somehow get brought back to life
r
yes TEST versions of everything so you can run financials and get a script to delete transactions after.
r
Are you saying your partner charges you Sandbox fees on top of what NS charges for a Sandbox? I'd find a new partner. That's ridiculous if that's what you mean.
k
Actually, I missed that completely.
n
@RJMNS Yes, and to be clear, this partner is an EDI provider. They are asking $300/month additional for a sandbox account on their platform.
k
Oh. An edi partner charging for their sandbox makes sense
I wouldn't implement edi in production
n
@KevinJ of Kansas could you elaborate on why not?
k
EDI normally takes multiple attempts to get right - including testing transactions and communication back and forth with your end customers
It's a good way to wind up with people cranky because of lost/mistaken transactions.
Also - I almost always wind up implementing EDI post - go live after you have real transactions in the system - differentiating these from test transactions becomes an issue if you are pushing through any sort of volume in your testing
1