CELR>DEX Load Testing September 12-14: Retrospective

Owned by Gretl Glick, created
Last updated: Sept 22, 2023 by Geoffery Miller
1 min read

 Overview

Reflect on past work and identify opportunities for improvement by following the instructions for the Retrospective Play.

Date

Sep 20, 2023

Team

AIMS Team

Dex Team

Participants

@Geoffery Miller @Charles Steele @Wouter Badenhorst @Erroll Rosser @Alissa McShane DEX Team

 Retrospective

Add your What Went Well?, What Didn’t Go Well?, and What should we change next time/Future Improvements? items to the table below. Please provide your initials by the item captured below as you add them to the table. We'll use these to talk about how we can improve our process going forward.

What Went Well

What Didn’t Go Well?

What should we change next time/What are potential future improvements?

What Went Well

What Didn’t Go Well?

What should we change next time/What are potential future improvements?

  • GM: Data transmission via tus-client worked without errors

  • GM: No infrastructure outages or problems

  • GM: Updating credentials/DEX endpoints was easy

  • GM: Data flow integration with AIMS mirth worked properly

  • GG: Updated documentation needed from DEX for STG endpoint.

  • GM: It’s not immediately obvious in the ATD integration what DEX environment it is pointing to

  • GG: Additional visibility needed for file transmission to identify specific transactions, compare file counts, identify potential missing files or files which were sent in duplicate.

  • GM: Need documentation for updating credentials for prod support

  • GM: Need documentation for how AIMS-to-DEX (ATD) integration supports multiple projects and DEX environments

  • GM: Need a way to properly test the resumable feature in tus when a tus client closes and application state is lost - already assigned in Jira project to Aly

 

 

 

 

 

 

 Action items