Get started with your AI assistant
Connecting your favorite AI assistant is the fastest and easiest way to get started with Nunu. It can use your code and docs to write your first tests, run them against a build, and schedule future runs.
Upload a build and connect the Nunu MCP. Then use the prompts below to create your tests, see how they run, and decide whether to automate them.
Upload a build
Open your project in Nexus and upload your build under Build Storage.
Connect Nunu
Add a remote MCP server in your AI client with this URL:
https://nunu.ai/mcpConnect with OAuth using your Nexus account.
See the MCP setup guide for connection details and local MCP options.
Create and run your first tests
Use a session where your assistant has access to your code and docs.
Paste this prompt. If you have a feature in mind, tell your assistant to focus on it.
Create and run my first Nunu tests using my available project and build.
If there are multiple projects or builds to choose from, ask me which to use.
Use the code and docs you can access to pick 2–3 important user flows.
Read Nunu's verification test authoring skill, then create one test per
flow with clear setup, steps, and expected results based on the requirements.
Reuse any existing tests and configs that fit.
Put the tests in a test plan and run it against that build. If you need
something like a test account to continue, ask me.
Share links to the tests, plan, and run, with a short summary of what
the tests cover.Review the results
Use this next prompt in the same conversation so your assistant knows which run to review.
Review the test plan run we just started. Wait for it to finish, then
look at the results and supporting evidence.
Summarize what passed and what needs attention. For each failure,
explain whether it looks like a product bug, a setup problem, or an
unclear test instruction.
Fix any setup or test instruction issues you can resolve and rerun
the affected tests once. Keep the expected results aligned with the
requirements. Share the updated results and evidence for any product bugs.Follow the results link your assistant gives you, or open History → Test Plan Runs in Nexus. Check the reports and recordings to see what Nunu tested and what it found.
Set up a trigger when you’re ready
Once you’re happy with the tests, use this prompt to run the plan regularly.
Set up a trigger for this test plan to run every day at 02:00 UTC,
using the deployment config we just used. Reuse a matching trigger
if one exists, or create a new one, and enable it.Choose a schedule that works for you. If you’d rather test each new build, replace the daily schedule request with: “Run this plan whenever a new build is uploaded to Build Storage.”
As you work on new features, you can ask the same assistant to add coverage using the code and specs you’re already working with.