Egov API Automation :: Weekly Status :: 08/02-12/02

Tasks/Accomplishments:

  • Phase 1.1 Sprint-1 Efforts from Manual and automation Test cases : Progressed

  • Automation karata-master build got it reviewed from Tarun on code changes as per eGov requirements

  • Demo of Phase-0 and Phase-1 test suite automation code with stable test results complete by addressing client’s requirements.

  • Handover of automation code to implementation team is in-progress with Tech review MoM.

Tasks

Weekly Status

Percentage

Comments

Manual Test Cases:

Egf-Master

In-Progress

90%

Ready for review

Manual Test Cases:

Egf-Instrument

In-Progress

70

InstrumentAccountCode_Create API is not generating ID, Shwetha is looking into it and will complete once she get back

Manual Test Cases:

Dashboard Ingest

Done

100%

 

 

 

Automation:
apportion-service

In-progress

80%

Service not exposed at eGov Infra config. Aniketh to update Sathish

Automation:
enc-service

In-progress

80%

Service not exposed at eGov Infra config. Aniketh to update Sathish

Collection Services

Done

100%

 

eGovUser

In-Progress

95%

 

Addressing automation code review comments

Done

100%

 

Automation code readme documentation

Done

100%

 

url-shortening and egov-wf-process-search

In-Progress

95%

Review under progress

egf_master chartofaccount

In-Progress

70%

Review under progress

 

Discussions/Action Items:  

  • Blocker : “apportion services” code implementation has a blocker due to “apportion services” is not exposed at eGov infra config to outside. Aniketh to convey Sathish on further approach (Port forward or any other way)

  • Complexity: Approach Document is progressed to roll a use case from automation, to ensure kafka framework for DIGIT services. Devops compliance not allowing Topics to consume by outsiders. so automation team is working on building dependency packages of services to be automated.

  • Review items pending for QA review: Phase 1.1 Sprint-1 test creation Efforts from Manual and automation Progressed by keeping QA team reviews on pipe-line with waiting status.

  • PHASE-2 delivery planning and sprint coverage at High level is completed.