Faraz Aleem
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # 3944 Dogfooding [Dogfooding](https://deviq.com/practices/dogfooding) is to run through as many relevant user scenarios as possible. Ideally, the individual scenarios work perfectly as intended. The reason it's important that we go through this process is to ensure the feature is ready for production. The purpose of internal testing is to identify potential gaps or defects so that items can be resolved prior to release. ## Capturing deficiencies It's best that we document any issues that we discover in as much of a uniform standard as possible so that upon later review, we're able to parse the individual instances as easily as possible for potential translation to tech debt/tech improvement Jira tickets. </br> Here's the template that we've decided to use for this session. So the goal is to fill it our for each individual discovery as throroughly as possible to capture the maximum amount of information on the particular issue: 1. Description of issue 2. Expected result (what **should've** occurred) 3. Actual result (what **did** occur) 4. Steps to reproduce 5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage) 5. Relevant screenshot(s) * screenshots are easy to add to hackMD, simply capture the shot you want on your machine, then drag and drop it into the doc like so:![](https://i.imgur.com/BMGvEp7.png) ## Testers and Test IDs | Tester | Scenario | Test ID |PO Office | VISN/ VAMC Queue |Vet ID | | -------- | ------- | -------- |-------- | ------- |------- | | Heather | 1-3 | Text | Prosthetics | Manchester VA Medical Center (VISN 1) | 700061780 | | Sean | 1-3 | Text | Beneficiary Travel | VA New Jersey Health Care System (VISN 2) | 796123018 | | Prajwal | 4-6 | Text | Veteran and Family Member | VISN 23 - VA Midwest Health Care Network | 764067367 | | Craig | 4-6 | Text | Health Eligibility | VISN 22 - Desert Pacific Healthcare Network | 76410445 | | Faraz | 4-6 | Text |Payment Operations | VISN 21 - Sierra Pacific Network | 141102026 | ## Pass/Fail | Test | PASS/FAIL | | -------- | -------- | | 1. Heather - Scenario 1 | PASS | | 1. Heather - Scenario 2 | PASS | | 1. Heather - Scenario 3 | PASS | | 2. Sean - Scenario 1 | PASS | | 2. Sean - Scenario 2 | PASS | | 2. Sean - Scenario 3 | PASS | | 3. Prajwal - Scenario 4 | PASS | | 3. Prajwal - Scenario 5 | PASS | | 3. Prajwal - Scenario 6 | PASS| | 4. Craig - Scenario 4 | | | 4. Craig - Scenario 5 | | | 4. Craig - Scenario 6 | | | 5. Faraz - Scenario 4 | PASS | | 5. Faraz - Scenario 5 | PASS | | 5. Faraz - Scenario 6 | PASS | ## USERS CAMO & PO Users - CF_HOOVER 283 VISN - CF_Q_317 317 ## Scenarios ### 1 Navigate an appeal from PO Office to VISN Queue using VAMC radio button x 3 PO Office > Place on Hold 45 days > Unhold > Mark in Progress > Assign to VISN > VISN Radio button > Verify in VISN queue 1. Sign in as a PO User CF_HOOVER 2. Navigate to any Program Office 3. Verify the following tabs exist in the VHA Program Office Queue - Assigned - In Progress - Ready for review - On Hold - Completed 5. Select an appeal and navigate to the case details page 6. Select the task actions dropdown and verify the following task actions are present - Mark task in progress - Put task on hold - Assign to VISN - Documents ready for VHA CAMO review - Return to VHA CAMO 7. Select the Mark task in progress task action 8. Verify a modal appears stating "By marking task as in progress, you are confirming that you are actively working on collecting documents for this appeal. Once marked, other members of your organization will no longer be able to mark this task as in progress." 9. Select the "Mark in Progress" button 10. Verify you are brought to the "In Progress" tab in the PO queue and the appeal is now in this tab 11. Select the appeal, verify the "Mark in Progress" task action is no longer an available selection 12. Select the "Put task on hold" option from the drop down 13. Verify a modal appears allowing you to select how many days you want to place the appeal on hold for and 45 days is an option 14. Select 45 days and place the appeal on hold 15. Verify you are brought to the "On hold" tab and the appeal you put on hold is now in this tab 16. Verify there is a message stating the case has been placed on hold 17. Select the appeal and navigate to case details 18. Select the task action dropdown and verify there is an "End hold early" task action, select it 19. Verify a modal now appears and select the "End Hold" button 20. Verify you remain on the case details page 21. Select the appeal and navigate to the case details page 22. Verify the "End hold early" task action is not available in the dropdown anymore and verify "Put task on hold" is an option again 23. Select the "Assign to VISN" task action 24. Verify a modal appears "Assign to VAMC/VISN" 25. Verify there are two radio buttons "VA Medical Center" and "VISN" 26. Select the "VAMC" radio button 27. Verify the dropdown has VAMCs in alphabetical order 28. Select your assigned VISN (table above) 29. Verify the VISN associated is correct (table above) 30. Select the "Assign" button 31. Verify the appeal is now in the "On hold" tab in the PO queue and a message appears confirming the appeal has been sent to the respective VISN ### 2 Navigate an appeal from VISN queue back to PO Office for Review x3 VISN queue > Place on Hold 45 days > Unhold > Mark in Progress > Documents ready for PO review > Verify in PO queue 1. Sign in as CF_Q_317 2. Navigate to the VISN queue you sent the appeal to 3. Verify the following tabs exist in the VISN queue - Assigned - In Progress - On Hold - Completed 5. Select an appeal and navigate to the case details page 6. Select the task actions dropdown and verify the following task actions are present - Mark task in progress - Put task on hold - Documents ready for Program Office review - Return to Program Office 7. Select the "Mark task in progress" option from the dropdown and verify a modal appears 8. Verify the modal states the following Modal Header: Mark task in progress | Modal Informational text: By marking task as in progress, you are confirming that you are actively working on collecting documents for this appeal. Once marked, other members of your organization will no longer be able to mark this task as in progress 9. Select the Mark In Progress button and verify you are navigated to the VISN "In Progress" tab and a message appears confirming the case has successfully been marked in progress 10. Verify the appeal is in the "In Progress" tab in the VISN queue 11. Select the appeal and navigate to the case details section 12. Verify the Mark task in progress is no longer in the dropdown 13. Select the "Put task on hold" and verify a modal appears stating the following Modal Header: Put task on hold |Modal Informational text: Select number of days (Value must be between 0 and 45)| User is required to select the number of days to place the appeal on hold45 days is added as an option for selection | User is required to add additional details for this action in the Notes section Required free text field 14. Select the custom option and type in 45 (days) to place the appeal on hold, fill out any required info and select the "Put on hold" button 15. Verify you are brought to the On Hold tab in VISN queue and a message appears comfirming the case was move to the on hold tab 16. Verify the appeal is in the On Hold tab 17. Select the appeal and navigate to case details 18. Select the task action dropdown and verify there is an "End hold early" task action, select it 19. Verify a modal now appears and select the "End Hold" button 20. Verify you are kept on the case details page 21. Select the appeal and navigate to the case details page 22. Verify the "End hold early" task action is not available in the dropdown anymore and verify "Put task on hold" is an option again 23. Select the "Documents ready for VHA Program Office review" task action 24. Verify a modal appears and contains the following information -Modal Header: Ready for review -Modal information text: This appeal will be sent to the Program Office for review. Please select where the documents for this appeal are stored. -User is required to select where the document is stored from the following options VBMS Centralized Mail Portal Other -User may add additional details on file structure or file path 25. Fill out the modal with required information and click the "Send" button 26. Verify you are brought to the 'Completed' tab and there is a message confirming the appeal has been sent to the program office for review 27. Verify the appeal is in the completed tab 28. Sign in as CF_HOOVER (283) 29. Verify the appeal is now in the "Ready for Review" tab in the PO Queue ### 3 Navigate an appeal from PO Office to CAMO review x3 PO Office > Documents ready for CAMO review 1. Select the appeal and navigate to case details 2. Select the task actions dropdown 3. Select Documents ready for VHA CAMO review 4. Select the cancel button 5. Verify you remain on the case details page 6. Select the task actions dropdown 7. Select Documents ready for VHA CAMO review 8. Verify the modal reads the following 9. Modal Header: Ready for review| Modal information text: This appeal will be sent to VHA CAMO for review. Please select where the documents for this appeal are stored. 10. Select Other 11. Verify the "Send" button is disabled 12. Fill out required text field "Why is Faraz so good at writing these documents" 13. Verify "Send" button is enabled, click it 14. Verify you are brought to the completed tab and the appeal is now in the completed tab 15. Verify a message appears confirming the case is in the completed tab 16. Navigate to the CAMO queue 17. Verify your appeal is now in the Assigned tab of the CAMO queue ### 4 Navigate an appeal from PO Office to VISN Queue using VAMC radio button x 3 PO Office > Place on Hold custom > Unhold > Mark in Progress > Assign to VISN > VAMC Radio button > Verify in VISN queue 1. Sign in as a PO User CF_HOOVER (283) 2. Navigate to any Program Office 3. Verify the following tabs exist in the VHA Program Office Queue - Assigned - In Progress - Ready for review - On Hold - Completed 5. Select an appeal and navigate to the case details page 6. Select the task actions dropdown and verify the following task actions are present - Mark task in progress - Put task on hold - Assign to VISN - Documents ready for VHA CAMO review - Return to VHA CAMO 7. Select the Mark task in progress task action 8. Verify a modal appears stating "By marking task as in progress, you are confirming that you are actively working on collecting documents for this appeal. Once marked, other members of your organization will no longer be able to mark this task as in progress." 10. Verify you are brought to the "In Progress" tab in the PO queue and the appeal is now in this tab 11. Select the appeal, verify the "Mark in Progress" task action is no longer an available selection 12. Select the "Put task on hold" option from the drop down 13. Verify a modal appears allowing you to select how many days you want to place the appeal on hold for and 45 days is an option 14. Select 45 days and place the appeal on hold 15. Verify you are brought to the "On hold" tab and the appeal you put on hold is now in this tab 16. Verify there is a message stating the case has been placed on hold 17. Select the appeal and navigate to case details 18. Select the task action dropdown and verify there is an "End hold early" task action, select it 19. Verify a modal now appears and select the "End Hold" button 20. Verify you are kept on the case details page 21. Select the appeal and navigate to the case details page 22. Verify the "End hold early" task action is not available in the dropdown anymore and verify "Put task on hold" is an option again 23. Select the "Assign to VISN" task action 24. Verify a modal appears "Assign to VAMC/VISN" 25. Verify there are two radio buttons "VA Medical Center" and "VISN" 26. Select the VISN radio button 27. Verify Assign button is unclickable 28. Select Your assigned VISN 29. Verify there are 18 selections in the dropdown 30. Fill out the optional field 31. Select the "Assign" button 32. Verify the appeal is now in the "On hold" tab in the PO queue and a message appears confirming the appeal has been sent to the respective VISN ### 5 Return an appeal from VISN queue to PO Office x 3 VISN queue > Place on Hold 30 days > Unhold > Mark in Progress > Return to PO > Verify in PO queue 1. Sign in as CF_Q_317 2. Navigate to the VISN queue you sent the appeal to 3. Verify the following tabs exist in the VISN queue - Assigned - In Progress - On Hold - Completed 5. Select an appeal and navigate to the case details page 6. Select the task actions dropdown and verify the following task actions are present - Mark task in progress - Put task on hold - Documents ready for Program Office review - Return to Program Office 7. Select the "Mark task in progress" option from the dropdown and verify a modal appears 8. Verify the modal states the following Modal Header: Mark task in progress | Modal Informational text: By marking task as in progress, you are confirming that you are actively working on collecting documents for this appeal. Once marked, other members of your organization will no longer be able to mark this task as in progress 9. Select the Mark In Progress button and verify you are navigated to the VISN "In Progress" tab and a message appears confirming the case has successfully been marked in progress 10. Verify the appeal is in the "In Progress" tab in the VISN queue 11. Select the appeal and navigate to the case details section 12. Verify the Mark task in progress is no longer in the dropdown 13. Select the "Put task on hold" and verify a modal appears stating the following Modal Header: Put task on hold |Modal Informational text: Select number of days (Value must be between 0 and 45)| User is required to select the number of days to place the appeal on hold45 days is added as an option for selection | User is required to add additional details for this action in the Notes section Required free text field 14. Select the 15 day option, fill out any required info and select the "Put on hold" button 15. Verify you are brought to the On Hold tab in VISN queue and a message appears comfirming the case was move to the on hold tab 16. Verify the appeal is in the On Hold tab 17. Select the appeal and navigate to case details 18. Select the task action dropdown and verify there is an "End hold early" task action, select it 19. Verify a modal now appears and select the "End Hold" button 20. Verify you are kept on the case details page 21. Select the appeal and navigate to the case details page 22. Verify the "End hold early" task action is not available in the dropdown anymore and verify "Put task on hold" is an option again 23. Select the Return to Program Office" task action 24. Verify a modal appears and the modal reads Modal Header: Return to Program Office| Modal information text: Why are you returning? Provide any important context 25. Verify "Return" button is unclickable 26. Verify you have to add text in the aditional details section 27. Add text to the text field "Why is Faraz so good at writing dogfooding docs" 28. Select the "Return" button 29. Sign in as PO User CFHOOVER 30. Navigate to the PO queue 31. Verify the appeal is now in the ASSIGNED tab ### 6 Return an appeal to VHA CAMO x 3 PO Office > Return to VHA CAMO 1. Select the appeal and navigate to case details 2. Select the task actions dropdown 3. Select Return to VHA CAMO team 4. Select the cancel button 5. Verify you remain on the case details page 6. Select the task actions dropdown 7. Select Return to VHA CAMO team 8. Verify the modal reads the following Modal Header: Return to VHA CAMO team | Modal information text: Why are you returning? Provide any important context 9. Fill out all required fields and select submit 10. Click the return button 11. Verify you are brought to the completed tab and the appeal is not in the completed tab 12. Navigate to CAMO queue and verify the appeal is in the assigned tab

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully