Thanks for the reply. What is the approximate percentage of connections that goes directly from service to service rather than from service to message bus/queue?
I'm curious about the order of magnitude.
Just depends on what can be lost and how you handle retries. Last big service I worked on (throughput of a few billion work items / incoming api requests per day) had a dozen network dependencies. We leveraged an in house queuing system, kafka as a bus, and all calls to other services as direct calls with heavy caching. Every call interacted multiple times with the queue (minimum 2) and sent out ~8 events. Each call leveraged direct network calls to the dependent services but due to caching responses, batching, pre-pulling data to cache, etc we would typically keep calls under a couple thousand requests per second.
So more direct to your question, I guess you could say 1 request became 2 queue calls, 8 bus events, and a dozen direct network calls at 90% cache hit ratio.
Hey @tkkapeed, if you mean stack that testhub supports then there are no limitations. Test-results scraping is done via CLI, Rest interface or CI/CD system plugins(we have only Github Actions for now). Test results and coverage format is jUnit and cobertura, but it's pretty easy to add new parser (just let me know which one is needed)
Hi, we built an open source too that aggregates unit and integration tests into a single dashboard. One can integrate it into their existing CI system and start gathering test results data. TestHub will then visualize test statistics across all projects, drilling down to individual test runs and all the tests within. We focus on simplicity of onboarding so it takes 10-15 minutes to integrate in any pipeline.
Check out how our UI looks: https://test-hub.io/test-hub
Hi, we are building an open source SaaS tool that aggregates unit test and coverage results into a single dashboard.
One can integrate it into their existing CI system and start gathering test results data. TestHub will then visualize test statistics across all projects, drilling down to individual test runs and all the tests within. We focus on simplicity of onboarding so it takes 10-15 minutes to integrate in any pipeline.
Check out how our UI looks: https://test-hub.io/test-hub
Do you write unit-test and analyze their results for your projects? Would you consider using such a tool? Any feedback is much appreciated. If you want to try Testhub in your project just let me know and I'll help with integration, with no obligations.
Can't find information what kind of test result reporting formats it can parse/import.
Links in the page footers don't work. Link to "download testhub CLI" on home page doesn't work.
Unclear what it does. How does "See what you've been working on daily and how much time you spent on each task or project. You can use automatic or online timer for tracking different tasks." relate to a test tracking tool?!
> One can integrate it into their existing CI system
Home page talks about Github Actions only. For many CI systems, this being third-party SaaS would be a hard sell.
Hey, appreciate the feedback! It's really helpful.
> Can't find information what kind of test result reporting formats it can parse/import.
All of them. It's fairly quick for us to add something if it's not already there. We are still in an early stage and quite flexible.
>Links in the page footers don't work. Link to "download testhub CLI" on home page doesn't work.> Unclear what it does. How does "See what you've been working on daily and how much time you spent on each task or project. You can use automatic or online timer for tracking different tasks." relate to a test tracking tool?!
What a shame, that's probably from a template. Removing it and fixing the links.
> For many CI systems, this being third-party SaaS would be a hard sell.
We provide a CLI that you can run in a pipeline and it will locate tests results and upload them. Would that work for you case ?
