NetNada
NetNada put testing and observability practices in place.
NetNada’s engineers put a protocol from a Vectorise workshop into practice, and report less manual bug hunting and fewer rework loops in pull request review.
Australian owned. Forward deployed engineers based in Australia.
- The problem
- Hot fix bugs frequently disrupted the development workflow and left the team testing individual features by hand.
- The work
- Vectorise ran a workshop that set out a protocol for testing and observability. NetNada’s engineering team implemented it.
- The outcome
- NetNada reports less manual bug hunting and fewer rework loops in pull request review, and says its average feature to production time is coming down.
- Client
- NetNada
- Industry
- Sustainability, cloud enterprise SaaS
- Engagement
- One workshop
- NetNada’s programme
- Six month sprint
What changed, and why it mattered.
The practices NetNada’s engineering team put in place, following the protocol a Vectorise workshop set out, in the order a change meets them.
Tests generated.
AI tools act as assistants that generate unit tests. They may not change source code logic without explicit approval; any required code change is flagged for manual review.
Coverage gate.
A CI gate blocks commits and deployments when coverage falls below 100%. Coverage shows which code the tests run. It is not a guarantee of correctness, security or production reliability.
Pull request review.
Changes go to pull request review, where NetNada reports fewer rework loops.
Observed in production.
OpenTelemetry exports logs and traces, Grafana centralises metrics, and automated notifications go to one Slack channel.
- Under
2 min
test suite run time, reported by NetNadaExternal services mocked in tests.
The team uses tools such as MinIO to mock external dependencies like AWS S3 (Simple Storage Service) buckets, and HTTP wire mocks to stand in for external application programming interfaces (APIs), so the tests stay off real cloud infrastructure and live third party endpoints. With tests run in parallel, NetNada reports the suite runs in under two minutes.
Who did what.
Vectorise ran the workshop that set out the protocol. NetNada’s engineering team made the coverage commitment and implemented the CI gate, the code integrity rule, the mocks, the telemetry and the alert channel. They are NetNada’s practices.
Read Ways of WorkingHave a similar challenge?
- ProblemVectorise’s Accelerator SolutionRelease FasterShorten feedback loops, improve testing and make releases more predictable.Explore Release Faster
Hot fix bugs frequently disrupted the development workflow and left the team testing individual features by hand.
Talk to a Director.
Tell us what your team is trying to achieve and what is getting in the way. We will contact you during Sydney business hours to arrange a short conversation. If there is a fit, we will agree the next scoping step.
Prefer email? [email protected]