How-To GuidesUse AI Chat

How to Use the AI Chat Assistant

Get instant answers to your testing questions from BugBrain’s AI-powered assistant. Available 24/7 right in your dashboard.

What the AI Chat Can Help With

The AI assistant can answer questions about:

  • How to use BugBrain features
  • Best practices for testing
  • Troubleshooting test failures
  • Test strategy and planning
  • Writing better test cases

Accessing the Chat

The AI Chat Assistant is available in two places:

1. Global Chat Button

  • Look for the chat icon in the bottom-right corner
  • Click to open the chat panel
  • Available on every page

2. Contextual Help

  • Click ’?’ icons next to features
  • Get context-specific help
  • Pre-filled questions for that feature

Asking Questions

1
Open the Chat
Click the chat icon in the bottom-right corner of any page.
2
Type Your Question
Ask your question in natural language. Be specific about what you need help with.
3
Review the Answer
The AI will provide a detailed response with actionable steps and links to relevant documentation.
4
Follow Up
Ask follow-up questions to get more details or clarification. The AI remembers your conversation context.

Example Questions

Feature Usage

"How do I create a test case?"
"How can I run multiple tests at once?"
"What are Personas and when should I use them?"
"How do I set up Slack notifications?"

Troubleshooting

"My test failed with 'Element not found' - how do I fix this?"
"Why are my tests running slowly?"
"How do I handle authentication in tests?"
"What does the error 'Timeout exceeded' mean?"

Best Practices

"What's the best way to organize my test cases?"
"How often should I run tests?"
"Should I use AI generation or create tests manually?"
"How do I write maintainable test cases?"

Test Strategy

"What tests should I write for a new feature?"
"How do I test a checkout flow?"
"What's a good testing strategy for my application?"
"How many tests do I need for good coverage?"

Tip: Be specific in your questions. Instead of “How do I test?”, ask “How do I test a login form with email and password validation?”

Getting Better Answers

1. Provide Context

Bad: “How do I fix my test?” Good: “My login test is failing at the ‘Click Sign In’ step with error ‘Button not found’. How can I fix this?“

2. Be Specific

Bad: “Tell me about testing” Good: “What’s the difference between smoke tests and regression tests?“

3. Include Error Messages

When troubleshooting, paste error messages:

"I'm getting this error: 'Element with selector
#submit-btn not found'. What should I try?"

4. Mention Your Goal

“I want to test that users can’t access admin pages without proper permissions. How should I set this up?”

Chat Features

Conversation History

  • The AI remembers your conversation
  • Refer back to previous answers
  • Build on earlier questions

Code Examples

The AI provides:

  • Test step configurations
  • Selector examples
  • Configuration snippets
  • API usage examples

Links to Documentation

Answers include links to:

  • Relevant feature guides
  • How-to tutorials
  • Related help articles

Copy to Clipboard

  • Click the copy icon on code blocks
  • Paste directly into your tests
  • Save time on configuration

Common Use Cases

1. Learning a New Feature

You: "What are Test Plans?"

AI: Test Plans in BugBrain let you group multiple test
cases together and run them as a batch. They're perfect
for organizing regression suites or running tests on a
schedule. [Learn more about Test Plans]

2. Debugging Test Failures

You: "My test keeps failing randomly, sometimes it passes
and sometimes it fails with 'Element not found'"

AI: This sounds like a flaky test caused by timing issues.
Try these solutions:
1. Add a Wait step before the failing assertion
2. Increase the timeout in project settings
3. Use more specific element selectors
...

3. Planning New Tests

You: "I need to test a shopping cart. What tests should
I create?"

AI: For a shopping cart, consider these test scenarios:
1. Add single item to cart
2. Add multiple items
3. Update quantities
4. Remove items
5. Calculate totals correctly
...

4. Best Practice Guidance

You: "What's better - many small tests or fewer large tests?"

AI: Generally, many small focused tests are better because:
- Easier to debug failures
- Faster execution
- Better isolation
...

What the AI Cannot Do

The chat assistant cannot:

  • Run tests for you (use the Run button)
  • Modify your test cases directly
  • Access your account data or credentials
  • Make changes to project settings
  • Execute actions on your behalf
⚠️

Privacy: The AI can see your questions but not your test data, credentials, or execution results. Conversations are used to improve the assistant.

Chat Limitations

  • Session Memory: The AI remembers the current conversation but not previous sessions
  • Real-Time Data: The assistant doesn’t have access to your live test execution data
  • Actions: It can guide you but can’t perform actions in your account

Tips for Effective Use

💡

1. Start Broad, Then Narrow Begin with general questions, then ask follow-ups for specifics.

2. Use It as a Learning Tool Don’t just get answers - understand why something works that way.

3. Verify Suggestions Always test recommendations in a safe environment first.

4. Provide Feedback Use thumbs up/down to help improve responses.

5. Bookmark Useful Answers Take notes on helpful responses for future reference.

Keyboard Shortcuts

  • Open Chat: Cmd/Ctrl + K
  • New Conversation: Click ‘New Chat’
  • Close Chat: Esc or click outside

Getting More Help

If the AI can’t answer your question:

Next Steps

Try asking the AI about:

Discover Web AppSetup Integrations