I forgot to come back to the conversation here - I feel like this is a more permanent place to note my thoughts after reflecting.
I definitely see the value here - if we also add an in-memory target, we remove the need to have docker or command line stuff involved at all for e2e/release testing, and also hopefully remove data files, and manage interpretation of results for e2e tests easier.
I definitely see the value of this. What we have now is functional but messy, so I don't think it'll take priority over developing QA in-deployment (for example), but it's certainly one for the list of QOL/mainenance improvements, which we chip away at as we get ahead of the requirements.
TL;DR - nag me about it when opportunity comes up please :)
I forgot to come back to the conversation here - I feel like this is a more permanent place to note my thoughts after reflecting.
I definitely see the value here - if we also add an in-memory target, we remove the need to have docker or command line stuff involved at all for e2e/release testing, and also hopefully remove data files, and manage interpretation of results for e2e tests easier.
I definitely see the value of this. What we have now is functional but messy, so I don't think it'll take priority over developing QA in-deployment (for example), but it's certainly one for the list of QOL/mainenance improvements, which we chip away at as we get ahead of the requirements.
TL;DR - nag me about it when opportunity comes up please :)