Operations | Monitoring | ITSM | DevOps | Cloud

Today it’s not unusual to see organizations having implemented mocking in their daily workflow, as mock APIs allow developers to speed up their development and not rely on external services. For those reasons and others, many engineers are looking to learn more about the mocked APIs and how they can best be implemented into their organization.

This is one of a two-part series. You can also learn how to automate the deployment of FeathersJS apps to Heroku. In the software development lifecycle, testing offers benefits that reach far beyond the code itself. Testing assures all parties (developers, clients, project managers, etc) that, while the application may not be completely bug-free, it does what is expected, as expected.

Testing is a vital part of the mobile app development process. Your team can use testing to evaluate the quality, security, and reliability of mobile apps before releasing them to your users. Users who expect their applications to be highly performant and intuitive. There are two ways DevOps teams can perform testing for mobile apps: on-premise (also called self-hosted) or in the cloud. But which of these is the best option for your team?

The modern standards of the web demand that user-facing applications be highly usable and satisfying. When deploying frontends, it’s important to implement a comprehensive testing strategy to ensure your customers are getting the best possible user experience. It can be difficult, however, to gauge the effectiveness of your test suite. For instance, all of your tests may be passing, but they might not cover a specific UI element that is crucial to a critical workflow.

I remember just about three years ago sitting in a companywide meeting in a conference room at the Museum of Modern and Contemporary Art in Lisbon, Portugal (Museu Coleção Berardo, Lisboa). Our CTO, Bernd Engist, was giving us a presentation about some new features we had recently developed on automating the start/stop process of an SAP system.

Delivering business-critical applications and code relies on two key factors; functionality and efficiency. Mock and Unit tests are a few industry standards that aim to ensure the correct functionality of your code, catching potential bugs and issues before deployment. These tests are vital to workflows, CI/CD pipelines, and the overall build and deployment process. While functionality may be sound, one key aspect that is oft-forgotten is the efficiency and performance of your code.

One difficult challenge in the software development cycle is increasing the speed of development while ensuring the quality of the code remains the same. The data world has adopted software development practices in recent years to test data changes before deployment. The testing process can be time-consuming and prone to unexpected errors.

Website regression testing is a form of software testing that helps to identify and fix problems with website content, functionality, and accessibility. It is a vital part of any testing strategy, as it can help to ensure that the website continues to meet user expectations. Website regression testing typically involves running a series of tests against the website to check for any issues. The tests can be performed by an automated system or manually by testers on the development team.

In this article, you’ll be introduced to two different load testing tools that are both able to work with Kubernetes; Speedscale and K6. Throughout this post you’ll be given a comparative view of how each tool performs in five different categories: Ease of setup, developer experience, working with the CLI, creating tests, and integration into CI/CD pipelines.