QA Bean

Today let’s talk about what is API testing, and what exactly do we test when we perform API testing? To start from the very beginning lets understand what API is.   What Is API? API – Application Programming Interface. This is a functional piece of a system that sits usually between a data source and a front end presentation to the user. In other words if we take a simple example of a web application the nice looking web site will be using API calls to retrieve data from the back-end database. It is important to understand that API can mean different things in different systems, for example for web application an API can be a SOAP or a REST web service, but for a desktop application API can be a set of known functions that allow retrieve or modify data within that application.   What Do We Test With API? When we talk about API testing we talk about testing some specific functionality that is described in the requirements for that API, and our verification points m

Today I wanted to discuss a very useful tip to get a Wifi Password of a network that your machine used in the past. For software testers this knowledge is particular useful when dealing with lab equipment that was pre-set and required additional changes and modifications. Imagen a scenario when you as a quality assurance analyst in the company have received a lab laptop that you need to install some software on it, and because of the type of the software you expect that pre-set wifi password for your network might be lost. Your first order of business will be to find out and back-up existing passwords, but how to do it? Here is a quick and easy way: The only thing you need for that tip to work is Admin level access to the machine you are working on. We begin by opening a Command Prompt with admin rights Then we write the following command: netsh wlan show profile A list of existing wifi networks profiles will be shown, pick a name of the network you want

Today I want to take a look on the 3 freely available tools that allow for test management without breaking the bank those are good starting point for those who are looking for an alternative for high end tools like HP ALM and Smart Bear Test Complete. Kiwi TCMS This is a test case management tool that allow for proper test case creation and execution with nice reporting functionality. This tool does not contain internal bug tracking but integrates nicely with big players like BugZilla  (A free Bug tracking tool) TestLink This is a full free solution for Software test management. It has it all from Requirement management to test case creation trough reporting and up to bug tracking. Everything can be done in this tool that has a lot of documentation online and a stable version the only downside is that its look and feel very outdated and might concern some modern testers out there XStudio This one is a commercial product that has a free, community, edition. It has a full spect

I lately noticed that there is some confusion going on around the software testing in regards to user facing parts of the system. Testers mention that they are planning to “run some UI testing” or others speak about “strange UX on that system”. I would like to spent some time today and emphasizing the main 3 differences between UI and UX and how we are testing each one, and by whom. But let’s start from the beginning what is UI and what is UX? UI is a User Interface, usually referring to anything that can be visually seen by the user when interacting with the system. That will include colors, page design, logos, element shapes, etc. UX is a User eXperience, usually referring to anything that can be done by the user when interacting with the system. That will include what can be clicked, what can be done, what will be returned back to user and in what way, etc. With that understanding we can now define the 3 most important identification points for each one UI - User inte