<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Isuri Wickramasinghe on Medium]]></title>
        <description><![CDATA[Stories by Isuri Wickramasinghe on Medium]]></description>
        <link>https://medium.com/@isuriimalsha94?source=rss-6b4d164865e4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QtSKRhPW2jo_F29enC9H8A.jpeg</url>
            <title>Stories by Isuri Wickramasinghe on Medium</title>
            <link>https://medium.com/@isuriimalsha94?source=rss-6b4d164865e4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:53:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isuriimalsha94/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is Performance Testing and Its Types]]></title>
            <link>https://medium.com/@isuriimalsha94/what-is-performance-testing-and-its-types-7d70f935f695?source=rss-6b4d164865e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d70f935f695</guid>
            <category><![CDATA[performance-testing-types]]></category>
            <category><![CDATA[performance-testing]]></category>
            <dc:creator><![CDATA[Isuri Wickramasinghe]]></dc:creator>
            <pubDate>Wed, 27 May 2026 12:46:58 GMT</pubDate>
            <atom:updated>2026-05-27T12:46:58.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q2nHWlCFHZ5BpEJIifSxRQ.png" /></figure><p>In today’s digital world, users demand applications that are quick, reliable, and responsive. Whether it&#39;s a banking app that manages transactions, an e-commerce platform, or a streaming service serving millions of users, performance significantly influences user satisfaction. Therefore, conducting performance testing is crucial.</p><h3>What is Performance Testing?</h3><p>Performance testing is a type of non-functional testing that evaluates how a system behaves under various loads. It assesses the reliability, stability, scalability, speed, and responsiveness of an application.</p><p>The main goal of performance testing is to identify any performance bottlenecks before the application is released to production. This testing verifies whether the system can handle the expected user traffic while maintaining acceptable response times and resource usage. Additionally, it helps to prevent downtime and enhance the overall user experience.</p><h3>Importance of Performance Testing</h3><p>The importance of performance testing is,</p><ul><li>It helps to identify the areas that will break and need fixing by evaluating app performance under heavy loads. This will prevent system failures and improve user experience.</li><li>It helps identify performance bottlenecks before users experience glitches.</li><li>It verifies that the system can scale effectively as the number of users grows.</li></ul><h3>Types of Performance Testing</h3><h4>Load Testing</h4><p>Load Testing is a type of performance testing that evaluates how a system performs under expected user load. It helps ensure the application remains stable, responsive, and efficient when multiple users access it simultaneously.</p><ul><li>Checks response time, speed, and system stability under normal and peak load</li><li>Identifies bottlenecks, crashes, and performance issues</li><li>Ensures the system can handle the expected number of concurrent users</li></ul><h4>Metrics of Load Testing</h4><p>Measures system performance using metrics like response time, throughput, error rate, and resource utilization under varying load conditions.</p><ul><li><strong>Average Response Time</strong>: The average time the system takes to respond to user requests. It indicates how fast the application performs under load and directly affects user experience.</li><li><strong>Error Rate</strong>: The percentage of failed or unsuccessful requests during testing. A higher error rate may signal server overload, configuration issues, or application defects.</li><li><strong>Throughput</strong>: The amount of data processed or transferred per second during testing. It shows how much workload the system can handle efficiently.</li><li><strong>Requests Per Second (RPS)</strong>: The number of requests the system processes each second. It helps measure how well the application manages incoming traffic.</li><li><strong>Concurrent Users</strong>: The number of users actively using the system at the same time. This helps determine whether the system can handle peak usage periods.</li><li><strong>Peak Response Time</strong>: The highest time taken by the system to respond to a request, usually observed during maximum load conditions. It helps identify performance bottlenecks and slow system behavior under heavy traffic.</li></ul><h4>Stress Testing</h4><p>Stress Testing is a software testing technique that evaluates how a system behaves under extreme load conditions beyond normal operating limits. It helps identify performance bottlenecks, system weaknesses, and recovery capabilities to ensure stability and reliability under pressure.</p><ul><li>Evaluates system performance under extreme workloads.</li><li>Identifies bottlenecks, failures, and recovery issues.</li><li>Ensures system reliability during high-pressure situations.</li></ul><h4>Metrics of Stress Testing</h4><p>Stress testing metrics are used to measure system performance under heavy load. Common metrics include:</p><ul><li><strong>Requests per Second:</strong> Number of requests handled per second.</li><li><strong>Load Time:</strong> Average time taken to load</li><li><strong>Time to First Byte (TTFB):</strong> Time taken to receive the first byte of data from the server.</li><li><strong>Transaction Response Time:</strong> Average time required to complete a transaction.</li><li><strong>Transactions per Second (TPS):</strong> Number of successful transactions processed per second.</li><li><strong>Error/Failure Rate:</strong> Number of failed connections or unsuccessful system attempts.</li><li><strong>Test Rounds:</strong> Number of test cycles executed successfully and failed.</li></ul><h4>Spike Testing</h4><p>Spike Testing is a performance testing that evaluates how a system behaves under sudden and extreme changes in user load. It helps identify stability issues, performance bottlenecks, and recovery capability during unexpected traffic spikes.</p><ul><li>Tests the system&#39;s response and stability during abrupt traffic surges.</li><li>Identifies failures, bottlenecks, and scalability issues.</li><li>Ensures quick recovery without crashes or downtime.</li></ul><h4>Endurance Testing</h4><p>Endurance Testing is a non-functional testing that evaluates how a system performs under continuous load over a long period. It helps ensure the application remains stable, responsive, and reliable during extended usage.</p><ul><li>Identifies issues like memory leaks and resource exhaustion during prolonged usage.</li><li>Ensures long-term system stability and reliability under continuous load.</li></ul><h4>Metrics of Endurance Testing</h4><p>Metrics of Endurance Testing are used to measure system performance and stability over a long duration.</p><ul><li><strong>Response Time:</strong> Measures the time taken by the system to respond to user requests. It should remain stable throughout long execution.</li><li><strong>Throughput: </strong>Indicates the number of requests processed per second. Consistent throughput shows good system performance over time.</li><li><strong>CPU Utilization:</strong> Tracks how much CPU is used during testing. High or continuously increasing usage may indicate performance issues.</li><li><strong>Memory Usage:</strong> Monitors memory consumption over time. A steady increase may indicate memory leaks.</li><li><strong>Disk I/O: </strong>Measures read/write operations on disk. High disk activity can slow down system performance.</li><li><strong>Error Rate:</strong> Counts the number of failed or incorrect requests. Increasing errors over time indicate system instability.</li><li><strong>Network Usage:</strong> Tracks data transfer across the network. Helps identify bottlenecks in communication.</li><li><strong>System Stability/Uptime:</strong> Measures how long the system runs without failure. Longer stable uptime indicates better endurance.</li></ul><h4>Volume Testing</h4><p>Volume Testing is a non-functional testing that evaluates how a system performs when handling a large amount of data. It ensures the application can manage high data volumes without performance degradation or failure.</p><ul><li>Focuses on database capacity and data handling capability</li><li>Identifies performance issues under large data loads</li><li>Ensures system stability when data volume increases</li></ul><h4>Scalability Testing</h4><p>Scalability Testing is a non-functional testing that checks how well a system can handle increased workload (users, data, transactions) without affecting performance. It ensures the application can scale up or down smoothly as demand changes.</p><ul><li>Verifies system performance under increasing and decreasing load</li><li>Helps identify bottlenecks and system limits</li><li>Ensures the system can scale efficiently (vertical or horizontal)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8UJqv-ZxlOexsbX3GGtrHw.png" /></figure><h3>Popular Performance Testing Tools</h3><ul><li>Apache Jmeter</li><li>LoadRunner</li><li>K6</li><li>Gatling</li><li>Blazemeter</li></ul><h3>Challenges in Performance Testing</h3><p>Even though performance tests give benefits, it comes with challenges.</p><ul><li>Creating a realistic production-like environment</li><li>Simulating real-world user behavior</li><li>Managing massive datasets</li><li>Handling dynamic architectures</li><li>Identifying root causes of bottlenecks</li><li>Limited Scalability of Test Infrastructure</li><li>Bottlenecks in Load Generation</li><li>Selection of Inappropriate Performance Testing Tools</li><li>Lack of Continuous Performance Testing in CI/CD Pipelines</li></ul><h3>Best Practices for Performance Testing</h3><ul><li>Define clear performance goals and benchmarks</li><li>Execute tests in a production-like environment</li><li>Use realistic workloads and test data</li><li>Monitor system resources during testing</li><li>Integrate performance testing into CI/CD pipelines</li><li>Monitor system resources during testing</li></ul><h3>Conclusion</h3><p>Performance testing is a vital part of software development. It ensures the application remains stable, fast, reliable and scalable under different conditions. Also, it helps the organization to identify the bottlenecks, prevent costly production failures, and improve user experience.</p><p>When choosing a type of performance testing, it’s crucial to have clear objectives in place to achieve the best results. Each type of performance testing serves a unique purpose in evaluating the system behavior. By selecting the appropriate performance testing types based on the performance requirements, you can develop a reliable, fast, stable and scalable system capable of handling real-world requests effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d70f935f695" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Why you should start Test Automation and How?”]]></title>
            <link>https://medium.com/@isuriimalsha94/why-you-should-start-test-automation-and-how-9e37fef0fb9b?source=rss-6b4d164865e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e37fef0fb9b</guid>
            <dc:creator><![CDATA[Isuri Wickramasinghe]]></dc:creator>
            <pubDate>Sat, 14 Aug 2021 16:45:14 GMT</pubDate>
            <atom:updated>2021-08-14T16:45:14.840Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7mvUc_gSIpsGaBOUOAhwyg.jpeg" /></figure><h4>Everything you need to know about Test Automation</h4><p>Automation testing is a technique that uses an application to implement the entire life cycle of the software in less time and provides <strong>Efficiency</strong> <strong>and Effectiveness</strong> to the testing software. And, it’s clear from the name itself that there is no handicraft in automated testing. Everything that humans do in manual testing, is performed by software tools and scripts in automated testing.</p><h3>Why should we Automate?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zScqmYaEyXoo3Usiy3q-IQ.png" /></figure><p>In a traditional environment, testing gets completed at the end of a development cycle. But leaving testing until the end no longer works because most of the companies move toward <strong>Continuous Integration and Continuous Delivery</strong> in which software is constantly in both development and deployment. So continuous testing is a good approach to software testing that aims to ensure quality at all times. At that point, it will be much more productive and time-saving to automate monotonous and repetitive tasks. So the QA engineer can run an automated unit test to check a new piece of code immediately after committing it and see the result immediately.</p><p>As an application grows and becomes more complex, manual testing can easily become cumbersome because the team has to spend time on both regressions and testing new functionality. So the main advantage of test automation is that it can <strong>release manual QA engineers from tiresome and time-consuming work</strong>, such as regression tests. And also after the QA engineer automated testing, those tests can be performed at any time by any team member. And, after the testing cycle is over, anyone in the project team can access the report and see all the reported bugs.</p><h3>What should and shouldn&#39;t Automate?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w8TbbgezrPY83uV3LIBkeQ.png" /></figure><p>In general, most of the repetitive tasks of the product, such as regression and load testing can be performed by automated tests, and other remaining tasks are handled manually. So what should we automate,</p><ol><li><strong>Repeatedly executed TCs</strong><br>In any project, there may be repetitive, and monotonous test cases. When growing the project, executing repetitive test cases manually can be tiresome. So automating these kinds of test cases will be more productive and time-saving.</li><li><strong>Regression tests <br></strong>When the developer did any change to the project, the QA needs to do a regression test to check the recent program or code change has not adversely affected existing features. So automating them will be more advantageous.</li><li><strong>Difficult to perform manually</strong><br>There may be time-consuming test cases that taking higher manual execution time. So executing them manually will be more difficult and bothersome. At this point, it will be more efficient to automate them.</li></ol><p>When considering automating the project, mainly we can use two approaches. One approach is that the project should be <strong>automating</strong> <strong>as much as possible from the beginning</strong>. So when a bug comes in, automate a test for it and when there is a new feature, document each scenario and automate those.</p><p>And the other approach is that <strong>automating core pieces of an application that should always be monitored</strong>. Automation takes up a lot of time and resources to create scripts. So it will be better to build small goals at the beginning such as a subset of existing features and repeatable manual test steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8aaNxFd7WKe-rvzuV1M9tw.png" /></figure><p>Finally, not all types of tests can be automated. For example, automation is not the best option for this type of test case,</p><ol><li><strong>Test Cases that are newly designed<br></strong>We should not automate newly designed test cases i.e the test cases that are not executed. It is better to execute them manually at least one time to understand the requirement.</li><li><strong>Requirements are frequently changing</strong><br>We should start automating when the system gets stable. If the requirements are changing frequently we have to change the automation script several times. That is not a good thing when considering productivity and efficiency.</li><li><strong>User Experience</strong><br> We should not automate usability tests, because the script will never be able to determine whether the application is comfortable to use.</li></ol><h3>When should we Automate?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a7ZYplojoAFVpdDx1NEChA.png" /></figure><p>The most common reason behind <strong>“Why Test Automation fails for your company?” </strong>is that the people are not aware of when to automate and when not to. Important to note that <strong><em>Everything is not possible to Automate</em></strong>, and all the possible scenarios aren’t necessarily worth automating.</p><p>It’s not applicable to use automation when you are testing something that<strong> </strong>tends to have a lot of changes i.e. if the requirements of the project change frequently<strong>.</strong> If you are testing a stable project and if the project needs to test the same areas often, automation is the way to go.</p><p>Below are a few reasons for the team to choose automation:</p><ol><li><strong>Reports required</strong><br>If the team has to submit daily/weekly reports to the client/product owner/stakeholders, then using automation, reports can be run repeatedly without any additional workload.</li><li><strong>Length</strong><br>If the project is for a long-term project it is better to invest time for automating monotonous and repeated tests. Then the team can be able to move to the new functionalities and features.</li></ol><blockquote>So if you are still not aware of when to start automating tests, the recommendation is that you can embark on test automation if you know exactly what your product should be in the future and you don’t have any major changes and revamps.</blockquote><h3>Benefits</h3><blockquote>“ By automating your testing process, your organization will not only save t<strong>ime </strong>and money but also deliver higher quality products. “</blockquote><p>Don’t think automated testing will solve all your problems. A mixture of manual and automated tests is doing a perfect job in software testing. Apart from that test automation offers more benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*iuVYvomYVEjc1S1xlUbksw.png" /></figure><ol><li><strong>Fast</strong><br>Automated tests run significantly faster than manual processes. Unlike humans, scripts don’t get tired so they can be much more productive and time-saving than manual tests.</li><li><strong>Reliable</strong><br>Automated tests are consistently good in quality and performance when running repetitive standardized tests. And it does not get any errors like in manual testings.</li><li><strong>Cost Reduction</strong><br>Automated testing is a one-time cost process. It does not need to spend money whenever testing is required.</li><li><strong>Better Quality software</strong><br>Ability to run more tests in less time with reduced team size i.e. Automated tests perform the same steps each time they are executed and they never forget to record detailed results.</li><li><strong>Increased test coverage </strong><br>Automated software testing can increase the depth and scope of tests to improve software quality. It encourages unattended lengthy test cases. They can even run on multiple machines with different configurations. And it allows regression testing after bug fixes or further development and Data-driven testing i.e running the same test cases using many different inputs.</li><li><strong>Continuous Integration</strong><br>Tests can run automatically whenever code changes are pushed and notify the team or the developer if they fail. So it saves developers time and increases their confidence.</li><li><strong>Improve team focus </strong><br>Automated tests allow teams the opportunity to focus on new implementations rather than executing repeatable actions. So they can use their time and mental power to understand users and improve their overall experience.</li><li><strong>Catch bugs earlier in the process</strong><br>The worse part of some projects is that testers are finding critical issues a few days from the launch, which would be an unpleasant surprise for the team. So to avoid this it is better to perform regression testing as frequently as possible.<em> </em>Automated tests give teams the ability to run more regression tests and catch bugs earlier on in the process.</li><li><strong>Accuracy</strong><br>Even the most careful tester will make mistakes during monotonous manual testing. Automated tests perform the same precise steps every time they are executed and all test results are recording in detail. So it increases the accuracy by reducing human errors.</li></ol><blockquote>“ Manual testing opens up the opportunity for humans to make mistakes “</blockquote><h3>Conclusion</h3><p>Nowadays a lot of manual testing is already being replaced with automated testing. As it offers more benefits, it has become a trend among software testers. Of course, Test Automation remarkably improves the product quality in combination with manual testing. And this can be done using different Automation Testing tools. So let’s meet with the next chapter with Test Automation Tools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e37fef0fb9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>