Egov API Automation :: Weekly Status :: 01/03-05/03

Tasks/Accomplishments:

  • Manual test cases for municipal services- phase 2 are progressed

  • Automation services of Phase 2 Sprint-1 are being progressed

Tasks

Weekly Status

Percentage

Comments

Manual Test Cases: Property Services

Done

100%

 

Manual Test Cases: WS-services

In-progress

90%

Ready for review

Manual Test Cases: WS-Calculator

In-progress

30%

 

Manual Test Cases: TL-services

In-progress

20%

 

Manual Test Cases: PT Mutation related end points

In-progress

90%

Ready for review

Manual Test Cases: E2E for property Module

Done

 

 

Manual Test Cases:
Dashboard-Ingest (Kakfa related end points)

Blocked

40%

Postman is throwing an error for kafka related end points. Need a dev’s help too look into this.

Automation:
enc-service

In-progress

80%

PR Approvals done, merge due and automation to pick test for completion

Automation:

egf-instrument/surrenderreasons

Done

100%

 

Automation:
egf-instrument/instruments

Done

100%

 

Automation:
egf-instrument/instrumentAccountCode

Done

100%

 

Automation(kafka):

egov-persister

In-Progress

80%

Progressed and items status are as per Discussions item-2 as detailed below

Automation: egf-instrumentTypes

Done

100%

 

Automation: PT - Mutation related endpoints

In-Progress

30%

 

Automation:

property-services

In-Progress

40%

 

 

Automation:

egf_master : AccountDetailTypes

In-Progress

70%

 

Automation: zool / telemetry

In-Progress

60%

spillover service efforts

 

Discussions/Action Items:

  1. Kafka Rest 6.2 APIs are not released by confluence team, So consumer instance responses would be mocked and progressed. Once 6.2 API are released, automation team to test actual responses of other consumer instances for records.

  2. Kafka implementation using REST proxy has found dependency on Rest 6.2 APIs for capturing cluster consumer instances and topics, to address Tarun’s review feedback on kafka automation code implementation. So automation team progressing mock codes/responses as part of sprint efforts.

  3. Automation suite test by QA team in under progress, automation and QA teams working to have summed up changes as required for Implementation team for final handover. add on tech review changes by Tarun are also being addressed.

  4. As discussed, shared a E2E testing approach document with Tarun - waiting for the feedback.