Quick start tests for Agile Development 2.0

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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

    The Quick start tests for Agile Development 2.0 help ServiceNow customers validate that their Agile Development 2.0 configurations remain functional after changes such as upgrades or custom application development. These tests ensure critical Agile features operate correctly, preventing issues in non-production environments.

    Show full answer Show less

    To run these tests, the Agile Development 2.0 plugin (com.snc.sdlc.agile.2.0) and Agile Development 2.0 - ATF Tests plugin (com.snc.sdlc.agile.2.0.atf) must be activated. Automated tests should only be executed on development, testing, or other non-production instances to avoid data corruption or outages, as the system property enabling automated tests is disabled by default for safety.

    Key Features

    • Validation of Story and Sprint Behaviors: Tests check that global rank is assigned to stories, sprint closing is blocked when active stories exist, sprints do not overlap within the same group, and sprint points update correctly.
    • Sprint Status and Date Integrity: Ensures only one sprint per group has the current state, and sprint end dates follow start dates.
    • Epic Roll-up Accuracy: Confirms updates to stories correctly roll up to epic-level totals, including creation, estimation, removal, and cancellation.
    • Sprint Scope and Committed Points: Verifies that once a sprint is current, changes to its scope do not alter total committed points.
    • Story Active Flag Behavior: Validates that Agile story active status is false when stories are completed or canceled, and true otherwise.
    • Group Capacity Management: Tests that updates to group capacity propagate to future sprints in draft or planning states but not to current or completed sprints, maintaining data integrity.
    • Epic Backlog Functionality: Checks creation and editing of epic backlogs within scrum program boards, ensuring epics listed belong to the selected backlog.
    • Demand to Agile Artifact Conversion: When the PPM Standard plugin is active, verifies that Demands can be converted into Agile 2.0 stories or epics via related links on the Demand form.

    What Customers Can Expect

    By leveraging these quick start tests, ServiceNow customers can confidently apply configuration changes or upgrades to Agile Development 2.0 without disrupting key Agile workflows. The tests provide comprehensive coverage of core Agile functions such as story ranking, sprint management, epic roll-ups, and demand conversions. Running these tests in non-production environments helps maintain system stability and data accuracy, enabling smoother Agile delivery processes.

    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