TOP 3 Server Configuration Issues and Possible Solutions

If you are reading this chances are that you are somehow involved in web server application development. Either you are a QA, developer, someone from the operations or a little bit of everything. It doesn’t matter to what kind of server architecture or programming language you are exposed to, dealing with HTTP is almost always a must. It’s arguably the most used application layer communications protocol on the web right now.

While writing core web services for API testing product Apimation the author has encountered a number of odd server behaviors which can lead to some very serious issues in production. Here is a list of TOP 3 nastiest, unwanted behaviors and their possible causes:

Debugging HTTP/HTTPS issues with Charles and Fiddler

Most applications use some kind of remote data source. Whether it is a website, some RESTful services, or SOAP APIs, it all comes down to HTTP (Hypertext Transfer Protocol) that handles the requests. When building applications, developers often don’t worry what is happening at the network level. But as things tend to get more complex and unusual bugs appear, looking into the network level could be an invaluable time saver.

If you’ve ever been suspicious of your app consuming unusual amounts of data, having connection problems or you just want to get the best performance out of your app, here are some useful tips that might make you want to consider trying HTTP proxy tools the next time you come across issues related to network communication.

How to Create, Categorize and Filter iOS Logs

We all have heard about logs, we all know what they are and we all use them every day in development and testing process. As an iOS developer, I always try to cover most of the logic with logs for each application layer: networking, database, device layer, user experience, business layer, etc.

By doing so it makes it easier for me, other developers and the QA team to debug the application later on.

Web Service Load Testing With Simulated Users

Singing and dancing is an important part of Latvian culture and every five years we have a grand Song and Dance celebration. It is by far the most attended event in our country and selling tickets to this event is a very challenging task.

Tickets to this years celebration went on sale on March online as well as at the ticket shops, and nearly 100 000 tickets to 19 events sold out in a matter of hours. As many people predicted, the ticket sale didn’t go as planned due to many technical challenges.

We are currently building a web service load testing tool that can simulate load generated from users and this blog post describes our experience with building this tool. There are a lot of things that can go wrong when the load level rises, but we think that our tool can help you pinpoint to issues before they become real problems.

To Automate, Or Not To Automate, That Is The Question

Functional testing is an integral part of any development project. That is why there comes a point in every project when it is necessary to answer the following questions: what kind of testing to choose, at which stage of development it is necessary to start testing, how carefully it should be conducted, what time interval should be provided for testing and others. The answers to these questions mostly depend on the specifics of the project (functional requirements, team size, deadlines, risks, budget), but one trend remains unchanged – the wrong approach to testing guarantees problems in the development cycle and has serious consequences.

Among the least harmful consequences is the failure to meet the deadlines or exceeding the budget. In the worst case, incorrect testing can lead to the fact that eventually the product will not perform the tasks set and the client will not receive a product that meets his needs. This article discusses the factors that will help you choose the optimal type of functional testing.

Our ARKit Experience – Why, Where, What and How?

As software developers, we are always introduced with new features and frameworks. Everything is evolving and we must learn new things. As an iOS developer, once you have a feeling that you have played enough with and gained some knowledge in all commonly used Apple frameworks, you are introduced with new ones. As it happened in WWDC 2017 when we were introduced with ARKit (Augmented Reality Kit).

Why Designers and Developers Should Work Together?

When it comes to thought process and idea execution designers and developers are polar opposites. Both supplement each other well, but, as with most things in life, there can be issues with collaboration and communication between both parties. Sometimes ignorant assumptions govern attitudes, which in the end hurts the end product and the user. I believe that designers and developers should work together more often, because if they don’t, it will cause unnecessary problems.