SaFi Bank Space : SaFi Transaction Automation Testing Status

transaction-processor-manager

[FOR DECOMMISIONING]

83

82.2

82.3

81.7

inbound-transaction-manager
SAF-1340 - Add Sonarqube for Inbound TPM Backlog

*

*

*

*

97

97

outbound-transaction-manager
SAF-1341 - Add Sonarqube for Outbound TPM Backlog

*

*

*

*

95

93

internal-transaction-manager

SAF-1630 - Add Sonarqube for Internal Transaction Manager Backlog

*

*

*

*

96

96

transaction-history-manager

92.1

91.8

91.8

91.8

scheduled-transactions-manager

78.7

78.7

78.9

78.9

statement-manager

88.0

88.0

88.1

88.1

engagement-manager

79.5

79.5

79.2

79.2

merchants-manager

90.2

90.2

90.2

90.2

fee-manager

74.4

89.5

89.5

89.5

transaction-categorization-manager
SAF-1342 - Add Sonarqube for Transaction Categorization Manager Backlog

*

*

*

*

product-manager

82.3

83.4

83.4

83.4

referral-manager

73.9

73.9

78.9

78.9

pdf-generator

44.6

48.0

48.0

48.0

pesonet-gateway

72.4

72.4

72.0

72.0

paynamics-gateway

89.1

89.1

88.3

88.3

digipay-gateway

79.8

79.8

79.8

79.8

ecpay-gateway

85.0

85.9

85.9

85.9

transaction-processor-manager

not appropriate right now, currently refactoring and breaking the service appart

transaction-history-manager

SAF-1237 - Component Tests - Transaction History Manager Backlog

scheduled-transactions-manager

SAF-1241 - Component Tests - Scheduled Transaction Manager Backlog

statement-manager

SAF-1242 - Component Tests - Statement Manager Backlog

engagement-manager

SAF-1244 - Component Tests - Engagement Manager Backlog

merchants-manager

SAF-1245 - Component Tests - Merchant Manager Backlog

fee-manager

SAF-1246 - Component Tests - Fee Manager Backlog

transaction-categorization-manager

product-manager

referral-manager

pdf-generator

pesonet-gateway

paynamics-gateway

digipay-gateway

ecpay-gateway

Unit

Yes

Yes

Yes

Yes

Current:

Coverage: 82.2

Duplicate: 11.9

Previous:

coverage is 83%, duplicated lines are 5.7%

Add missing coverage SAF-506 - Add Unit Tests for Transaction Processor Manager Cancelled

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

Current:

Coverage: 91.8

Duplicates: 12.9

Previous:

coverage is 92.1%, duplicated lines are 12.3%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

ADDED component tests for new features.

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

Current:

78.7

9.4

Previous:

coverage is 78.7%, duplicated lines are 9.4%

Minor work: SAF-510 - Add Unit Tests for Scheduled Transactions Manager Backlog

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 79.5%, duplicated lines are 3.6%

SAF-511 - Add Unit Tests for Engagement Manager Backlog

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 88%, duplicated lines are 0%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

Current:

89.5

0

coverage is 74.4%, duplicated lines are 0%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 90.2%, duplicated lines are 6.3%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

Current:

83.4

9.9

coverage is 82.3%, duplicated lines are 10.3%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 73.9%, duplicated lines are 0%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

Current:

48.0

0.0

coverage is 44.6%, duplicated lines are 0%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 79.8%, duplicated lines are 7.6%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 72.4%, duplicated lines are 0%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

coverage is 89.1%, duplicated lines are 5.2%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)

Unit

Yes

Yes

Yes

Yes

Current:

85.9

0

coverage is 85.0%, duplicated lines are 0%

N/A

Component

Yes

Yes

Yes

No

N/A

write cases the cover critical paths identified

Contract

Yes

No

No

No

N/A

1, get contract test framework ready;

2, identify critical paths;

3, create epic tickets in Jira backlog to keep track of test cases for critical paths

4, write test cases to cover the critical paths

We have the REST client library there, so we don’t think contract test is necessary; we also have the Kafka library there

Smoke

Yes

No

No

No

N/A

Performance

Yes

No

No

No

QPS/TPS?

Response time(Percentile)