Dokimore Product Team
What the product does, what it does not do yet, and why.
- Articles
- 5
- Topics
- 1
- Last updated
What this team covers
Articles signed by this team
- ProductHow-to guide
How to Test an LLM API Key Before You Build on It: The Dokimore LLM Tester, Step by Step
Paste a key, test the connection without spending a token, then chat, run an agent or compare up to four models side by side while every reply is checked, scored and traced. This guide walks the LLM tester end to end: the probe catalogue grouped by the OWASP Top 10 for LLM Applications, the multi-turn chains with their single-turn controls, and exactly where your key does and does not go.
- ProductOpinion
Self-Healing Tests Are Lying to You (Unless a Human Checks)
Test maintenance is where automation initiatives die, and silent auto-healing re-breaks trust the first time it fixes a selector to the wrong element. Playwright now ships a healer agent of its own, so the question is not whether a tool heals but how you find out. Dokimore’s approach: fallback locators captured at record time, a ranker that matched 48 of 60 evaluation cases with no false accepts, and a run that shows every rescue for a person to check.
- ProductExplainer
AI Testing Tools and Your Code: Where Does It Go? Ask.
Many AI testing tools send your code, selectors and test data to a third-party model API on every analysis, and the only way to know is to ask. Dokimore’s test intelligence runs on small locally hosted open-weight models on our own servers, scoped to your tenant; your data reaches a third-party model only by two paths you switch on yourself, the key you paste into the LLM tester and the paid Work with AI add-on. This article gives the three questions to ask any vendor, what the OWASP list says about the risk, and what we measured about our own models.
- ProductExplainer
"Test It Like Black Friday" Is Now a Valid Load Test Spec
A realistic load profile, with a ramp, a think time and a duration that match real traffic, can take an experienced engineer hours to write, so many teams run a flat ramp that resembles no real traffic, pass it, and meet their first realistic load in production. Intent-based load testing turns the sentence you would say in the planning meeting into a reviewable configuration, generated by a local model on the Dokimore host and edited before anything runs. What it produces, what it does not decide for you, and how a profile leaves the platform.
- ProductExplainer
A QA Dashboard Should Be a Command Center, Not Another Report
Test reporting answers "what happened when we last ran tests". The questions a QA lead fields at nine in the morning are operational, and answering them from five tools is how mornings disappear. A command center puts security posture, structured system logs, dependency circuit breakers and the audit log on one screen, with a day’s counts beside them. What is on Dokimore’s, how to read it, and which published metrics to put next to it.
What its articles carry
- 5 of 5 list their outside sources, each with the date it was read.
- 5 of 5 say how their numbers were measured, under “How we measured this”.
- 5 of 5 answer the questions readers ask, one paragraph each.
- An article that changes after publication shows the date it was updated.