Test case is the backbone of any testing project. The art of software testing is to write the right test case. Firstly it’s not about how you write it, but rather what scenarios you are writing for. After that, we need to closely tie our test cases with test design and test execution. Let’s explore how to write test cases in the most strategic fashion.

Application developers want to provide the most secure and seamless login experience for their users, but even when following OAuth and OpenID Connect (OIDC) best practices, user experience issues can still be a problem. In this article, we will walk through how developers can provide a secure and seamless login experience to users by providing the login functionality natively within the app itself.

When you’re ready to automate your manual tests, you might naturally think you need to hire someone with a technical skill set who specializes in automating end-to-end tests. That is, you might think you need to hire a QA engineer. It’s not an unreasonable assumption. But for many startups, it’s the wrong thing to do. QA engineers are quite expensive (in more ways than one), bottleneck release processes with their complex tooling, and can present other types of business risks.

Today, we're looking at MySQL vs MS SQL Server. Relational database management systems (RDBMS) form the backbone of enterprise IT. The main difference between MySQL and Microsoft SQL Server is that MySQL is an open-source RDBMS known for its cross-platform compatibility and cost-effectiveness, while Microsoft SQL Server is a commercial RDBMS primarily designed for the Windows platform, offering advanced features and tight integration with Microsoft technologies.

Financial and operational reporting for NetSuite can be a challenge. As is the case with many ERP systems, NetSuite’s reporting capabilities tend to be somewhat restrictive. It can be difficult to pull information from multiple NetSuite modules into a single, cohesive report. In other instances, information for which there ought to be a fairly straightforward reporting process turns out to be inaccessible.

An effective dashboard requires careful design to present data in the best way, and to help more people (users, customers) find insights without feeling overwhelmed. Yellowfin BI comes with a wide variety of chart types as part of its extensive data visualization tools, and while it is tempting to use a lot of eye-catching charts to make a dashboard that looks great, it is important to select the right chart for the right situation.

If you compare the world 10 years ago with today's era, you can easily see the difference. From the difference, we don’t mean how the world looks, rather we mean how it functions now and used to function then. What do you think has changed in how the world functions now compared to back then? Is it purely due to digitalization? Or is it just a mere change? Keeping these questions aside, let us tell you that recent data suggests that people spend around 3 hours and 15 minutes on their phones daily.

In the previous article, we set up the AI API with AWS Lambda and Gateway, integrated it with Moesif, and then connected Stripe with Moesif. We now have the infrastructure to begin billing for API usage. In this article, we move on to configuring Moesif with the following steps in the API monetization journey: First, let’s set the prices we want to charge for API usage in Moesif.

RAG and Fine-Tuning are two prominent LLM customization approaches. While RAG involves providing external and dynamic resources to trained models, fine-tuning involves further training on specialized datasets, altering the model. Each approach can be used for different use cases. In this blog post, we explain each approach, compare the two and recommend when to use them and which pitfalls to avoid.