Systems | Development | Analytics | API | Testing

Most people have encountered frustrating software errors. While the Windows "blue screen of death" was a necessary evil in the 1990s, customers have much more choice in today's software-as-a-service market. A single error or broken workflow is often enough for a would-be customer to switch over to a competitor. Of course, many software businesses mitigate these risks through testing and quality assurance.

Since the release of Xcode 14, numerous code signing issues have emerged, plaguing builds across various CI/CD platforms. And even though code signing process was never easy, issues like these were relatively uncommon in previous versions of Xcode, such as Xcode 13 and Xcode 12, leaving many developers worried. If you are facing some unfamiliar code signing issues with Xcode 14, while everything seems to be fine with your keys and certificates, you aren’t alone.

As you may know, event logs are a common feature in operating systems and other software that keep track of system and application errors. When you have API traffic to follow or front-end actions you want to watch, using Moesif’s Live Event Log is a simple way to filter and find the data you need.

Many API developers and companies struggle to find ways to set up systems to monetize their APIs easily. Some are simple but not customizable and some are complex and require massive engineering effort to actually get it all running. To make things easier, Moesif created the Billing Meters feature which gives massive customizability but with a minimal amount of code and engineering effort to monetize APIs.

Learn why most web apps and web services use REST (RESTful) APIs–and why GraphQL and gRPC APIs are emerging as alternatives to REST APIs in a growing number of organizations. Most web traffic today is actually API traffic for web applications and REST web services.

Learn the fundamentals of DataProvider and how it can be used in TestNG for automated testing. As the volume of applications increases, software testing teams find themselves overburdened with a “combinatorial explosion” of permutations for their test cases. In the early days, we hard-coded our test cases with the most important workflows, and we wrote bespoke automation scripts, each one to handle its own particular use case.

This is a guest post for Integrate.io written by Bill Inmon, an American computer scientist recognized as the "father of the data warehouse." Inmon wrote the first book and first magazine column about data warehousing, held the first conference about this topic, and was the first person to teach data warehousing classes.

Today, API-driven microservices applications are a source of speed to innovation and competitive advantage – according to SmartBear’s most recent State of Software Quality – API report: However, this modern way of architecting software doesn’t come without challenges. Neglecting to adapt a new approach to service architecture design with a new approach to the underpinnings – API design and testing – can undermine the efforts.