Documentation Index
Fetch the complete documentation index at: https://docs.testfactors.com/llms.txt
Use this file to discover all available pages before exploring further.
FactorBot is the fastest way to get an answer about your project. Faster than searching, faster than asking a colleague, and it cites its sources so you can verify.
What FactorBot does
FactorBot is an AI assistant built into TestFactors that knows everything about your current project:- Every uploaded workbook (every sheet, every cell)
- Every scenario, test case, and script
- Every defect logged in any cycle
- Every entry in your project’s knowledge wiki
- Every membership and permission in your project
“Which scenarios cover hire flows for international employees?” “Show me all defects logged on the Hire wizard this cycle.” “What does Iteration 2 mean on the Position Management sheet?” “Who’s the assigned tester for the Compensation module?” “What’s the difference between Test Cases TC-042 and TC-043?” “Summarize the open defects by severity.” “What workbook changes between v2 and v3 of the FO workbook?”
Who can use FactorBot
| Role | Can chat | Can see all project data | Can run actions |
|---|---|---|---|
| All project members | Yes | Scoped to what you can see in the UI | Limited (read-only for now; some safe actions available) |
Where to find FactorBot
The FactorBot chat icon appears in the bottom-right corner of every page when you’re inside a project. Click to open a side panel.
Step-by-step: ask your first question
Type a question
Just write what you want to know in plain English. Don’t worry about phrasing — FactorBot understands typos, partial questions, and conversational tone.Example: “how many test cases for hire”
Read the answer
FactorBot streams the answer in real time. Every claim has a citation badge — click it to jump to the source.Example response:
You have 18 test cases related to hire flows across 3 categories:Of those, 15 are Active and 3 are still Proposed. Want me to open the Proposed ones for review?
- Hire (12 cases) —
Category: Hire[↗]- Rehire (4 cases) —
Category: Rehire[↗]- Concurrent Hire (2 cases) —
Category: Concurrency[↗]
Follow up
Reply to refine. FactorBot keeps the conversation context:
“Yes, show me the proposed ones”FactorBot opens the list in the main pane or directly cites the 3 proposals with links.
That’s it. Your first question. FactorBot remembers the conversation, so follow-ups feel natural.
What FactorBot is great at
Finding things
“Where’s the defect about the picklist on the Job Code field?” — beats manual searching every time.
Summarizing
“Summarize this cycle’s progress.” / “What are the top 3 risks right now?”
Explaining
“What does the AI mean by ‘high_null_rate’ on this column?” — FactorBot reads the docs so you don’t have to.
Comparing
“How is test case TC-042 different from TC-051?” — diff view in plain English.
Workbook lookups
“What’s the expected behavior for a Position with no manager assigned?” — FactorBot finds the relevant workbook cell.
Status questions
“Who hasn’t started their assignments yet?” — saves you a trip to the dashboard.
What FactorBot is less great at
Predicting the future
“Will we hit the deadline?” — FactorBot can summarize progress and velocity, but human judgment makes the call.
Strategic decisions
“Should we skip regression testing this cycle?” — that’s a call you make.
External information
FactorBot doesn’t browse the internet or know things outside your TestFactors project. For SF help, use SAP’s documentation.
Destructive actions
By design FactorBot won’t delete defects, archive test cases, or remove members on its own — those need explicit human action in the UI.
Tips
Be specific when you can
“Show me Critical defects in EC logged this week” beats “What’s broken?”. Specifics get crisper answers.
Don't pre-format your question
No need for keywords or jargon. Conversational works fine: “i think there’s a defect about the wizard. can you find it?”
Use it for onboarding new team members
“Walk me through this project — what’s the goal of this cycle?” — FactorBot gives a great orientation.
Ask for the data, not the conclusion
“Show me defect counts by severity” gets you a table. “Is the project healthy?” gets you opinion. Pick the right one.
Click citations
Don’t trust the summary — verify the source. FactorBot is right 95% of the time and wrong 5% — knowing which is which matters.
Start a new chat for new topics
Long conversations get muddled. Use the + New chat button to reset context when switching subjects.
Conversation history
FactorBot keeps your chat history per project. The history panel (left side of the chat) shows recent conversations grouped by date.- Search history with the input at the top
- Pin important conversations so they stay at the top
- Delete conversations you don’t need
- Share a conversation with a teammate (sends a link they can view)
Troubleshooting
FactorBot says 'I don't have access to that information'
FactorBot says 'I don't have access to that information'
Two possible causes:
- You don’t have permission to see the data you’re asking about (e.g. defects in a project you’re not a member of). FactorBot respects your permissions — ask your Admin if you should have access.
- The data doesn’t exist yet — e.g. asking about scenarios when none have been generated. Use the relevant module to create the data first.
The answer cites the wrong source
The answer cites the wrong source
Click the thumbs-down on the response with a one-line note describing what was wrong. This trains the model. The right answer is often one follow-up question away: “That citation looks wrong — can you double-check against the v3 workbook?”
FactorBot is slow / unresponsive
FactorBot is slow / unresponsive
Most responses come within 3–10 seconds. If it’s taking 30+:
- Cancel and retry (the Stop button in the chat input)
- Refresh the page
- If it’s still slow, your AI service may be experiencing latency — try again in a few minutes
The answer is too short / lacks detail
The answer is too short / lacks detail
Ask a follow-up: “Can you give me more detail on the second point?” or “Show me 10 examples instead of 3.” FactorBot calibrates to what you ask for.
I want to share a chat with a colleague
I want to share a chat with a colleague
FactorBot doesn't know about a workbook I just uploaded
FactorBot doesn't know about a workbook I just uploaded
Workbooks need to finish processing before FactorBot can read them. Check the Workbooks tab — once it says “Ready”, FactorBot will see it within ~30 seconds.
Related guides
Knowledge Wiki
Add domain knowledge so FactorBot’s answers get smarter over time.
Workbooks
FactorBot’s accuracy depends on clean, processed workbooks.
Defects
Ask FactorBot to find, summarize, or compare defects.
Test Cases
Use FactorBot to find specific test cases when there are too many to scroll through.