In XML, we can at least use basic refactoring techniques based on strings, such as "replace with", etc. In my experience, sooner or later, editing from the GUI will cease to be pleasant and we will switch to the source code that is in XML and (typically for XML) is completely unreadable. shared variables) between individual queries. You have to use the mouse a lot, know what's hidden where, and what is worse, remember about all implicit connections (e.g. Unfortunately, if we start to expand our scenario to add new steps, parameterize the current ones or change their behavior, then very soon, we will come to the conclusion that this is very tedious work. Everything is clear and it's easy to understand what a given test is testing. A very simple business flow in JMeter may look as follows:Īt first glance - quite good. Comparing the readability of the application with the GUI vs the source code is a rather unusual approach, but let's see what comes out of it. Otherwise, tempted by some interesting function that in the long run will be neither so interesting nor so useful, we will end up with a suboptimal test tool. If a tool meets these four basic requirements, only then can we proceed to the analysis of the full spectrum of its functionality. That's why I want to focus on these points to show what is really important when choosing a tool that will be both convenient and maintainable. Of course, there are a lot of specific and useful functionalities, although most tools provide a more or less similar set of options when it comes to creating test scenarios, simulating production traffic, etc. These are the most important aspects when choosing a tool. You may ask, “That's it?” To be honest - yes. How to Choose Tools for Performance Tests?Ĭhoosing a tool for performance testing will be one of the first dilemmas and I hope this article will help you to make the right choice.Īgain, from a developer's perspective, you should expect four main attributes from a good performance testing tool: However, from my observations, it appears that taking shortcuts at the beginning of the game with performance testing may cost us a lot in the future. This is not always possible and does not always make sense. Ideally, performance tests should be part of our Continuous Deployment (CD) cycle. This is sometimes even more expensive than the original creation of such tests.įor the above reasons, my first piece of advice when it comes to performance testing is to think about the whole process in a long-term context. Applications change very dynamically, and thus performance tests should also track these changes and be kept up to date. In addition to the valuable tester or developer time to create them, they also require a dedicated (if possible) environment to conduct such tests. Performance tests are undoubtedly some of the most expensive tests in software development. VFunction is a patented AI-powered platform for companies that intelligently and automatically transforms legacy monolithic applications into microservices. Of course, this is very good for the developers because it creates a feedback loop regarding the quality of their solutions, similarly as in the case of writing unit, integration, or End-to-End (E2E) tests. This is especially true in a situation when the results are different from what we originally expected. Over time, more and more responsibility may be transferred to the testing team, but developers will still be needed to analyze the results. Rather, I want to emphasize that if we have performance testers at our disposal, the application testing process must be carried out in close cooperation between testers and developers, especially at the very beginning. I don't mean that testers can't create good performance tests. Thus, an approach in which a dedicated team of testers who have never touched the source code of the application and must check its performance - will not work. What Should Performance Testing Look Like in a Perfect World?įrom my perspective as a developer, testing the performance of an application is the responsibility of the developer who built it. I've been using both for quite some time and I think it's time to summarize my experiences. There's already a lot of content comparing these two projects out there - so why write another article about it? I'll try to compare the two tools from a slightly different angle. JMeter and Gatling are one of the most popular performance testing tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |