Sandhata

Sandhata Sandhata Technologies Sandhata Technologies is an experienced, professional middleware integrator, encompassing SOA, ESB, BPM and analytics.

It has developed its own integration methodology that can offer simple and flexible solutions to complex issues such as regulatory compliance. Sandhata has extensive experience in capital markets, telecommunications and retail and its on-staff specialists have a minimum of five years' middleware project experience. This underlines the company's aim to provide quality and reliability in every customer interaction. With a head office in London, and EMEA onshore and APAC offshore delivery centres, its global presence can provide the best mix of onshore and offshore resourcing.

Why do your tests keep breaking?We think you already know the answer. We'll say it out loud anyway.Someone from your tea...
11/09/2026

Why do your tests keep breaking?

We think you already know the answer. We'll say it out loud anyway.

Someone from your team innocently renames a button on Friday afternoon. And the next thing you know, forty tests go red overnight! Monday morning, a perfectly good engineer sits down to work out which of the forty actually matter, and there goes her day.

Nobody plans for this. It just keeps happening, every few weeks, until one day somebody drops the suite from the pipeline "just for this release". And the just-for-this-release quietly becomes forever.

Here is the thing. Most suites are written to describe what the screen looks like. Change the screen and they seem to take it personally. Ours are written to describe what the app does, which is a much steadier thing to have an opinion about.

In practice that means locators built on roles and labels instead of brittle selectors, self-healing when something does move, and auto-waiting instead of the hopeful sleep(3000) we have all written at six o'clock on a Friday.

Teams usually get a first test running in under four hours, cut around 60 percent of the setup effort, and settle above 95 percent pass rate with flaky under 2 percent.

Your tests will always need a bit of looking after. They should not need a babysitter.

Anyway, here's a question. How much of your last sprint went on fixing tests rather than writing them? Do let us know in the comments or DM.

We promise, this is a no judgement zone. It is usually more than people expect, and that is rather the point.

Reclaim your Mondays here: https://zurl.co/HF0GO

Less triage. More testing.That is our whole pitch, and it is a smaller promise than it sounds.Most teams we meet are not...
04/09/2026

Less triage. More testing.

That is our whole pitch, and it is a smaller promise than it sounds.

Most teams we meet are not short of tests. They are short of trust in them. If a developer renames a button, forty tests fail, and your entire Monday goes to working out which failures are real. By Wednesday, somebody quietly excludes the suite from the pipeline for this release.

The suite is not catching bugs at that point. It is catching your engineers.

Our Playwright framework is built so that stops happening. Self-healing locators absorb UI change instead of breaking on it. Tests get generated from requirements rather than typed by hand. Parallel ex*****on means the suite finishes before anyone loses interest in the result.

What that looks like in practice: 60 percent less setup effort per project, a first running test in under four hours, pass rate above 95 percent, flaky rate under 2 percent.

None of which is the point.

The point of our entire pitch is that your engineers go back to testing the product instead of the tooling.

You can get started here: https://zurl.co/Gj0cN

You're probably doing better than you think with your SRE. No, that's not flattery. It's just what we usually tend to f...
01/09/2026

You're probably doing better than you think with your SRE. No, that's not flattery. It's just what we usually tend to find.

Most engineering teams we meet are carrying a system that grew fast, under real pressure, with constraints nobody outside the team ever sees. And they're holding it together with more skill than they get credit for.

The hard part usually isn't the work. It's that nobody has ever given them a straight answer about where they actually stand.

So you end up guessing. You know the pipeline has soft spots. You know the on-call rota isn't quite fair to whoever's on it this week. But is that normal for a company your size, or is it something to be worried about? Nobody can tell you. So the questions and the uncertainity just sit there.

We built something small to help with that.

The DevOps and SRE Maturity Compass is a free self-assessment.

You answer questions across key areas such as CI/CD, observability, incident management, that sort of thing. It takes about fifteen minutes or less, and you can do it on your own without telling anyone.

At the end you get a score, a view of where your risk is concentrated, and how you compare with others in your industry.

At Sandhata, we believe in community value addition . So if you take this free test, you don't have to sign up for a demo or a newsletter afterwards. No webinar upselling. Nobody from sales will ring you.

Take the assessment, get your result, and if we never speak again that's completely fine.

Start here: https://zurl.co/QTuqy

Your automation suite was meant to reduce the cost of testing. Somewhere along the way, it became another system your en...
19/08/2026

Your automation suite was meant to reduce the cost of testing. Somewhere along the way, it became another system your engineers have to maintain.

A developer renames a button and forty tests fail. The team then spends hours working out which failures point to an actual problem and which ones are simply broken scripts. By the middle of the sprint, confidence in the suite drops, and someone eventually suggests excluding it from the pipeline "just for this release."

The real cost here is not a failed test. It is engineering time.

Technical debt already consumes a significant share of IT budgets, and test automation adds its own hidden maintenance bill when scripts are brittle, frameworks age badly, and every interface change creates more repair work.

This is where AI can make a practical difference to QA teams.

Self-healing locators can detect interface changes and update affected tests without someone manually repairing every selector. Tests can be generated from requirements and user stories instead of being written line by line. Framework health checks can also spot recurring failure patterns and weak areas before they spread across the test estate.

For teams doing this well, the impact is measurable: test pass rates above 95%, flaky tests below 2%, setup effort reduced by around 60%, and ex*****on running up to three times faster.

In 2026, skilled engineers should be spending their time finding product risks, not fixing broken locators every time a button moves.

How much of your QA capacity went into maintaining automation last quarter?

Book a Free QA Health Check: https://zurl.co/wkm3X

Automating a bad process doesn't fix it. Most people start at the automate bit and wonder why it breaks at scale. This i...
14/08/2026

Automating a bad process doesn't fix it. Most people start at the automate bit and wonder why it breaks at scale. This is a great way to just get the same mess, faster.

Which is why its very important that you do the boring part first: ask introspective questions on the intention of automating.

Ask: What's this actually for? Which steps can you delete? Can what's left be simpler? AND THEN, you automate.

DM us if you want a personalized demo to see how this would look in your environment!

07/08/2026

So here's the thing nobody tells you about reliability: people usually have a measurement problem, but they go around in circles thinking they have an uptime problem.

We built SRE Compass because we kept walking into the same three questions and nobody had answers:

1. How fast are you burning your error budget? You need to watch your error budget like a hawk because your budget is the most accurate reflection of your risk apettite (or how much risk you can afford). Spend it deliberately or it'll get spent for you.

2. How long between something breaking and someone knowing? Everyone loves to quotes MTTR. But very few people separate out time-to-detect (which is usually the ugly half). Fixing a thing takes minutes. Noticing and observing take hours. Guess which one your customers experience.

3. What percentage of your changes cause a failure? Deploy frequency is the metric everyone puts on a slide. But we need to monito change failure rate as the one that tells us whether the deploy frequency is acting as an achievement or a liability!

Sandhata's SRE Compass runs across your services, scores them on all these questions AND more, and hands your team an ordered list of what's actually worth fixing. This is not just another gated dashboard. Its a free maturity assessment that could end up being your biggest pivot point.

The unglamorous truth is that reliability is mostly.....good and sharp bookkeeping. You have to know what you've got, know what it costs when it breaks,and know who owns it.

Anyway....if any of this sounds relatable, we should talk:https://zurl.co/sAlji

If your team uses 12 tools and zero of them talk to each other....it probably means that your ops team has to play refre...
03/06/2026

If your team uses 12 tools and zero of them talk to each other....it probably means that your ops team has to play refree and manually copy data between them....Every. Single. Day.

Sandhata's integration layer connects your entire stack: CRMs, ERPs, finance tools, support platforms, so data flows without a human in the middle.

Our integration mantra is simple: One source of truth with zero manual handoffs.

If your team is drowning in copy-paste work, let's fix that this week: https://lnkd.in/gDN6guzZ

Have you heard of "The Microservice Hangover"??The pitch that made complete sense in 2019 because of smaller services, ...
30/04/2026

Have you heard of "The Microservice Hangover"??

The pitch that made complete sense in 2019 because of smaller services, faster teams, nobody stepping on each other...... but nobody mentioned the part where five years later you've got a single failed transaction that takes three engineers and half an afternoon to trace, and an on-call rotation that's quietly become the thing your best people bring up when they're explaining why they're leaving.

Distributed systems come with a maintenance bill nobody budgeted for, and this is the honest conversation about what to do about it.

Read more here: https://zurl.co/LeH9u

Every chair taken, every stylist locked in, the kind of Thursday evening that makes the whole week worth it .....but the...
29/04/2026

Every chair taken, every stylist locked in, the kind of Thursday evening that makes the whole week worth it .....but then a phone rings, nobody gets to it, and that caller doesn't leave a voicemail or try again later, they just open a competitor's app, confirm in under a minute, and become someone else's regular without a second thought.

Your busiest nights are also your most expensive ones for missed opportunity, and the gap isn't your service. The gap is that narrow window between a ringing phone and a confirmed booking, which also happens to be the most fixable problem on your list: https://zurl.co/G7IRc

Are you having a silent slowdown?If last quarter looked genuinely good on paper, but you're being straight with yourself...
28/04/2026

Are you having a silent slowdown?

If last quarter looked genuinely good on paper, but you're being straight with yourself, something in the team's rhythm felt heavier than the metrics were letting on ....decisions taking three days that should've taken an hour, simple changes somehow needing four people before anything moved.

Most of our clients think this is a sprint planning problem, but actually, it's an overhead that's been quietly building until it's just how everything works, and you can't fix it until you've actually named it.

Here's how: https://zurl.co/YHOyh

Address

Thanet House 231-232 Strand
London
WC2R1DA

Opening Hours

Monday 9am - 5pm
Tuesday 9am - 5pm
Wednesday 9am - 5pm
Thursday 9am - 5pm
Friday 9am - 5pm

Telephone

+442076807105

Website

Alerts

Be the first to know and let us send you an email when Sandhata posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Sandhata:

Shortcuts

Share