Create WM Test Case
Published on August 24, 2026 Agile Manager
Creating a WM Test Case
A WM Test Case is used to define and document quality assurance checks that verify your deliverables work correctly. Test cases outline what should be tested, how to test it, and what the expected outcome should be. Creating test cases ensures your team has a clear quality checklist before marking stories as complete.
🔡 Create a New WM Test Case
Follow these steps to create a test case for a story:
- Open Agile Manager
Click the App Launcher (9-dot grid icon) and select Agile Manager. - Navigate to Stories
Click on WM Stories in the navigation menu or access stories from your sprint or project. - Open the Story
Click on the specific story record that you want to add test cases for. - Scroll to Test Cases
On the story detail page, scroll down to find the WM Test Cases related list. - Click New Test Case
Click the New button in the WM Test Cases section to open the test case creation form.
- Fill in Test Case Details
Enter the following information:- Test Case Name: A clear name describing what is being tested (e.g., "User Login - Valid Credentials")
- Description: Detailed description of what needs to be tested
- Pre-conditions: Any setup or prerequisites needed before running the test (optional)
- Test Steps: Step-by-step instructions on how to perform the test
- Expected Result: What should happen if the test passes
- Priority: Set as High, Medium, or Low based on importance
- Status: Mark as Not Tested, In Progress, Passed, or Failed
- Save the Test Case
Click Save. The test case is now created and linked to your story.
📌 Next Steps After Creating a Test Case
Once your test case is created, you can:
- Execute the Test: Run the test steps and document the results
- Log Test Results: Create a WM Test Result record to capture pass/fail outcomes
- Report Bugs: If the test fails, create a WM Issue to track the defect
- Track Coverage: View all test cases for a story to ensure complete coverage
- Reuse Test Cases: Copy test cases across similar stories to improve QA efficiency
💫 Writing Effective Test Cases
- Be specific: Clearly describe what is being tested, not just "test the login"
- Use clear language: Write steps that anyone on the team can follow without guessing
- Include edge cases: Test not just happy paths but also error conditions and boundary cases
- Document pre-conditions: Make sure testers know exactly what state the system should be in before starting
- Define expected results: Be explicit about what "passing" looks like—don't leave it to interpretation
- Keep them independent: Each test case should be runnable on its own, not dependent on other tests
💫 Test Case Example
Test Case Name: User Login with Valid Credentials
Pre-conditions: User account exists and is active in the system
Steps:
1. Navigate to the login page
2. Enter valid username
3. Enter valid password
4. Click "Login" button
Expected Result: User is logged in successfully and redirected to the dashboard
❓ Troubleshooting
Can't see the WM Test Cases related list? Make sure you're on the story detail page (not the list view) and scroll down to find the related lists section.
New button not appearing? Verify you have the Agile Manager User permission set assigned and that the story record is saved.
Test case not saving? Check that all required fields (marked with *) are filled in. Test Case Name and Expected Result are typically required. Contact support at info@codeylabs.com if issues persist.
Knowledge Article Number: KA-00363