Reference Documents

Squad-specific Automation Testing Status Template

Standard of SaFi Automation Test(WIP)

I. Jira Tickets

Placeholder for the parent ticket of all the Cards Test-Feature tickets

Tickets

Status

Remarks

1

SM-7982 - Getting issue details... STATUS

In Progress

Parent ticket for CARDS unit tests

1.1

SM-7983 - Getting issue details... STATUS

1.2

SM-7984 - Getting issue details... STATUS

1.3

SM-7985 - Getting issue details... STATUS

2

SM-7986 - Getting issue details... STATUS

Parent ticket for CARDS component tests

2.1

SM-7987 - Getting issue details... STATUS

2.2

SM-7988 - Getting issue details... STATUS

2.3

SM-7989 - Getting issue details... STATUS

3

SM-7990 - Getting issue details... STATUS

Parent ticket for CARDS contract tests

3.1

SM-7991 - Getting issue details... STATUS

3.2

SM-7992 - Getting issue details... STATUS

3.3

SM-7993 - Getting issue details... STATUS

4

SM-7994 - Getting issue details... STATUS

Parent ticket for CARDS performance tests

II. Microservices

II.A. Card-Transaction-Processor-Manager

II.A.1. UNIT/Component Testing

Required: Yes

Framework Ready: Yes

Coverage: 56.6 %

Duplicated Lines: 25.1 %

Reference: SonarQube - card-transaction-processor-manager

II.A.1.1. UNIT Testing

Critical paths

Is Tested

Action Points

Remarks

1

Controller calls

 

1.1

Request payload validation

N

date-string, etc

1.2

Negative scenario response validation

N

2

Anti-Fraud (Slacker-Manager) client call

2.1

Request payload validation

N

2.2

Negative scenario response-handling validation

N

no implementation in place yet

3

Corebanking (TM) system responses

3.1

No-response handling

N

3.2

Error-response handling validation

N

no implementation in place yet

3.3

Missing transaction-type handling

N

no implementation in place yet

3.4

Duplicate request-ID response handling

N

request-ID is set using the requests idempotency-key

4

Temporal workflow

4.1

Transaction entity updating

N

I.A.1.2. COMPONENT Testing

Critical paths

Is Tested

Action Points

Remarks

1

Authorise outbound-amount transaction

Partly

Setup additional tests for anti-fraud validation flow

 

2

Settle authorised-amount transaction

Partly

Setup additional tests for anti-fraud validation flow

3

Transfer transaction

Partly

Setup additional tests for anti-fraud validation flow

4

Release blocked-amount transaction

Partly

Setup additional tests for anti-fraud validation flow

5

Adjust and settle transaction

Partly

Setup additional tests for anti-fraud validation flow

6

All transactions common temporal workflow

6.1

Blocked workflow awaiting corebanking-system’s response

Y

II.A.2. CONTRACT Testing

TBD

II.A.3. PERFORMANCE/STRESS Testing

II.A.3.1. PERFORMANCE Testing

TBD

II.A.3.2. STRESS Testing

TBD

II.B. Card-Manager

II.B.1. UNIT/Component Testing

Required: Yes

Framework Ready: Yes

Coverage: 75.3 %

Duplicated Lines: 9.3 %

Reference: SonarQube - card-manager

II.C. Euronet-Gateway

Euronet-Gateway is a pass-through service for incoming/outgoing request from and to a third-party system (Euronet)

II.C.1 UNIT/Component Testing

Required: Yes ()

Framework Ready: Yes

Coverage: TBD

Duplicated Lines: TBD

Reference: TBD

Note: SonarQube monitoring is not yet in place

II.D. Card-Aggregator

II.E. Delivery-Aggregator

II.F. Ninjavan-Gateway

II.G. GogoExpress-Gateway

II.H. Bucket-Function

II.H. Card-Transaction-Processor-Manager

Required: Yes

Framework Ready: Yes

Coverage: 50.85 %

Duplicated Lines: 21.66 %

Reference: https://sonarqube.safibank.online/dashboard?id=card-transaction-processor-manager