Making software that your target audience will love is no easy feat; after all, even the most brilliant application won’t do anyone much good unless it is carefully planned, structured intuitively and seamlessly implemented. Here we will look at what an API is, how it is tested and why it matters. What is an API? An Application Programming Interface (API) deals with the core functioning of a program and is made up of a collection of protocols, tools, routines and procedures which together determine how components interact with each other. While API usage first started out as a way to facilitate integrations with a set of closed distributed systems it has evolved considerably over the years and now plays a key role in multi-use integrations with both internal and external systems. How does API testing work? API testing takes place at the business or logic level of the software architecture and validates the complete functioning of a component by conducting a number of targeted tests. Basically, an application is used to send ‘calls’ to the API which triggers various responses and these outputs are then recorded and analyzed to determine reliability, functionality, security and overall performance. Service virtualization is also […]
With software applications becoming more complex and the global number of browsers and devices combinations skyrocketing, comprehensive testing has never been more important; however, a lot depends on your ability to pair the right technique with the right application. The following guide to software testing techniques will hopefully help you acquire a better understanding of this often misunderstood process. Software testing methods The three primary software testing methods are known as Black Box, White Box and Grey Box testing. Here is a brief overview of each one. Black Box With this method, testing is conducted without any knowledge of the software’s source code or system architecture. While this blind approach can be rather inefficient it ensures that testing is conducted from a user-perspective rather than that of the program designer. White Box This method implies that the tester has access to application’s architecture and source code. This enables testers to dig deeper into products and identify issues and their causes more easily. Grey Box A mix of the Black and White Box methods, Grey Box testing is conducted with limited access to the internal workings of the program. For instance, while testers may have access to the architecture and the […]
6 years ago, the good folks over at Wufoo held an API contest in which the first prize was a friggin’ battle axe. I thought that was absolutely brilliant on their part and I was positively jealous of how creative their idea was. Ever since we’ve had a public API for Lean Testing I wanted to do something similar. But obviously we couldn’t do it unless we had something more badass to give away than a friggin’ battle axe. Let’s just say that was hard to beat.
Here are two recent Lean Testing news we thought you should know about: Version 3.0 is now live for all users We’ve added a ton of new features in version 3.0. Here are just a few of them:
If you want to ensure that the software you ship is the best possible quality, then you need to maximize your test coverage. The problem is that you have limited time and resources, so how do you maximize your test coverage? Where should you focus your efforts for best results? How can you spread those resources a little further without spreading them too thinly? We have a few tips to share that will hopefully help you maximize that test coverage.