How do I turn off print at home for the test environment? **self-hosted**

My first question is, "Why do you want to turn off PAHT in Test?". We like having it available for testing.

In my experience, it's primarily to prevent accidentally sending emails to real customers. This can happen if someone places an order for a customer (like training a box office user, testing something unrelated, etc.), or when you complete a live to test copy and you happen to catch an unprinted PAH order that gets processed in Test. Not only could this be unexpected or confusing for a customer, but they may inadvertently keep and use the Test ticket in the Production environment, and that can lead to all kinds of confusion for everyone.

Ashley and Jerry may have additional reasons to share as well. 

In my experience, it's primarily to prevent accidentally sending emails to real customers. This can happen if someone places an order for a customer (like training a box office user, testing something unrelated, etc.), or when you complete a live to test copy and you happen to catch an unprinted PAH order that gets processed in Test. Not only could this be unexpected or confusing for a customer, but they may inadvertently keep and use the Test ticket in the Production environment, and that can lead to all kinds of confusion for everyone.

Ashley and Jerry may have additional reasons to share as well. 

They're still going to get confirmation emails and password reset emails, which seems bad enough.  Also, testing ticket sales and PAHT delivery are part of our standard upgrade testing scripts.

We rarely use actual customer accounts for testing, but to really prevent that from happening I mangle all customer emails in Test.  We use Gmail for our mail service, and so I take the email address, replace the "@" with a "+", then insert it into an internal email: [internal username]+[mangled customer email]@calperformances.org.

For added identification (and filtering) we change all of our FROM and BCC addresses in Test to use a labeled alias (i.e. confirmations-test@ instead of confirmations@)

With regular tickets we have a design element that looks at campaign name, and if it detects the control character ("|" for us) in front, then it covers the ticket with "VOID".  Part of our Live->Test post copy scripting prepends all ticketing campaign names with the character.  Alas you can't do conditionals in PAHT ticket designs, but one could consider just having two templates.  We haven't bothered as the email address mangling covers us fairly well.

We're moving to Mobile Tickets (although, spoiler, they don't send well in the client currently) where, again, the email change generally protects us, but at some point I might want to revisit security around the tickets themselves.