Navigation

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.

Adding Browser Logs to your Capybara/Cucumber UI Test Report

UI automation is a big part of the testing industry, because people appreciate reliable advantage of finding regression errors. Even the most advanced QA can make mistakes during monotonous manual testing, but automated tests do not. If you are a test automation engineer or don’t know what kind of test framework to use this is my positive experience with UI test framework called Capybara.

How We Unite Android And iOS Test Automation With Appium

Testing always plays a big role when developing a product for customers. By testing in different stages of development we make sure that bugs are found as soon as possible and customers get a great product. The testing level that makes sure the product has met the business requirements and customer experience will be pleasant is called Acceptance testing.

Acceptance tests are often done manually, so a human can validate that not only the functionality works as expected, but also verify that there are no visual bugs, inconsistencies or annoyances in general. However, when doing big suites of repetitive tests, manual testing is not perfect because human error is inevitable. We can reduce amount of these manual repetitive tasks and improve acceptance tests overall by automating the most crucial ones and those which take less time for a machine to validate.

Automating tests takes a lot of time. For example, if you have an Android or iOS app it’s twice the work. If resources and time are limited you might have to choose only one system’s tests to automate. But we have a solution to greatly reduce the cost of automating acceptance tests in a single project for both – Android and iOS.

Things To Take Into Consideration When Developing Android Apps In 2018

It’s 2018 and here are some things you should consider when developing Android apps. On 17 May 2017, Google announced that it was adopting Kotlin as a high-level programming language for Android development and the usage of it has grown rapidly. The Kotlin plug-in, developed by JetBrains, the same company which created IntelliJ, is now bundled with Android Studio 3.0 and up. So is Kotlin the way to go in 2018? First let’s look what’s expected to be trending this year.

Mobile app trends for 2018

The past year was great for the app economy and 2018 is set to be even better. Mobile apps are more mainstream than ever, and businesses from all industries are diving into this market to boost existing revenue by meeting customer demands. Because development trends change a lot, it is not surprising that new, cutting-edge techniques and tools will emerge. So let’s look at the top trends to focus this year.

How We Test Audio Quality In VoIP Applications

Once a novelty Voice over IP (VoIP) nowadays is a basic requirement for any social application. If not included initially, it will later once the application is gaining popularity.

Our need for VoIP testing came early – with one of our first clients, which had VoIP calls integrated. We started with network traffic analysis – gathering UDP/RTP data stream through Wireshark. While a very simple concept, there is quite a lot that can be found from looking at the data coming to and from the computer. Not only we were able to see the bandwidth used by the calls, we could also see the average packet size and packets sent per second. We also noticed that the data consumption correlated with the audio volume that was sent (which of course we have to take in mind when making any tests), however there was one exception.

How We Test Smart-ID Authentication Solution

Last week in our Riga office we hosted a seminar about Smart-ID. It is an innovative digital identity app in a smart device. Smart-ID offers safe, easy and convenient online authentication. It was launched in the beginning of 2017 and is developed by SK ID Solutions. Smart-ID is used by top Baltic companies in banking, energy, telecom, and retail sector; the network of e-services is growing day by day. Smart-ID is offered by SK ID Solutions AS from Estonia, a privately held company with three shareholders: Swedbank, SEB bank and Telia. They are a qualified trust service provider in European Union. Additionally, they run the core infrastructure for Estonian national electronic ID system. So, they are experts in e-identity solutions and we are helping Smart-ID to improve the quality of their product.

5 Memorable Presentations from “Agile Testing Days 2017”

This year I had the opportunity to visit Agile Testing Days 2017 in Potsdam, Germany which is considered as one of the greatest testing conferences in Europe intended for Agile Software Testing Community (basically for anyone who works in Agile team and is responsible for the Testing and Quality of the Software). This was the 9th Agile Testing Days and seems like the community grows each year (this year there were more than 700 attendees).

It was a four full day conference, and tutorial day on day one, with more than 160 speakers. Does it sound like much? It was. There were up to eight parallel track sessions, so you can imagine the challenge deciding which talks and workshops to attend. There were great experience stories and talks about testing, test automation and agile future as well as best practices and common mistakes to avoid. I would like to share some interesting presentations as they provide some new viewpoints on software testing and new thoughts about how to improve the quality of the software in agile development teams.