DOC

R334_TU_TC_List_draft_1doc - Test Case Objective

By Wendy Dixon,2014-05-19 13:06
11 views 0
R334_TU_TC_List_draft_1doc - Test Case Objective

    Turn Up Test Case List for Software Release R3.3.4

    NANC 416

    New Test Cases:

    N/A

Updates to existing Test Cases:

    NANC 416 BDD File for Notifications Adding New Attributes

    Test Case Objective Requirements

    NANC 348-1 SOA - NPAC personnel create a Bulk Data RR3-540, Table E-8,

    Download file for SOA notification data specifying a service Notification Download File provider ID and time range. Verification steps are performed Example

    to ensure the BDD file was processed successfully by the service provider system. Success

    NANC 440

    New Test Cases:

    N/A

Updates to existing Test Cases:

    N/A

NANC 440 FCC Order, Medium Timers

    This change order introduces the Service Provider and System tunables required to support

    Medium Timer ports. These tunables will be tested as a result of Medium Timer Port scenarios

    tested with NANC 441 test cases.

    NANC 441

    New Test Cases:

    NANC 441 FCC Order, SOA Indicator

    These new test cases should be executed where both SPs to the port request support

    Medium Timer Indicators and L-12.0b notification priority set to production value.

    Test Case Objective Requirements

    NANC 440/441 1: SOA New Service Provider (System RR3-531, RR5-182, RR5-183, Under Test (SUT)) issues a single TN, Inter-SP Create, RR5-184

    setting the Medium Timer Indicator (MTI) to True. Wait for the

    T1 and T2 Timers to expire. Old Service Provider issues a create where the Medium Timer Indicator is set to False. Both Service Provider Profiles indicate they support Medium Timers. Initial Concurrence Timer is re-set. T2 notification is sent to

    NSP based on the L-12.0b Notification Priority Setting

    Success

     1

    NANC 440/441 2: SOA Old Service Provider (SUT) issues a RR3-531, RR5-182, RR5-183, single TN, Inter-SP Create, setting the MTI to True. New RR5-184

    Service Provider issues a create and sets MTI to False. Both

    Service Provider profiles indicate they support Medium Timers. Success

Note: In this scenario Timers are not reset and the AVC sent

    after the NSP create will not include TT or the MTI because there is no change to TT as a result of the NSP create even

    though the NSP/MTI indicator is different than the OSP/MTI indicator.

    NANC 440/441 3: SOA New Service Provider modifies the RR3-531, R5-27.1, RR5-182, MTI from False to True for a single TN, Inter-SP, Pending RR5-183, RR5-188, RR5-189

    subscription version after the T1 Timer has expired (before the Old Service Provider has issued their create). Success

    Let T2 timer expire; NSP will receive T2 expiry notification based on their support of the L-12.0b notification priority.

    NANC 440/441 4: SOA Old Service Provider modifies the RR3-531, R5-27.1, RR5-182, MTI for a range of TNs from True to False, Inter-SP, Pending RR5-188, RR5-189

    (or Conflict) subscription version before the New Service Provider has issued their create Success

    NANC 440/441 5: SOA New Service Provider modifies the RR5-183, R5-27.2, RR5-188, MTI from False to True for an Inter-SP, Porting to Original RR5-189

    subscription version Success

    NANC 440/441 6: SOA New Service Provider attempts to RR5-186

    modify the MTI for a single TN, Inter-SP, Pending (or Conflict)

    subscription version after the Old Service Provider has issued their create Error

Note: Some SP systems may not be able to create this

    scenario.

    NANC 440/441 7: SOA Old Service Provider modifies the RR5-182, RR5-187, R5-27.3,

    MTI for a single TN, Inter-SP, Pending (or Conflict) RR5-188

    subscription version after both Service Providers issued their initial create and prior to the activate Success

    NANC 440/441 8: New Service Provider Personnel remove Can re-use NANC 201-25.

    a Subscription Version from Conflict when the Timer Type and There are other conflict Business Type are set to „MEDIUM‟ (after the Conflict scenarios in regression too, Resolution New Service Provider Restriction Tunable has but none exactly like this one.

    expired) Success

Regression Testing:

    All Service Provider‟s must execute the Regression Test Suite (102 test cases depending on the actual functionality the SUT supports) where all Service Provider configurables are set to

    their production value.

During the Regression phase of Turn Up Test, Neustar/NPAC Test Engineers (Test Engineers)

    will establish two or more “other” service provider profiles (at least one that does support MTI and one that does not support MTI) to be used in the regression porting scenarios.

     2

    Service Provider and Test Engineers should work together to alternate the different other service provider profile (party to the test scenario) use and appropriately verify test results.

    When executing Modify (pending-like) test scenarios, and the Service Provider under test supports MTI, and it‟s appropriate based on the actual scenario, the MTI attribute should be modified as part of the test steps.

    For Subscription Version Query test scenarios the SUT along with Test Engineers should establish a body of Subscription Versions that use Medium Timers and some that do not use Medium Timers. The SUT has their MTI set to their production value and queries this combined body of MTI=True and MTI=False Subscription Versions and handles the NPAC SMS response appropriately.

    Resynchronization and BDD test cases should be executed such that (pre-requisite) requests issued to generate the notifications in the expected results specify attributes (MTI, Optional Data, etc.) supported by the SUT.

    NOTE: The Regression Test Suite is not listed in this document; these test cases can be found in the latest Individual SP Certification and Regression test plan available on the NPAC website.

    Additional/Optional Regression Testing:

    For Service Provider‟s that support MTI the following subset of Regression Test Cases

    can optionally be executed where the other service provider (profile established by Test

    Engineers) also supports Medium Timers such that the Timer Type and Business Hours

    set by the NPAC SMS will be Medium and notifications and porting rules will reflect

    Medium Timers.

    For Service Provider‟s that do not support MTI, the following subset of Regression Test

    Cases can optionally be executed where the other service provider (profile established

    by Test Engineers) does support Medium Timers. In this situation the NPAC SMS will

    establish Timer Type and Business Hours for the Subscription Versions and notifications

    and porting rules will occur as if neither Service Provider supports MTI.

    Test Case Objective

    Regression Subscription Version Create Test Scenarios:

    8.1.2.1.1.18 Create intra-service provider „pending‟ port of a single TN via the

    SOA Mechanized Interface. Success

    8.1.2.1.1.32 Create inter-service provider „pending‟ port (concurrence) of a single

    TN via the SOA Mechanized Interface. Success

    2.1 SOA - Old SP Personnel create a range of Inter-Service Provider subscription

    versions. Their Customer TN Range Notification Indicator is set to their production

    value. New SP does not submit their create request. Initial and Final Concurrence

    Windows expire. Success

    2.2 SOA New Service Provider Personnel create a range of 3 Inter-Service

    Provider subscription versions. Their Customer TN Range Notification Indicator is

    set to their production value. Old Service Provider Personnel does not submit their

    create request. Initial Concurrence Window Expires. Final Concurrence Window

    Expires. Success

    Modify Subscription Version Test Scenarios

     3

    8.1.2.2.1.1 Modify required fields for a single TN „pending‟ port with valid data.

    Success

    NANC 388-1 SOA Using their SOA system, Service Provider personnel send an

    “un-do” cancel request to the NPAC SMS for a Subscription Version in a Cancel-

    Pending status for which they are either the New SP or Old SP that cancelled the

    SV Success

    Query Subscription Version Test Scenarios

    8.1.2.7.1.1 Subscription Version Query SOA. Success

    Conflict/Conflict Removal Subscription Version Test Scenarios

    NANC 375-2 SOA Old Service Provider personnel remove a Subscription Version

    from Conflict status whose cause code is currently set to 50 or 51 Success

    218-2 SOA Old Service Provider personnel successfully put a pending

    Subscription Version into conflict using an Old Service Provider create after the

    Conflict Restriction Window Tunable Time has been reached but before the Final

    Concurrence Timer (T2) has expired. Success

    Resynchronization Test Scenarios

    187-5 SOA Service Provider Personnel submit a resynchronization request for

    Network Data and Notification Data by time range, over the SOA to NPAC SMS

    Interface, with the Service Provider‟s SOA Linked Replies Indicator set to their

    production setting. The recovery response includes a number of Network Data

    objects and Notifications greater than the respective Linked Replies Blocking Factor

    and less than the respective Maximum Linked Recovered Notifications. Success

Updates to existing Test Cases:

    Existing Turn Up Test Cases will be updated to reflect the MTI as the test case detail warrants. For example, Chapter 8 test cases do not always list the detail of notifications, thus these test cases will likely not warrant updates (to be consistent with the existing test case detail). However, Chapter 9 and later test cases use the latest test case template which contains more attribute detail in the messages exchanged between the NPAC SMS and Local Service Provider systems thus relevant test cases will be updated to reflect MTI details in a consistent manner.

    Subscription Version Create test scenarios will be updated such that the appropriate ObjectCreation and AttributeValueChange notifications reflect the MTI when supported.

    When T2 notifications are issued as part of the test case detail, this step will also be updated to reflect that the T2 expiry notification is issued to the New Service Provider when the L-12-0.b notification priority is set appropriately.

    Subscription Version Modify (pending-like) test scenarios will be updated such that the appropriate AttributeValueChange details reflect MTI when supported.

    Subscription Version Query test cases do not actually list the detail in the results due to the many combinations, but SUT and Test Engineers can verify query results based on the Service Provider configurables, etc.

    Resynchronization and BDD test case detail is updated to include MTI attributes in pre-requisite requests to be generated for inclusion in recovery and/or BDD files. Furthermore, Test Case results are updated to include MTI data when supported.

     4

Report this document

For any questions or suggestions please email
cust-service@docsford.com