DevOps Scoping

Outputs:
1. MPS/Existing process loaded
Solution Book Entities
Business Process
2. Customer reviews a single E2E flow within the process to define a CR
Fragment

3. Testing Architect & Process Element

Customer define Interface
MTFs within CRs and
cross CRs using Solution Documents
parameters
CR Document
Customized Process Element

Customized Interface

Testing Architect
MTF
Customized Process Element
Customized Interface
Parameter Value

Interface

Sharon Elgarat
DevOps Grooming
1. CRs are Submitted to Dev & Test
CR Document
Customized Process Element

Customized Interface

2. Dev define in Rally EPICs & Features

MTF#01
MTF#02

EPIC#01 EPIC#02 MTF#03

Feature#1.1 MTF#01 Feature#2.1 MTF#02

Feature#1.2 MTF#01 Feature#2.2 MTF#01

Feature#1.3 MTF#03

Feature#1.4 MTF#02

3. Test Link MTFs from BEAT to

Features in Rally
EPIC#03

Feature#3.1
PI#01 PI#02
MTF#01

Feature#3.2 MTF#03 Feature#1.1 Feature#1.2

Feature#3.3 MTF#03 Feature#3.1 Feature#1.4

Feature#2.2 Feature#3.1
4. Dev Prioritize PIs targeting MTFs Delivery
DevOps Grooming 3rd Parties

DevOps MTFs Management Multi Vendors Interface List

ORIGINATING VENDOR ORIGINATING APP

Aspect IVR

TERMINATING VENDOR TERMINATING APP

Amdocs CRM

DESCRIPTION

Identify Caller and Launch Interaction Home with Caller dealers in context

LONG CHAIN BUSINESS PROCESSES

Call Center Incoming Call MCI COP

ORIGINATING STATUS TERMINATING STATUS

Delay Mitigated On Track

1. MTFs are linked to interfaces within BEAT

2. Originating & Terminating interface vendors update in BEAT a coordinated delivery date
DevOps Test Design

DELIVERY STATUS VIEW

RALLY FEATURES

MTF#017

MTF#017 - MCI

MTF#017 - Reg

1. Design Console test calendars are created per BEAT MTF

2. Business Process structure is loaded for the MTF Customized Flow from Solution Book
3. Copying components and sub flows to generate short and long chain to cover all testing Levels

4. Integrating with Rally to link tests to features and present delivery status for each testing flow
DevOps Test Design

50% (19) 100% (10) 100% (4) 100% (6) 85% (12) 60% (5)

MTF#017 1 100% 1 100% 1 100%

2 100% 2 100% 3 60%

MTF#017 - MCI
2 100%
2 100% 3 60%

MTF#017 - Reg

3 60% 4 90%

4 90%

5 40%

6 100%

7 80%

8 0%

E2E Integration Stubbed Stubbed Integration Stubbed

1. The System breaks down the diagram to its flows to generate

the final tests for all Test Levels

2. Scenarios are added to each flow using Pairwise at diagram level which ensures parameterized
coverage increase cross test levels and reduce duplication

3. Closing the loop between delivery readiness and automation enables instant execution
of developed flows
DevOps Test Execution & Certification for Production

DevOps MTFs Management

1. Short chain flows are executed to indicate feasibility for long chains
then long changes are run to find farther integration defects

2. Execution results are reflected to the customer per MTF to enable decision making for production
Thank you
DevOps Testing Example: MTF Mapping to Features
1. VFIE Business brought to scoping uses cases including UC 5.1 for selling Broadband products

2. VFIE Grooming VFIE EPIC E100 (Broadband COP) VFIE EPIC E237 (General CCS)
Epic Name Feature ID Feature Name Epic Name Feature ID Feature Name Feature ID Feature Name
Produced EPICs F12
F258
COP - Wireline flow for Internet (F12)
CHQ - Cancel fulfillment flow for Internet and PSTN (Provide/Cease)
F1015
F104
Store VoLTE information on the Event
Processing Wireless Voice Events
F395
F462
RA extracts
Duplicate Check

including E100 &

F105 Processing Wireline Data Events
F261 CHQ - Amend fulfilment flow for PSTN F482 COP - ALU flat OC - MZ (OFCA-TC Only)
F106 Processing Wireless Data Events
COP 14: Service F59 Outage Monitoring - Fixed CCS_01_CustomerC F484 ALU OC Flow - OC Charge Accumulation - Rating
F107 BI exracts
Fulfilment and onsumes Service: F487 COP - ALU flat RC - MZ (OFCA-TC Only)
E237
F772 Outage Monitoring for IPTV and Internet F1208 Changes to UC charge codes and Service Filter mapping
Activation: Fulfil F785 CHQ - Amend fulfilment flow for Internet Customer Initiates a F488 Processing RC Charge Events
F200 Processing Wireline Voice Events
Broadband Order F787 Access Provider Interface for Provide Call F490 Additional Attributes in EOM Extracts to AR
F201 Processing SMS Event
F788 Access Provider Interface for Inflight Orders (Cancel/Amend) F202 UC - ER (Content event) F694 Processing MMS Events
F789 Access Provider Interface for Non Provide Create F203 CCS Rainy Day Scenarios F805 Process VFI RC Charge Accumulation by ALU …
F957 CM integration with Surepay - Provide Broadband without GLP - Tracker 505 F204 Late Calls F998 Processing VOIP Voice Events

3. In DevOps Scoping the testing architect 4. In DevOps Grouping tester link MTFs to features
would create an MTF for Broadband COP & CCS (E100 main flow only + F106 from E237)

MRL: Mobile Number COP & CCS : Fulfil & Use COP & CCS : Fulfil & Use COP & CCS : Fulfil

COP & CCS : Fulfil & Use

Repatriation WLR Order VoIP Order IPTV Order

Broadband Order
MRL: Mobile Number
Repatriation
COP & CCS : Fulfil & Use
Broadband Order
F1015 F204 F106 F1208 F785 F772 F12
Broadband COP & CCS Broadband COP & CCS
Broadband COP & CCS
COP & CCS : Fulfil & Use
Port In Mobile
F104
F105 F787 F788 F59
F201 F258
F107 Broadband COP & CCS
Broadband COP & CCS
F200

F957 F789
F261
Broadband COP & CCS
 DevOps Testing Definition: Short Chain, Long Chain and E2E
Before we continue with our example let’s see the test level which acceptance testing must contain

Short Chain

1 2 3 4

Short Chain: Any Test which contains one and only one External Interface
*External Interface: an interface between two applications developed by two different vendors

Long Chain

1 2

Long Chain: A test with multiple external interfaces which:

1. Starts from a request and continues till a response returns to the original requesting application
2. Starts from a Transaction which doesn’t return to source and ends at the Business Process end.

E2E

E2E: A Test which starts from the first action a tester needs to perform to prepare the environment or data to test
a business activity till the final action the tester must perform to validate the activity provided value to the customer
DevOps Testing Example: MTF Test Design

Create Mediation Create Activate

Create Customer Event Customer Device
Customer
Create Guiding Create Start Usage
Create BA & FA Validated BA & FA on Device
Negotiate
Broadband COP & CCS BA & FA
COP Mediation
Negotiate Event Negotiate
COP Rated COP Event
Broadband Main Credit
Evaluation Credit Credit Guiding
Broadband
MTF#017 OPT
- Reg Evaluation Evaluation Validated
COP & CCS Regression Provision Activate
Product Device Provision Event
Credit Product Rated
Evaluation
Start Usage Activate
on Device Provision Device
Product
Mediation
Event
Provision
Product
Guiding
Validated Activate
Device
Event
Rated

E2E Short Chain Long Chain

1. Test Designer builds calendars per MTF including Main Functional, OPT and Regression
2. The MTF branch of COP & CCS Business Processes is imported to show the E2E flow
3. Let’s first Mark the External Interfaces to better analyze the next step

4. To create short chain tests we copy sub flows till or from an external interface

5. the example doesn’t have responses returning to source so Long chains are defined by BP
DevOps Testing Example: Test Design to Dev Features

Create Create Mediation Create Activate RALLY FEATURES

Customer Customer Event Customer Device

Create Negotiate Create Guiding Create Start Usage

BA & FA COP BA & FA Validated BA & FA on Device

Broadband COP & CCS Credit Mediation

Negotiate Negotiate
Evaluation Event Rated Event
COP COP
Broadband Main
Provision Activate
Credit Credit Guiding
Broadband OPT Product Device
MTF#017 - Reg Evaluation Evaluation Validated
Start Usage
COP & CCS Regression
on Device Provision
Event Rated
Credit Product
Mediation Evaluation
Event Activate
Provision Device
Guiding Product
Validated

Event Rated Provision

Product

Activate
Device

1. Testers map each feature to the tests which depend on it

2. Delivery Status will allow to show which flows are available to start execution

3. The MTF is production ready if all boxes are green both in delivery and in testing status
 Delivery Amdocs Testing SIT waits till the first PI
which provides Testable
Feature
features on integrated
User Story environment with Business
Feature value to the customer
Dev EPIC CJ
Scope User Story
SIT
PI 01 Feature
Dev EPIC CJ
User Story
PI 02 Feature
Dev EPIC CJ
User Story
PI 03 Feature
Dev EPIC CJ
Current User Story
M ethod PI 04

EPIC Dev EP

PI 05
Feature
EPIC
User Story
Feature
SIT
Scope

Dev CJ User Story E2E

PI 01 EPIC
SIT
Scope

Dev CJ
Feature
PI 02
User Story E2E
EPIC
Dev CJ SIT
DevOp Scope
Working by MTF
the team receives s End S PI 03
Feature
testable features with tate User Story E2E
business value for testing
Dev CJ SIT

Scope
already from PI 01 and
can certify E2E based on
MTF Scope PI 04
Amdocs Testing Rampup
120% Flex Team Leads, Executers, Designers ORT/Sanity On Going Regression & SWP Sanity Stabilization

Core Top Designers, Automation Expert

TMO TSP, CTA (Testing Architect)

100%

80%

60%

40%

20%

0%
PI 01 PI 02 PI 03 PI 04 PI 05 PI 06 PI 07 PI 08 PI 09 PI 10