Dawn C Simmons is available for your Digital Transformation needs.

Dawn C Simmons - Digital Business Process
Table of Contents
< All Topics
Print

AutoTest Case Planning

AutoTest Case Planning is designed for ServiceNow Process Owners and AutomatePro users who want to enhance their test automation skills. In this session, you will first learn how to organize and convert existing test records from systems like ALM. Next, you will discover how to create automated tests from acceptance criteria and effectively manage testing for both new users and product upgrades. Additionally, this comprehensive guide covers identifying personas, mapping high-level process flows, grouping tests for maximum efficiency, and providing ongoing support. By the end of this session, you’ll be equipped with the knowledge and tools to streamline your testing processes, ensuring robust and efficient test coverage for your projects.

AutoTest Case Planning Use Case 1: Converting ALM or Other Established System Test Records to AutomatePro

Objective: Organize and convert existing test records from ALM or other systems to AutomatePro, ensuring efficient automation.

Steps for AutoTest Case Planning:

  1. Create a List of Records:
    • First, extract test records from ALM or other systems.
    • Then, identify and categorize test cases.
  2. Identify Personas:
    • Next, determine existing personas from test cases.
    • Identify any new personas required for AutomatePro.
  3. High-Level Process Flow:
    • Map the high-level process flow for each test scenario.
    • Align the test cases with the process flow to determine test sequences.
  4. Group Tests for Automation:
    • Subsequently, group related tests to enhance automation efficiency.
    • Create end-to-end tests for each step, simulating ticket management exchanges.
  5. Track Conversion Progress:
    • Define the “Definition of Done” for the conversion process.
    • Track the conversion status from ALM to AutomatePro.
  6. Create Test Structure in AutomatePro:
    • Finally, organize tests into Product Folders, Test Themes, Test Packs, Model Blocks, and Custom Actions.

Use Case 1: Worksheet for preparing for ALM or Manual Test System Records to Automate Pro:

Here is a survey form for the steps involved in AutoTest Case Planning:

AutoTest Case Planning Survey

Section 1: Create a List of Records

  1. How do you currently extract test records from ALM or other systems?
    • Manually
    • Using automation tools
    • Other (please specify): ________________
  2. How do you categorize test cases after extraction?
    • Based on functionality
    • Based on user personas
    • Other (please specify): ________________

Section 2: Identify Personas 3. How do you determine existing personas from the test cases?

  • Based on user roles
  • Based on usage patterns
  • Other (please specify): ________________
  1. Are there any new personas required for AutomatePro?
    • Yes
    • No
    • Not sure

Section 3: High-Level Process Flow 5. How do you map the high-level process flow for each test scenario?

  • Using flowcharts
  • Using process mapping tools
  • Other (please specify): ________________
  1. How do you align test cases with the process flow to determine test sequences?
    • Manually
    • Using tools
    • Other (please specify): ________________

Section 4: Group Tests for Automation 7. How do you group related tests to enhance automation efficiency?

  • By functionality
  • By process steps
  • Other (please specify): ________________
  1. Do you create end-to-end tests for each step, simulating ticket management exchanges?
    • Yes
    • No

Section 5: Track Conversion Progress 9. What is your “Definition of Done” for the conversion process?

  • When tests are successfully automated
  • When tests pass all criteria
  • Other (please specify): ________________
  1. How do you track the conversion status from ALM to AutomatePro?
    • Using project management tools
    • Manually
    • Other (please specify): ________________

Section 6: Create Test Structure in AutomatePro 11. How do you organize tests into Product Folders, Test Themes, Test Packs, Model Blocks, and Custom Actions? – [ ] Using predefined templates – [ ] Manually based on project needs – [ ] Other (please specify): ________________

Additional Comments

Please provide any additional comments or suggestions related to AutoTest Case Planning:


Use Case 2: AutoTest Case Planning from Acceptance Criteria

Objective: Develop automated test cases from acceptance criteria using actions and checks in AutomatePro.

Steps :

  1. Understand High-Level Flow:
    • First, review the product’s high-level functionality and workflow.
    • Then, identify key process stages and transitions.
  2. Identify Personas:
    • Next, determine the personas involved in each stage of the process.
  3. Write Test Cases from Acceptance Criteria:
    • Subsequently, translate acceptance criteria into detailed test cases.
    • Use actions and checks to automate the testing process.
  4. Organize Tests:
    • Finally, group test cases by process stages for clarity and efficiency.
    • Sequence tests to follow the logical process flow.

Use Case 2: Worksheet for preparing AutoTest Case Planning from Acceptance Criteria:

Here is a survey form for preparing AutoTest Case Planning from Acceptance Criteria:

AutoTest Case Planning Survey

Section 1: Understand High-Level Flow

  1. How do you review the product’s high-level functionality and workflow?
    • By using product documentation
    • By consulting with subject matter experts
    • Other (please specify): ________________
  2. How do you identify key process stages and transitions?
    • By creating flowcharts
    • By using process mapping tools
    • Other (please specify): ________________

Section 2: Identify Personas 3. How do you determine the personas involved in each stage of the process?

  • By analyzing user roles
  • By reviewing usage data
  • Other (please specify): ________________

Section 3: Write Test Cases from Acceptance Criteria 4. How do you translate acceptance criteria into detailed test cases?

  • Manually
  • Using automated tools
  • Other (please specify): ________________
  1. How do you use actions and checks to automate the testing process?
    • By using automation scripts
    • By using automation tools
    • Other (please specify): ________________

Section 4: Organize Tests 6. How do you group test cases by process stages for clarity and efficiency?

  • Based on the process flow
  • Based on functionality
  • Other (please specify): ________________
  1. How do you sequence tests to follow the logical process flow?
    • Manually
    • Using sequencing tools
    • Other (please specify): ________________

Additional Comments

Please provide any additional comments or suggestions related to AutoTest Case Planning:


Use Case 3: Organizing AutoTest for New Product and Automate Pro Users

Objective: Help a group unfamiliar with AutomatePro and testing organize and execute their tests.

Steps:

  1. Engage with the Project Team:
    • First, conduct initial meetings to understand the project scope and stories that must be tested.
  2. High-Level Process Flow:
    • Next, map out the high-level process flow to provide context.
    • Identify the personas and stages where changes occur.
  3. Develop Test Cases:
    • Subsequently, write test cases based on user stories and project requirements.
    • Ensure tests cover all necessary scenarios.
  4. Provide Training and Support:
    • Finally, offer training sessions on AutomatePro functionalities.
    • Provide ongoing support to the project team.

Example Process Flow:

  1. First, engage with the project team.
  2. Next, map high-level processes and identify personas.
  3. Then, develop comprehensive test cases.
  4. Finally, use AutoTest Successful Tests to provide Documentation & KB Articles support.

Use Case 3: Worksheet for Organizing AutoTest for New Product and Automate Pro Users

Here is a survey form for organizing AutoTest for new product and AutomatePro users:

AutoTest Case Planning Survey

Section 1: Engage with the Project Team

  1. How do you engage with the project team to understand the new product?
    • Regular meetings
    • Collaborative workshops
    • Other (please specify): ________________
  2. What methods do you use to gather information from the project team?
    • Surveys and questionnaires
    • Interviews and discussions
    • Other (please specify): ________________

Section 2: Map High-Level Processes and Identify Personas 3. How do you map the high-level processes for the new product?

  • Using flowcharts
  • Using process mapping tools
  • Other (please specify): ________________
  1. How do you identify the personas involved in each stage of the process?
    • By analyzing user roles
    • By reviewing usage data
    • Other (please specify): ________________

Section 3: Develop Comprehensive Test Cases 5. How do you develop comprehensive test cases for the new product?

  • Based on acceptance criteria
  • Based on user stories
  • Other (please specify): ________________
  1. What methods do you use to ensure the test cases are detailed and thorough?
    • Peer reviews
    • Automation scripts
    • Other (please specify): ________________

Section 4: Use AutoTest Successful Tests to Provide Documentation & KB Articles Support 7. How do you use successful AutoTest results to provide documentation support?

  • By creating detailed test reports
  • By updating existing documentation
  • Other (please specify): ________________
  1. How do you use successful AutoTest results to support the creation of Knowledge Base (KB) articles?
    • By documenting common issues and solutions
    • By providing step-by-step guides
    • Other (please specify): ________________

Additional Comments

Please provide any additional comments or suggestions related to organizing AutoTest for new products and AutomatePro users:


Use Case 4: Organizing Tests for ServiceNow or Product Upgrades

Objective: Organize and convert existing tests to regression tests for a ServiceNow or product upgrade.

Steps:

  1. Review High-Level Process:
    • First, map the high-level process flow of the current system.
    • Then, identify the personas involved.
  2. Review Existing Tests:
    • Next, evaluate current test cases for relevance.
    • Convert applicable tests into regression tests.
  3. Plan for Upgrade Testing:
    • Subsequently, review the upgrade details and identify changes.
    • Plan and prioritize tests for the new features and changes.
  4. Include Clone Down Review:
    • Finally, review the clone down process to ensure data integrity.
    • Identify what needs to be tested post-upgrade.

Example Process Flow:

  1. First, map high-level processes and identify personas.
  2. Next, review and convert existing tests to regression tests.
  3. Then, plan tests for the upgrade.
  4. Finally, conduct a clone down review and identify testing needs.

Use Case 4: Worksheet for Organizing Tests for ServiceNow or Product Upgrades

Here is a survey form for organizing tests for ServiceNow or product upgrades:

ServiceNow/Product Upgrade Test Planning Survey

Section 1: Map High-Level Processes and Identify Personas

  1. How do you map the high-level processes for the product upgrade?
    • Using flowcharts
    • Using process mapping tools
    • Other (please specify): ________________
  2. How do you identify the personas involved in each stage of the process?
    • By analyzing user roles
    • By reviewing usage data
    • Other (please specify): ________________

Section 2: Review and Convert Existing Tests to Regression Tests 3. How do you review existing tests for relevance to the upgrade?

  • By comparing with new requirements
  • By consulting with stakeholders
  • Other (please specify): ________________
  1. How do you convert existing tests to regression tests?
    • By updating test scripts
    • By validating against the new system
    • Other (please specify): ________________

Section 3: Plan Tests for the Upgrade 5. How do you plan tests specifically for the upgrade?

  • By identifying new features
  • By considering potential impact areas
  • Other (please specify): ________________
  1. What methods do you use to ensure comprehensive coverage of the upgrade?
    • Risk-based testing
    • End-to-end scenarios
    • Other (please specify): ________________

Section 4: Conduct Clone Down Review and Identify Testing Needs 7. How do you conduct a clone down review?

  • By reviewing clone logs
  • By validating environment setups
  • Other (please specify): ________________
  1. How do you identify testing needs post-clone down?
    • By assessing data integrity
    • By reviewing system functionality
    • Other (please specify): ________________

Additional Comments

Please provide any additional comments or suggestions related to organizing tests for ServiceNow or product upgrades: