4 ms·
I must admit that the test coverage is still lower than we would want it to be. Currently, we are in the process of adding tests, and the test coverage will on
by vmatsiiako 3y ago
I must admit that the test coverage is still lower than we would want it to be.
Currently, we are in the process of adding tests, and the test coverage will only keep increasing over the next few weeks. You can learn more about this in our community Slack: https://infisical.com/slack https://infisical.com/slack
- iLoveOncall 3y agoYou said the same 5 months ago: https://news.ycombinator.com/item?id=34956592 https://news.ycombinator.com/item?id=34956592 Any reason to believe this to be true this time around?
- vmatsiiako 3y agoYes, indeed! I understand how it might sound. We have already started doing it and discussed it within our community – in other words, it's not just a plan. Expect it within the next 2 weeks maximum.
- RadiozRadioz 3y agoI would prefer that you didn't set yourself hard time-based deadlines for security features. If this product is going to be around long enough for enterprise to trust it, that you did this in two weeks won't make any difference. Unnecessarily rushing yourself to meet an arbitrary deadline helps nobody and hurts the product. Especially if, as noted by GP, you don't have a good track record. It's also worth noting that you're doing this in the wrong order. The "We can test it all later, ship! ship! ship!" strategy works fine for trivial apps, not security software.