Create WM Test Result

Published on August 24, 2026 Agile Manager

Creating a WM Test Result

A WM Test Result documents the outcome of running a test case during QA execution. Test results record whether tests passed or failed, capture any issues discovered, and provide evidence that testing was completed. Creating test results helps your team track QA progress and identify blockers before release.

✅ Create a New WM Test Result

Follow these steps to record a test execution result:

1. Open Agile Manager
   Click the App Launcher (9-dot grid icon) and select Agile Manager.
2. Navigate to Test Cases
   Click on WM Test Cases in the navigation menu, or access test cases from your story or sprint.
3. Open the Test Case
   Click on the specific test case you want to record results for.
4. Scroll to Test Results
   On the test case detail page, scroll down to find the WM Test Results related list.
5. Click New Test Result
   Click the New button in the WM Test Results section to open the result recording form.

6. Fill in Test Result Details
   Enter the following information:
   • Test Status: Select Passed, Failed, Blocked, or Skipped based on the execution outcome
   • Execution Date: Record when the test was executed
   • Executed By: Identify who performed the test (usually auto-populated with current user)
   • Actual Result: Document what actually happened when you ran the test
   • Execution Notes: Add any observations, issues encountered, or additional context
   • Defect/Issue Link (if applicable): Link to any bugs discovered during testing
7. Save the Test Result
   Click Save. The test result is now recorded and linked to your test case.

📌 Next Steps After Recording a Test Result

Once your test result is recorded, you can:

• Log Issues: If the test failed, create a WM Issue to track the bug for the development team
• Update Test Case Status: Mark the test case itself as Passed or Failed based on results
• Create Follow-up Tests: If issues are found, add new test cases to verify the fix
• Track QA Metrics: Monitor pass/fail rates across all test results to gauge release readiness
• Generate Reports: Use test results to create QA reports for stakeholders

💫 Test Status Guide

• Passed: The test was executed and all expected results matched. No issues found. This test case is verified.
• Failed: The test was executed but the actual result did not match the expected result. A defect was found and must be logged.
• Blocked: The test could not be executed due to a blocker (e.g., dependent feature not ready, environment issue). Document the blocker in notes.
• Skipped: The test was intentionally not executed (e.g., out of scope, low priority). Explain why in the notes.

💫 Best Practices for Test Results

• Be detailed: Describe exactly what you saw, including screenshots or error messages when tests fail
• Document blockers: If a test is blocked, explain clearly what needs to happen before you can run it
• Link issues immediately: Create and link defects to failed tests right away so developers can start fixing
• Retest after fixes: Create a new test result when bugs are fixed to verify they're actually resolved
• Track timing: Record when tests are executed to establish a timeline for the sprint

Knowledge Article Number: KA-00364