Quick start tests for Agile Development 2.0

  • Release version: Zurich
  • Updated July 31, 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

    These quick start tests for Agile Development 2.0 help you validate that the Agile Development 2.0 features continue to work correctly after any configuration changes, such as upgrades or application development. They are designed to be customized with your instance-specific data and should only be run on non-production environments to avoid data corruption or outages. Running automated tests requires enabling the appropriate system property and activating the Agile Development 2.0 and Agile Development 2.0 - ATF Tests plugins.

    Show full answer Show less

    Key Details for ServiceNow Customers

    • Test Environment: Only run tests on development, test, or other non-production instances due to risk of data corruption.
    • Required Plugins: Activate com.snc.sdlc.agile.2.0 and com.snc.sdlc.agile.2.0.atf plugins before running tests.
    • System Property: By default, automated tests execution is disabled; enable it cautiously.

    Key Tests and Their Purposes

    • Story Management: Verify global rank assignment, active flag status changes on story completion or cancellation, and that updates roll up correctly to epics.
    • Sprint Validation: Check that sprints cannot be closed with active stories, sprints in the same group do not overlap, sprint points update accurately, only one sprint per group has current state, and sprint start/end dates are validated.
    • Capacity Management: Confirm that updating team/group capacity affects future sprints appropriately, considering sprint states (Draft, Planning, Current, Complete, Cancelled).
    • Epic Backlog: Test creation and editing of epic backlogs on the scrum program board’s Backlog tab, ensuring only epics belonging to the selected backlog are listed.
    • Demand Conversion (when PPM Standard plugin is active): Verify that Demands can be converted into Agile 2.0 stories or epics using related links on the Demand form.

    Practical Benefits

    By running these quick start tests, you can ensure that core Agile Development 2.0 functionalities remain intact and reliable after upgrades or customizations. This helps maintain the integrity of your Agile processes, prevents errors in sprint and story management, and supports seamless integration with Demand management when applicable.

    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