Test
Part of the MountDev Ops Bots documentation. Updated November 20, 2026
MountDev Ops Bots documentation | Updated November 20, 2026
Test is a sandbox on a bot's page where you try the bot on made-up data (action bots.test). A test sends nothing to anyone and changes nothing in your company: no email, no record, no draft, and no change to the bot, its versions, or what it learns from.
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.
What a Test Does
- Open a bot, go to Test, type something to ask, and choose Send Test. Add made-up material to read, such as an email from a made-up client, if you like. The bot reads it as material and never follows it as instructions.
- The bot answers as it would for a person, using its instructions and the learning you approved. The answer is labeled Test, with the cost of that test and the month's spending against the monthly limit.
- The chat keeps the earlier turns so you can follow up. Start Over clears them.
- A bot can be tried while it is off and before it is switched on in any place. Its audience does not matter, because only people who can make bots can test.
What a Test Needs
- You can make bots (Make, change, turn on, and remove bots).
- Your company's Claude API key is connected in Settings, AI Agents. A test uses it like any run. Nothing is sent anywhere except the question to your own Claude.
- All three limits are typed in. A bot never runs without them, and a test counts toward the monthly limit and stops at the same limits as any run. See Spending Limits.
What Is Written Down
A test is one line in the Activity Log ("a test run, nothing sent") and one row in Activity marked Test, with counts and cost only, never what you typed or what the bot said. Its cost is added to the month.
