Note - Not Found

Product Name: Treeify Version: 0.2-beta Date: 2025.07.10

When you see <Note: NOT found in PRD> in Treeify’s generated test logic, it means the AI was unable to find this information in your uploaded requirement document (PRD, user story, spec, etc.). Instead of guessing or staying silent, Treeify explicitly marks the gap — so you stay in control.

🔍 Why It Happens

Treeify uses advanced AI to extract system behavior and test logic from your input documents. However, when key details are missing, vague, or ambiguous, the AI:

Flags it with <Note: NOT found in PRD>
Inserts a placeholder so you know what needs attention
Avoids hallucination (making up test logic that wasn’t actually specified)

📌 Common Scenarios

When it Appears	Why It Happens
A precondition is marked as NOT found	The requirement didn’t mention setup conditions explicitly
Role-based behavior is flagged	No access control or user role logic was found in the input
An expected result is missing	The outcome or result logic is not described in the spec
Edge cases or exceptions are noted as missing	The document lacks error handling or alternative flows

🛠 How to Handle It

When you see a <Note: NOT found in PRD>:

✅ Option 1: Provide the Missing Information

First:

Ask your product owner for clarification
Review assumptions with developers
Strengthen requirement quality before testing begins

Then:

Option 1: Edit the original requirement
Option 2: Add a Note on the specific node to clarify the missing logic. Then click Regenerate — Treeify will update the result with your correction. (Coming Soon Smart Note Generation feature)

✅ Option 2: Accept It As Is

If the missing detail is acceptable (e.g., it's standard behavior or handled elsewhere), you can proceed with the placeholder or manually complete the test logic.

🚫 Why Treeify Doesn’t Guess

Most AI tools will hallucinate — they’ll invent expected outcomes, behaviors, or logic not grounded in your input. Treeify does the opposite:

❗ If it’s not in your document, Treeify tells you.

This approach:

Ensures trust and traceability
Prevents false coverage
Encourages better requirement hygiene

💬 Example

{
	"step": "User clicks 'Submit' on the checkout page",
	"expected_result": "<Note: NOT found in PRD> — Expected outcome for submission missing"
}

You might revise this by adding:

“The user should see a confirmation screen with order details.”

Then click Regenerate — and Treeify will incorporate it into a complete, traceable scenario.

✨ In Summary

<Note: NOT found in PRD> = AI didn't find the info and flags it clearly
It helps you stay in control of test logic quality
Use it to improve input clarity, not as a blocker

🧠 Better specs = better test logic. And Treeify helps you close the gap — one note at a time.

Note - Not Found

On this page