# Testnet Etiquette?
**URL:** https://forum.flow.com/t/testnet-etiquette/2072
**Category:** New To Flow
**Created:** [June 14, 2021, 4:25pm UTC](https://forum.flow.com/t/testnet-etiquette/2072 "2021-06-14T16:25:28Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@aphelionz](https://forum.flow.com/u/aphelionz)
#### Post date: [June 14, 2021, 4:25pm UTC](https://forum.flow.com/t/testnet-etiquette/2072/1 "2021-06-14T16:25:28Z")
Hello folks, Mark here from [Equilibrium](https://equilibrium.co). We’re working on a Cadence project and are building our CI/CD flow to include smoke testing on testnet.
What we’re wondering is - what is the proper etiquette, if any, with regards to deploying contracts and creating accounts on testnet? We obviously don’t want to flood the system: our target is a handful of upgradable contracts with new accounts generated for each test run. Is that reasonable?
If not, we’re happy to follow any provided guidance 🙂
---
### Author:  [@flowjosh](https://forum.flow.com/u/flowjosh)
#### Post date: [June 15, 2021, 3:32pm UTC](https://forum.flow.com/t/testnet-etiquette/2072/2 "2021-06-15T15:32:06Z")
I would recommend defaulting to using the emulator for any automated testing you have to do unless absolutely necessary. We usually recommend that teams use testnet for testing staging apps and such. Testnet can probably handle whatever you are trying to do, but you’ll probably be rate limited if it gets too crazy and testnet is just a bit more complex than the emulator anyway.