Skip to content

Arch Forum 2023-03-30

Participants: Andy, Johan, Liangxiong, Shoaib, Victor and Zakarya

Agenda

  • Growing Logs
  • Regression testing
  • Risk regression testing

Notes

Growing Logs: A short discussion about the growing amount of logs we do. Right now we do more than 50GB of logs per day and it's growing. 

Regression testing: There has been confusion around how/when regression tests should use the Internal Testing API. This was a rather long discussion. 

In the end we concluded:
- Internal Testing API is needed, and can be kept mostly as today. It would be a massive effort to change, and it is (importantly) used by App teams as well.
- Regression tests for an area should test / use the area's API to do its test. Its the API that is tested.
- If the regression test needs to do something not available/possible through the API, its fine to do it through the Internal Testing API like today.

It was also brought up that it's sometimes difficult to understand errors, i.e. when App teams call Internal Testing API. However, there is no simple solution since these errors might happen in asynchronous flows where the API is not directly involved in the error. Instead it might best be "fixed" by education about how to look in elastic/kibana.  

Risk regression testing: As a last point we started to talk about how risk regressions, including other areas "testing"  risk are often unstable, and take a lot of maintenance. This discussion was not concluded, but one outcome was that we need to rethink how/if risk rules configuration should be tested, e.g. the remittance limit for Mexico is x amount.