We collect the latest Development, Anaytics, API & Testing news from around the globe and deliver it direct to your inbox. One email per week, no spam.
See how Tableflow converts data to Apache Iceberg or Delta Lake format, and how it can be integrated with Amazon Redshift to query and analyze customer activity snapshots.
Before you can test software, you need to know what to test. That’s where many QA teams stall out. They don’t have the right software testing tools for mapping the app, identifying user paths, and determining testing priorities. So, building a test plan can take days (or more) of manual work. It’s often slow, frustrating, and error-prone.
API and AI services now sit at the heart of modern products. However, the more we use them, the harder it seems to become to account for the budget. Launching an AI product often leads to massive end-of-period bills. This requires attributing costs to the key internal power users and consumption drivers. The challenge is identifying the departments, products, or projects responsible for the consumption, and the extent to which they contribute.
Picture this: You’re creating test cases for a new feature. You have a Jira ticket with text requirements, a Figma mockup from design, a workflow diagram from the architect, and a screenshot from a stakeholder meeting. Traditionally, you’d manually translate all of this into test steps: describing the UI in words, interpreting the diagram, cross-referencing the mockup. But what if your testing tool could “see and “understand” all these artifacts directly, just like you do?
If you find that your team is struggling to get releases out the door, it could be inefficient testing practices. Oftentimes, software teams don’t know what their tests actually cover, or which tests are relevant after each code change — so they run everything. This means spending hours executing full test suites for minor updates or burning through CI/CD resources while bugs slip through untested paths. On top of this, software is always becoming more complex.
In this episode of the "Data Cloud Podcast," Dana Gardner is joined by Chandi Kodthiwada, Vice President of Product Management at Komodo Health, to explore how Komodo Health utilizes vast and disparate data sources to generate unprecedented insights in life sciences and healthcare. They discuss the founding mission of Komodo Health, the challenges of building a comprehensive, de-identified data set, and AI’s role in reducing the burden of disease and improving patient outcomes.
We’re entering a phase where AI can draft emails, resolve tickets, summarise complex information, and occasionally present fiction as fact with equal conviction. Generative AI has become incredibly powerful, but in enterprise environments, power without precision quickly becomes a risk rather than an advantage. This is exactly where the shift is happening.
MLRun 1.10, the latest version of our open source AI orchestration framework, is available today to all users. Iguazio started out as a platform to operationalize enterprise machine learning projects. Though we’ve been through quite a few waves of AI in just a short time, the underlying challenges are the same: getting from experimentation to production remains a major blocker.
For a long time, we spoke about “AI agents” like they were a future concept, something that might eventually book flights, run workflows, or make payments on our behalf.