3 ms·

This is a brilliant idea. One of those "why hasn't that happened yet??" ones. Is there any way for me to obscure PII data easily? or anonymise any data recogni

This is a brilliant idea. One of those "why hasn't that happened yet??" ones. Is there any way for me to obscure PII data easily? or anonymise any data recognised as file contents or base64? That'd help. Have you considered hooking up alerts. For example to run `npx pythagora --script ./path/to/your/server.js --mode test` but with an option to pass a key/function to send alerts(perhaps just picking up test fail and dealing with it in the CI is better though) if a test fails that previously passed (wherever that command is run, so in the CI or if manually ran). We do use socket.io for a massive amount of our requests so I don't think it'd cover that (happy if wrong?) but I will look into if we can add a pull request for socket.io support, if you are interested in that scope creep... As that would be very powerful.

zvonimirs 4y ago
Thanks James! Yea, agree, I'm also curious why this doesn't exist yet. I thought there might be a tech roadblock but there really isn't any - especially since Node released Async Context. We did a POC for covering Redis and requests to 3rd party APIs and everything looks very doable, just need some time to implement it. Re PII, interesting question. We were thinking Pythagora will be used in a local/qa environment and not in production so that there won't be a need to anonymise data. However, it's good to have it in mind. Re alerts, yes, definitely. I think that's a great idea for using Pythagora in a CICD pipeline. Especially since, once the test suite grows, it will be super handy to get alert for failed tests after branches merge. Re sockets, yes, they are definitely on the roadmap - my previous startup used mostly sockets so hoping we cover them soon and we would LOVE if you want to contribute. If you have any questions or need anything, just let me know, I'd be happy to help you with the contribution.

zvonimirs 4y ago

Thanks James! Yea, agree, I'm also curious why this doesn't exist yet. I thought there might be a tech roadblock but there really isn't any - especially since Node released Async Context. We did a POC for covering Redis and requests to 3rd party APIs and everything looks very doable, just need some time to implement it. Re PII, interesting question. We were thinking Pythagora will be used in a local/qa environment and not in production so that there won't be a need to anonymise data. However, it's good to have it in mind. Re alerts, yes, definitely. I think that's a great idea for using Pythagora in a CICD pipeline. Especially since, once the test suite grows, it will be super handy to get alert for failed tests after branches merge. Re sockets, yes, they are definitely on the roadmap - my previous startup used mostly sockets so hoping we cover them soon and we would LOVE if you want to contribute. If you have any questions or need anything, just let me know, I'd be happy to help you with the contribution.