Quick start tests for Agile Development 2.0

  • Release version: Yokohama
  • Updated January 30, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Quick Start Tests for Agile Development 2.0

    This guide provides a set of quick start automated tests designed to help ServiceNow customers validate that Agile Development 2.0 functionality remains intact after configuration changes such as upgrades or custom development. These tests ensure your Agile Development 2.0 environment functions correctly by verifying key features and workflows.

    Show full answer Show less

    Important: Automated test execution is disabled by default to prevent accidental runs in production environments. Run these tests only in development, test, or non-production instances to protect your data integrity and avoid service disruptions.

    To use these tests, you must activate the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0) along with the Agile Development 2.0 - ATF Tests plugin (com.snc.sdlc.agile.2.0.atf).

    Key Tests and Their Purpose

    • Global Rank on Story Creation: Confirms that stories receive a global rank upon creation, ensuring prioritization works correctly.
    • Sprint Closure Restrictions: Prevents closing sprints that still have active stories, maintaining proper sprint lifecycle management.
    • Sprint Overlap Prevention: Ensures sprints within the same group do not overlap, supporting clear sprint scheduling.
    • Sprint Points Accuracy: Validates that story changes correctly update sprint point totals, crucial for accurate progress tracking.
    • Sprint State Management: Checks that only one sprint per group can be in the current state, avoiding conflicting sprint statuses.
    • Sprint Date Validation: Verifies that sprint end dates occur after start dates to maintain logical timelines.
    • Epic Roll-ups: Confirms that updates to stories (adding, estimating, removing, cancelling) correctly roll up to the epic level for accurate tracking.
    • Total Committed Points Stability: Validates that changes to sprint scope after sprint state changes do not alter total committed points, preserving commitment integrity.
    • Active Flag Management for Stories: Ensures the active flag on Agile stories is correctly set to false when stories complete or are cancelled, and true otherwise.
    • Group Capacity Updates: Verifies that updating the team/group capacity properly propagates to future sprints while respecting sprint states, allowing flexible capacity management.
    • Epic Backlog Management: Tests creating and editing epic backlogs on scrum program boards, facilitating backlog organization.
    • Demand to Scrum Artifacts Conversion: For instances with the PPM Standard plugin active, verifies the ability to convert Demands into Agile 2.0 stories or epics, integrating demand management with agile planning.

    Practical Value

    Running these quick start tests after changes ensures that your Agile Development 2.0 configurations continue to work as expected, minimizing risk of disruptions. They help maintain data accuracy, enforce process rules, and verify integrations, providing confidence in your agile workflows.

    By customizing these tests with your instance-specific data, you can tailor validations to your environment. This proactive validation supports smooth upgrades, configuration changes, and application development.

    Validate that Agile Development 2.0 still works after you make any configuration change such as apply an upgrade or develop an application. Copy and customize these quick start tests to pass when using your instance-specific data.

    Danger:
    By default, the system property that is used to run automated tests is disabled to prevent you from accidentally running these tests on a production system. To avoid data corruption or an outage, run tests only on development, test, and other non-production instances. See Enable or disable executing Automated Test Framework tests.

    Agile Development 2.0 quick start tests require activating the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0) and the Agile Development 2.0 - ATF Tests plugin (com.snc.sdlc.agile.2.0.atf ).

    Table 1. Agile Development 2.0 quick start test suite
    Test Description Release version
    Verify that global rank is populated when a story is created Verify the global rank of a story after creation. Madrid
    Verify that closing a sprint with active stories is prevented Verify that a sprint with active stories cannot be closed. Madrid
    Verify that sprints cannot overlap in the same group Verify that sprints in the same group do not overlap. Madrid
    Verify that sprint points are updated Verify that changes to stories produce accurate sprint point totals. Madrid
    Verify that only one sprint in a group can have the current state Verify sprint statuses. Madrid
    Verify sprint end date is after the sprint start date Verify sprint start and end dates. Madrid
    Verify that any update on story rolls up to Epic Verify that adding, estimating, removing, deleting, updating, or cancelling a story updates the epic-level roll-ups correctly. Orlando
    Verify changes to the scope of a current sprint do not alter the value of the Total Committed Points Verify that the value of Total Committed Points does not change with change in the scope of a sprint after its state is changed to Current. Orlando
    Verify active flag is set false when Agile Story state is changed to Completed/Cancelled Verify that active flag of an Agile story is set to the following:
    • False, if the state is changed to Completed or Cancelled
    • True, for all other states
    		 Orlando
    Verify that updating the team/group capacity overrides the capacity on all the future sprints
    Verify that any update to the Group capacity field of the assignment group results in the following changes to the Group capacity field of the various sprints associated with this assignment group:
    • For the sprints that are in the Draft and Planning state:
      • The group capacity is updated to the new value.
      • The Group capacity field is editable.
    • For the sprints in the Current, Complete, or Cancelled state:
      • The group capacity remains the old value.
      • The Group capacity field is read-only.

    For the sprints in the Draft or Planning state, you can individually edit the group capacity of the sprint anytime later. This would not change the group capacity of the assignment group associated with this sprint.

    		 Paris
    Verify create and edit functionality of an epic backlog on the scrum program board
    • Verify that you can create an epic backlog for scrum programs from the Backlog tab of Agile Board.
    • Verify that you can update an existing epic backlog for scrum programs from the Backlog tab of Agile Board.
    • The epics listed in the backlog must belong to the selected epic backlog.
    		 Quebec
    Verify a Demand is converted to a scrum story If the PPM Standard plugin (com.snc.financial_planning_pmo) is active, verify that a Demand can be converted to an Agile 2.0 story using the Create Story related link on the Demand form.

    For more information on how to create an Agile 2.0 story from a demand, see Create an artifact from a demand.

    		 Quebec
    Verify a Demand is converted to a scrum epic If the PPM Standard plugin (com.snc.financial_planning_pmo) is active, verify that a Demand can be converted to an Agile 2.0 epic using the Create Epic related link on the Demand form.

    For more information on how to create an Agile 2.0 epic from a demand, see Create an artifact from a demand.

    		 Quebec