This thesis deals with a load testing of web applications. The text is introduced with a definition of the load testing, reasons for its execution and a description of its types. Recommended procedures are provided for preparation, execution and evaluation of the testing. Several commercial and open-source load testing tools are described. Cloud testing -- the contemporary phenomenon -- is also included. The entire process of load testing depicted in this text is demonstrated on a selected application. A following chapter briefly deals with a profiling of web applications. It, again, covers its definition and its purpose, accompanied with a practical example. The aim of this thesis is to introduce the reader to the world of load testing, which is primarily accomplished by describing an example, which provides an in-depth explanation for every step necessary in order to perform the web application testing successfully.

The title of graduation work is development of techniques of software testing. The objective of research is studying of the testing process, defect types in the software and their tracking, methods of creating and applying test cases, and development of auto-test project for the web service “Expert”. An additional objective is to conduct stress testing for the web service "Expert". The first part is devoted to the theoretical foundations of testing: a place of testing in software development, testing process in it-companies, review of defects and their tracking, and techniques of creating tests and their applying. The second part is devoted to the review of software for load testing and it’s practical usage for testing the web service “Expert”. The last part is devoted to the study of automation functional testing and development of the auto test project for the web service “Expert”. The graduation work consists of an introduction, 12 chapters and conclusion on 106 pages, including 55 figures and the list of 15 references. / Тема выпускной квалификационное работы: разработка методики тестирования программного обеспечения. Цель работы: изучение процесса тестирования, видов дефектов в ПО и их отслеживание, способов создания и применения тест кейсов, и, на основе полученных знаний, разработка проекта авто-тестов для веб-сервиса "Эксперт". Дополнительной целью является проведение нагрузочного тестирования для веб-сервиса "Эксперт". Первая часть работы посвящена теоретическим основам тестирования: место тестирования в разработке ПО, процесс тестирования в IT-компаниях, обзор дефектов, способов их отслеживания, а также техник создания тестов и их применение. Вторая часть посвящена обзору ПО для нагрузочного тестирования и его практическое использование для тестирования веб-сервиса «Эксперт». Третья часть посвящена изучению процесса автоматизации функционального тестирования и разработке авто-тестов для веб-сервиса «Эксперт». Выпускная работа состоит из введения, 12 глав и заключения, изложенных на 106 страницах, а также списка литературы и приложений. В работе имеется 55 рисунков. Список литературы содержит 15 наименований.

Microservice architecture, which involves breaking down applications into smaller and loosely coupled components, is becoming increasingly common in the development of modern systems. Connections between these components can be established in various ways. One of these approaches is event-driven architecture, where components in the system communicate asynchronously with each other through message queues.  AWS, Amazon Web Services, the largest provider of cloud-based services, offers such a messaging queue: SQS, Amazon Simple Queue Service, which can be integrated with SNS, Amazon Simple Notification Service, to enable "one-to-many" asynchronous communication.  An alternative tool is Apache Kafka, created by LinkedIn and later open-sourced under the Apache Software Foundation. Apache Kafka is an event logging and streaming platform that can also function as a message queue in an event-driven architecture.  The authors of this thesis have been commissioned by Scania to compare and evaluate the performance of these two tools and investigate whether there are use cases where one might be more suitable than the other. To achieve this, two prototypes were developed, each prototype consisting of a producer microservice and a consumer microservice. These prototypes were then used to conduct latency and load tests by producing messages and measuring the time interval until they were consumed.  The results of the tests show that Apache Kafka has a lower average latency than SNS/SQS and scales more efficiently with increasing data volumes, making it more suitable for use cases involving real-time data streaming. Its potential as a message bus for loosely coupled components in the system is also evident. In this context, SNS/SQS is equally valuable, as it operates as a dedicated message bus with good latency and offers a user-friendly and straightforward setup process. / Mikrotjänstarkitektur, som innebär att applikationer bryts ned till mindre och löst kopplade komponenter, är något som blir allt vanligare vid utvecklingen av moderna system. Kopplingar mellan dessa komponenter kan etableras på olika sätt. Ett av dessa tillvägagångssätt är händelsedriven arkitektur, där komponenterna i systemet kommunicerar asynkront med varandra genom meddelandeköer.  AWS, Amazon Web Services, som är den största leverantören av molnbaserade tjänster, tillhandahåller en sådan meddelandekö: SQS, Amazon Simple Queue Service, som kan integreras med SNS, Amazon Simple Notification Service för att möjliggöra ”en-till-många” asynkron kommunikation.  Ett alternativt verktyg är Apache Kafka, skapat av Linkedin och senare öppen källkodspublicerad under Apache Software Foundation. Apache Kafka är en händelselogg och strömningsplattform som även kan fungera som en meddelandekö i en händelsedriven arkitektur.  Författarna av detta arbete har på uppdrag av Scania blivit ombedda att jämföra och utvärdera prestandan hos de två verktygen samt undersöka om det finns användningsfall där det ena kan vara mer lämpligt än det andra. För att uppnå detta utvecklades två prototyper, där varje prototyp består av en producent- och en konsumentmikrotjänst. Dessa prototyper användes sedan för att genomföra latens- och lasttester genom att producera meddelanden och mäta tidsintervallet till dess att de konsumerades.  Resultatet från testerna visar att Apache Kafka har lägre genomsnittlig latens än SNS/SQS och skalar mer effektivt vid ökande datamängder, vilket gör det mer lämpat för användningsfall med realtidsströmning av data. Dess potential som meddelandebuss för löst kopplade komponenter i systemet är också tydlig. I detta sammanhang är SNS/SQS lika användbart, då det fungerar som en dedikerad meddelandebuss med god latens och en användarvänlig och enkel startprocess.