<html><body><h2 style="margin-left:-18pt;text-align:justify;">1. What is capacity in performance test? </h2>Capacity in performance testing refers to the ability of a system to handle a specific workload or user traffic volume while maintaining acceptable performance levels. In other words, it is the maximum amount of load or traffic a system can handle without any performance issues such as slow response times, high error rates, or system crashes. Capacity testing involves simulating a high volume of user traffic on the system to identify bottlenecks and performance issues, and to determine the maximum amount of load the system can handle.<h2 style="margin-left:-18pt;text-align:justify;">2. Why is capacity measurement important in performance test?</h2><ul><li>First, Capacity measurement can help ensure that an application can handle the expected number of users or data without experiencing any performance issues.</li><li>Second, the Capacity measurement helps to identify the bottlenecks in performance of system, and allow the performance engineers to optimize an application's performance to handle larger loads effectively. </li><li>Finally, the Capacity measurement ensures that an application is scalable for the future growth or increasing performance of the system in peak time.</li></ul><h2 style="margin-left:-13.5pt;text-align:justify;">3. How to measure capacity in performance test?</h2>By considering factors that are able to affect the capacity of a system, performance engineers can identify exactly capacity and areas to optimize the system resources. Some of critical factors of the system should be considered as:<ul><li>Hardware resources, including the CPU, memory, disk space, and network bandwidth.</li><li>Software architecture, including the number of servers, load balancers, and databases.</li><li>Expected user behavior, such as the number of users, the type of requests, and the frequency of requests</li><li>Network infrastructure, including the bandwidth, latency, and packet loss.</li><li>Testing environment, including the tools and techniques used for performance testing.</li><li>System configuration, including the settings for caching, logging, and other parameters. </li></ul> To measure the capacity of system effectively and identify potential performance issues, performance engineers can use the following strategies and work closely with developer team and stakeholders as <ul><li>Define realistic user scenarios and traffic volumes based on the system's expected usage patterns.</li><li>Choose appropriate performance testing tools that can simulate realistic user behavior and traffic volumes.</li><li>Conduct a series of tests with gradually increasing loads, starting from low loads and increasing to peak loads, to identify the system's maximum capacity.</li><li>Monitor key system metrics such as response time, throughput, CPU usage, memory usage, and network utilization during the tests.</li><li>Analyze the test results to identify performance issues such as slow response times, high error rates, or bottlenecked resources.</li><li>Use profiling tools to drill down and identify the root cause of performance issues.</li><li>Make more changes to improve capacity and performance of the system, such as optimizing code, tuning database settings, or upgrading hardware or infrastructure.</li><li>Repeat the testing process to ensure that the changes have had the desired effect on the system's capacity and performance. </li></ul> Available tools to measure capacity of the system:<ul><li>Apache JMeter is used to test the performance and capacity of web applications.</li><li>LoadRunner is a commercial tool from Micro Focus that can be used to test the performance and capacity of various types of applications, including web, mobile, and cloud applications.</li><li>Gatling is an open-source tool that can be used to test the performance and capacity of web applications.</li><li>Apache Bench is a command-line tool that can be used to test the performance and capacity of web servers.</li><li>Tsung is an open-source tool that can be used to test the performance and capacity of various types of applications, including web, SOAP, and XMPP applications.</li><li>Locust is an open-source tool that can be used to test the performance and capacity of web applications.</li></ul><h2 style="margin-left:-18pt;">4. Best practices for system capacity measurement </h2>Measuring capacity can present several challenges for performance engineers. Here are some of the most common challenges in capacity measurement:<ul><li>Limited Resources, such as time, budget, or test hardware, can make it challenging to conduct thorough capacity testing. It can be difficult to simulate real-world traffic volumes and user behavior with limited resources.</li><li>Complex Systems with multiple components, dependencies, and integration points can be difficult to test comprehensively. It can be challenging to isolate performance issues in such systems.</li><li>Changing Requirements can make it difficult to plan and execute capacity testing effectively. Unexpected changes in traffic volumes or user behavior can lead to inaccurate test results.</li><li>Lack of Test Data can make it difficult to simulate realistic user behavior and traffic volumes. Without adequate test data, it can be challenging to generate accurate test results.</li><li>Scalability Issues can arise when the system's capacity is insufficient to handle growing traffic volumes or user activity. It can be challenging to predict future capacity requirements and ensure that the system can scale to meet them.</li><li>Unreliable performance testing tools can lead to inaccurate test results and make it challenging to identify performance issues. Using the wrong tools or outdated versions of tools can also result in inaccurate test results.</li></ul> Here are some best practices that can help performance engineers measure the capacity of a system effectively:<ul><li>Defining clear objectives for capacity testing, such as determining the maximum number of users the system can handle or identifying performance bottlenecks, is important to help focus testing efforts and ensure that the testing is aligned with the goals of the project.</li><li>Using realistic test scenarios that reflect the expected usage patterns of the system will help ensure that the testing is relevant and accurate. Using production-like environments helps to ensure that the testing environment accurately reflects the production environment.</li><li>Using appropriate testing tools that can simulate realistic user behavior and traffic volumes will help ensure that the testing accurately reflects the expected usage patterns of the system.</li><li>Monitoring key system metrics during testing, such as response time, throughput, CPU usage, memory usage, and network utilization, will help identify performance issues and ensure that the testing accurately reflects the system's performance.</li><li>Conducting multiple rounds of testing with gradually increasing loads to identify the system's maximum capacity and any performance bottlenecks is essential.</li><li>Collaborating closely with development teams to identify and resolve performance issues will ensure that performance issues are resolved efficiently and effectively.</li><li>Documenting and sharing test results will ensure that everyone is aware of the system's capacity and any performance issues.</li></ul><h2 style="margin-left:-18pt;">5. Conclusion</h2>Capacity Measurement in performance test is essential to ensure that an application can handle the expected number of users or data without experiencing any performance issues. By using load testing, stress testing, and scalability testing, performance engineers can determine an application's capacity and optimize it for the expected usage. By following best practices such as defining realistic load scenarios, starting with baseline testing, monitoring key performance indicators, and using cloud-based testing, performance engineers can deliver high-performing applications that meet the needs of their users.Source: https://saigontechnology.com/blog/the-basic-concepts-of-performance-test-capacity</body></html>

Capacity is one of the most important performance factors in ISO 25010 and is a critical aspect of performance testing because it helps the organizations determine the scalability of their system and ensure that it can handle expected traffic volumes. In this article, we will discuss what capacity is in a performance test, why it is essential, and how to measure it effectively.

The Basic Concepts Of Performance Test - Capacity

<html><body><h3>1. Introduction</h3>It can be said that, with the convenience of smartphones, more and more people use them today. So, it is obvious that mobile apps have become important things in daily life, from ordering food, booking a car, connecting with friends, and family, or making money online.With the growing number of mobile users, it is essential to make sure that the application works correctly, is reliable, and is user-friendly. In this topic, we will have an overview of types of mobile testing, and also discuss the challenges and best practices of testing to deliver quality applications that meet clients’ needs.<h3>2. Types of mobile applications</h3>Firstly, we will go through mobile application types to know which typical types the market currently has. Basically, there are 3 main types according to the technology used to create mobile apps:Native apps: It is a type of application developed for a particular mobile operating system (iOS or Android). That means that if a native app is built in iOS only, the user cannot find it on CH Play Store.Web apps: A web application is more or less a website that looks and feels more like a mobile application. Web apps can be accessed directly via a browser, such as Google Chrome, Safari, Firefox, or Edge.Hybrid apps: As the name indicates, hybrid apps combine elements of native apps and web apps. Users are able to download and install on the device (iOS or Android) and open via a web browser. Some hybrid apps are Instagram, Twitter, Amazon, and Gmail, etc.<h3>3. Types of mobile application testing</h3>First of all, testing is an essential stage of any software development life cycle that helps to ensure an application’s quality, usability, and security.<img src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-heJoxXu5mgg6Qr9smAQr0esklZWYIJOK1BsYJ7p1.png">Free source: <a href="https://www.freepik.com/free-vector/tiny-people-testing-quality-assurance-software-isolated-flat-vector-illustration-cartoon-character-fixing-bugs-hardware-device-application-test-it-service-concept_10613736.htm#query=testing%20types&amp;position=18&amp;from_view=search&amp;track=ais">https://www.freepik.com</a>There are various mobile testing types to make sure that the application works correctly, depending on the type of application, and the client’s request, suitable testing types can be selected to carry on. Below are the main testing types for mobile applications.Functional testing: As the name implies, it is focused on verifying that the mobile application functions correctly and meets the specifications. Performance testing: This type of testing is used to evaluate the application's performance under different scenarios, such as high traffic, low battery, and bad network conditions. Compatibility testing: This testing type is to verify the mobile application's compatibility with different devices, operating systems, and network configurations. Testers may check whether the app runs smoothly on various devices with different screen sizes, hardware, and software specifications.Security testing: Security testing is vital for mobile applications as they often handle sensitive user data. This testing includes checking for vulnerabilities, potential threats, and malware that can cause damage or steal user information.Usability testing: This type evaluates the app in terms of user friendly and easy to use the application.Installation testing: Installation testing is conducted to verify the installation, updates, and uninstallation of the mobile application. This testing also includes checking the app's compatibility with different app stores and versions.<h3>4. Challenges in mobile application testing</h3>Mobile application testing involves verifying the functionality, usability, performance, security, and compatibility of applications across different devices and platforms. Here are some of the difficulties that testers may face during testing activities:Multiple devices: There are many different mobile devices, operating systems, and screen sizes, making it challenging to test the application on all devices.Network: Mobile devices run on different types of networks, which can cause variations in the application's performance and functionality. For example, using the app in a bad connection, interrupting the network while using, or in airplane mode.Security testing: Mobile applications are susceptible to security vulnerabilities, such as data leakage, and unauthorized access. Testing for these cases is crucial to ensure the safety and privacy of user data.Automation challenges: Mobile applications may require a different approach to test automation, as there are different operating systems and devices to consider. Additionally, some functionalities of the application may not be easily automated, and also carried on by experienced automated testers to build the automation framework from scratch.<h3>5. Best practices</h3>Talking to tips for testing on mobile apps, we can refer to the following points to apply in the specific project to get better testing outcomes.Follow the test plan: Before starting mobile testing, it is necessary to have a testing plan. This includes identifying the testing objectives, and the scope of testing, choosing the tools and techniques, and determining the testing milestones.Test across multiple devices and platforms: Mobile devices come in various operating systems, and sizes. Therefore, it is important to test your mobile application across multiple devices and platforms to ensure that it works consistently across different environments.Test for different network conditions: Mobile applications are designed to work in various network conditions. For that reason, test mobile applications under different network conditions to ensure that it functions as expected.Usability testing: A mobile application should be user-friendly to all users, so it is also important to spend time on usability testing besides the main function test.Automate your testing: Choosing the proper test automation tools and frameworks to automate can help improve testing efficiency and reduce testing time.Teamwork: Collaboration between the testing and development teams is essential for mobile testing. This includes sharing information on bugs, issues, and test results - it is faster and more effective than working independently.Exploratory testing: Mobile testing has different aspects than web/desktop testing. There may be edge cases that will happen to users that sometimes testers can not find while performing functional testing. At that time, exploring testing is the best choice that testers can apply to test the app.<h3>6. Conclusion</h3>Last but not least, mobile application testing cannot be skipped in the software development life cycle. By following the test plan and best practices, mobile applications can be delivered to clients with high quality, reliability, and user-friendliness. With good test results, the application can be released with confidence, knowing that it has been thoroughly verified and meets the expectations of clients.Source: https://saigontechnology.com/blog/testing-of-mobile-application---challenges-and-best-practices</body></html>

With the convenience of smartphones, more and more people use them today. For that reason, mobile testing becomes essential before the app is released, to make sure the functions work properly and the user's data is secured. Let's explore the basics of mobile testing in this article.

Testing of mobile application - Challenges and Best Practices

<html><body><h2 style="text-align:justify;">1. What is Time Behavior?</h2>Time behavior is the measurement of an application's ability to react to different events over time, encompassing the duration required for the application to perform particular actions such as loading a page, running a query, or processing a transaction. Time behavior also includes evaluating how the application performs under various loads, including high traffic or heavy user activity.<h2>2. Why Is Time Behavior Important In Performance?</h2><ul><li>Time behavior is a critical aspect of performance testing as it helps in identifying potential bottlenecks and performance issues. By measuring the application's response time under different scenarios, performance engineers can identify which parts of the application are causing delays and where improvements are needed. This information can help developers optimize the application's performance and improve its overall efficiency.</li><li>Time behavior also plays a crucial role in user satisfaction. Users expect applications to respond quickly and efficiently, and slow response times can result in frustration and dissatisfaction. By understanding the application's time behavior, developers can ensure that the application meets users' expectations and provides a seamless experience.</li></ul><h2 style="text-align:justify;">3. Measuring Time Behavior In Performance Testing</h2>Time Behavior in ISO 9126 quality management:<img class="image_resized" style="width:85.42%;" src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-Rn9TZQhJLz1ZjvKjSVbUhNp1aScn344bu4qCopSH.png">Time Behavior in ISO 25010 quality management:<img class="image_resized" style="width:84.97%;" src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-iy6V3h2r5aA5aglVRlvppvWdjEKqexXw4Y1u4XXg.png">The time behavior evaluation is the most common objective of the performance testing. This aspect evaluates the ability of a component or system to respond to user behaviors within a specified duration and under the other conditions. The time behavior measurements can differ between the system's response time from user input and the number of CPU cycles needed by a software component to perform a specific task. Since time behavior is a quality metric for dedicating the system to good or bad performance, it becomes the necessary metric to be verified while doing performance verification.  Many questions can be raised while gathering the performance requirements. A defined goal's first priority is the user behaviors' response time as<blockquote><ul><li>If the actual response time is exactly 2 seconds, is it a failure expectation?</li><li>What about 2.01 seconds?</li></ul></blockquote>Time behavior can be measured differently. It should become the standard practice  for the performance engineer to acquire the performance requirements from the stakeholders. The performance engineer can ask the following questing for the TIME MEASUREMENT:<blockquote><ul><li>Is this the maximum response time? </li><li>Is this the average response time?</li><li>Is this a percentile time and if so, what is the exact percentile?</li></ul></blockquote>Increasingly, the percentile measure is being used. It can be more useful to know that 95% of the user responded within two seconds than dining a maximum response time. And the other concerned questions are:<blockquote><ul><li>Why should it be 02 seconds? Should it be less than?</li><li>What are the impacts if the system under test took longer than the expected response time?</li><li>Would the business lose the customers if the application makes them wait longer than the expected response time?</li><li>How does the longer wait time affect the user’s experiences?</li><li>What does “response time” mean?</li><li>Does the response time mean that the time of transaction has completed the entire operation? Or that a connection time to the target server has been completed?</li><li>What’s the system?</li><li>Is the time of transaction measured from the end user’s local machine through the application stack and back to their local machine? </li><li>Or is response time measured from the point the web request passes the organization firewall through the application stack and back to the firewall?</li></ul></blockquote>Crucially, for what user actions or behavior is the attainment of a two-second response time deemed necessary? Is a single user logging in, and logging out of the system? Five users? A thousand? And thousands? What happens to the system's performance? How does the system scale up to satisfy the client’s behaviors? Besides, the total number of transactions that need to be completed (throughput) can also affect the timing behavior. A single transaction being processed can complete quite quickly, while a thousand transactions being processed together (much higher throughput rates) can take longer.<h2>4. Time Behavior In Static Testing</h2>The performance engineers can detect and remove defects early in the software development lifecycle before the code execution by reviewing the requirements, architecture designs, and implementing source code. This activity is called Static Testing.So, in the static testing the performance issues can be found beyond the scope of the project. Ultimately, static testing can also allow the performance engineers to ask relevant questions against the non-executable components of the project for detecting the potential issues of time behavior as below:<blockquote><ul><li>Will the response time be within the defined time constraints?</li><li>Have all the all time constraints been explicitly defined in relation to average, maximum, or percentile response times?</li><li>Have all temporal restrictions been precisely delineated with regards to response times in terms of mean, maximum, or percentile values?</li><li>Have these response times been validated against real-world scenarios?</li><li>Has the assessment of these response times been carried out by various parties involved in the project? </li><li>Has the evaluation of aggressive time behaviors' effects, such as extremely low response times, been conducted in relation to the other project features, including cost, scope, quality, and risk?</li></ul></blockquote><h2 style="margin-left:-18pt;">5. Conclusion</h2>Time behavior is a fundamental concept in performance testing that helps in identifying performance issues and optimizing application performance. By measuring response time, latency, and throughput, performance engineers can gain insight into the application's behavior under various scenarios and identify areas for improvement. Understanding time behavior is crucial for ensuring that applications meet users' expectations and provide a seamless experience. References<ul><li>ISTQB Certified Tester Foundation Level Specialist.</li><li>ISO 9126 quality management</li><li>ISO 25010 quality management</li></ul></body></html>

Developing a high-performance and scalable system is a complex task, and organizations must find practical and cost-effective approaches to build large-scale applications. Before we get into how to do it right, let's look at Time Behavior, which is one of the most important performance factors in ISO 25010.

&lt;html&gt;&lt;body&gt;&lt;h2 style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:16pt;&quot;&gt;1. What is Time Behavior?&lt;/span&gt;&lt;/h2&gt;&lt;p style=&quot;margin-left:4.5pt;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Time behavior is the measurement of an application's ability to react to different events over time, encompassing the duration required for the application to perform particular actions such as loading a page, running a query, or processing a transaction. Time behavior also includes evaluating how the application performs under various loads, including high traffic or heavy user activity.&lt;/span&gt;&lt;/p&gt;&lt;h2&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:16pt;&quot;&gt;2. Why Is Time Behavior Important In Performance?&lt;/span&gt;&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Time behavior is a critical aspect of performance testing as it helps in identifying potential bottlenecks and performance issues. By measuring the application's response time under different scenarios, performance engineers can identify which parts of the application are causing delays and where improvements are needed. This information can help developers optimize the application's performance and improve its overall efficiency.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Time behavior also plays a crucial role in user satisfaction. Users expect applications to respond quickly and efficiently, and slow response times can result in frustration and dissatisfaction. By understanding the application's time behavior, developers can ensure that the application meets users' expectations and provides a seamless experience.&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;h2 style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:16pt;&quot;&gt;3. Measuring Time Behavior In Performance Testing&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;background-color:transparent;color:#434343;font-size:13.5pt;&quot;&gt;&lt;strong&gt;Time Behavior in ISO 9126 quality management:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:center;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;&lt;img class=&quot;image_resized&quot; style=&quot;width:85.42%;&quot; src=&quot;https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-Rn9TZQhJLz1ZjvKjSVbUhNp1aScn344bu4qCopSH.png&quot;&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#434343;font-size:13.5pt;&quot;&gt;&lt;strong&gt;Time Behavior&nbsp;in&nbsp;&lt;/strong&gt;&lt;i&gt;&lt;strong&gt;ISO 25010&lt;/strong&gt;&lt;/i&gt;&lt;strong&gt; quality management:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:center;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;&lt;img class=&quot;image_resized&quot; style=&quot;width:84.97%;&quot; src=&quot;https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-iy6V3h2r5aA5aglVRlvppvWdjEKqexXw4Y1u4XXg.png&quot;&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;The&nbsp;&lt;strong&gt;time behavior evaluation&lt;/strong&gt; is the most common objective of the performance testing. This aspect evaluates the ability of a component or system to respond to user behaviors within a specified duration and under the other conditions. The time behavior measurements can differ between the system's response time from user input and the number of CPU cycles needed by a software component to perform a specific task. Since&nbsp;&lt;strong&gt;time behavior is a quality metric&lt;/strong&gt; for dedicating the system to good or bad performance, it becomes the necessary metric to be verified while doing performance verification.&nbsp; Many questions can be raised while gathering the&lt;strong&gt; performance requirements&lt;/strong&gt;. A defined goal's first priority is the user behaviors' response time as&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;If the actual response time is exactly 2 seconds, is it a failure expectation?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;What about 2.01 seconds?&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Time behavior can be measured differently. It should become the standard practice&nbsp; for the performance engineer to acquire the performance requirements from the stakeholders. The performance engineer can ask the following questing for the&nbsp;&lt;strong&gt;TIME MEASUREMENT:&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Is this the&nbsp;&lt;strong&gt;maximum response time&lt;/strong&gt;?&nbsp;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Is this the&nbsp;&lt;strong&gt;average response time&lt;/strong&gt;?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Is this a&nbsp;&lt;strong&gt;percentile time&lt;/strong&gt; and if so, what is the exact percentile?&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Increasingly, the percentile measure is being used. It can be more useful to know that 95% of the user responded within two seconds than dining a maximum response time. And the other concerned questions are:&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Why should it be 02 seconds? Should it be less than?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;What are the impacts if the system under test took longer than the expected response time?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Would the business lose the customers if the application makes them wait longer than the expected response time?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;How does the longer wait time affect the user&rsquo;s experiences?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;What does &ldquo;response time&rdquo; mean?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Does the response time mean that the time of transaction has completed the entire operation? Or that a connection time to the target server has been completed?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;What&rsquo;s the system?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Is the time of transaction measured from the end user&rsquo;s local machine through the application stack and back to their local machine?&nbsp;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Or is response time measured from the point the web request passes the organization firewall through the application stack and back to the firewall?&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Crucially, for what user actions or behavior is the attainment of a two-second response time deemed necessary? Is a single user logging in, and logging out of the system? Five users? A thousand? And thousands? What happens to the&lt;strong&gt;&nbsp;&lt;/strong&gt;&lt;i&gt;&lt;strong&gt;system's performance&lt;/strong&gt;&lt;/i&gt;? How does the system scale up to satisfy the&nbsp;&lt;i&gt;&lt;strong&gt;client&rsquo;s behaviors&lt;/strong&gt;&lt;/i&gt;?&nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Besides, the total number of transactions that need to be completed (throughput) can also affect the timing behavior. A single transaction being processed can complete quite quickly, while a thousand transactions being processed together (much higher throughput rates) can take longer.&lt;/span&gt;&lt;/p&gt;&lt;h2&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:16pt;&quot;&gt;4. Time Behavior In Static Testing&lt;/span&gt;&lt;/h2&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;The performance engineers can detect and remove defects early in the&nbsp;&lt;i&gt;&lt;strong&gt;software development lifecycle&lt;/strong&gt;&lt;/i&gt; before the code execution by reviewing the requirements, architecture designs, and implementing source code. This activity is called&nbsp;&lt;i&gt;&lt;strong&gt;Static Testing.&lt;/strong&gt;&lt;/i&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;So, in the static testing the&nbsp;&lt;i&gt;&lt;strong&gt;performance issues&lt;/strong&gt;&lt;/i&gt; can be found beyond the scope of the project. Ultimately, static testing can also allow the performance engineers to ask relevant questions against the non-executable components of the project for detecting the potential issues of time behavior as below:&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;Will the response time be within the defined time constraints?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;Have all the all time constraints been explicitly defined in relation to average, maximum, or percentile response times?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;Have all temporal restrictions been precisely delineated with regards to response times in terms of mean, maximum, or percentile values?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;Have these response times been validated against real-world scenarios?&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;Has the assessment of these response times been carried out by various parties involved in the project?&nbsp;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;Has the evaluation of aggressive&nbsp;&lt;i&gt;&lt;strong&gt;time behaviors' effects&lt;/strong&gt;&lt;/i&gt;, such as extremely low response times, been conducted in relation to the other project features, including&nbsp;&lt;i&gt;&lt;strong&gt;cost, scope, quality, and risk&lt;/strong&gt;&lt;/i&gt;?&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;&lt;h2 style=&quot;margin-left:-18pt;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:16pt;&quot;&gt;5. Conclusion&lt;/span&gt;&lt;/h2&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#0e101a;font-size:13pt;&quot;&gt;Time behavior is a fundamental concept in performance testing that helps in identifying performance issues and optimizing application performance. By measuring response time, latency, and throughput, performance engineers can gain insight into the application's behavior under various scenarios and identify areas for improvement. Understanding time behavior is crucial for ensuring that applications meet users' expectations and provide a seamless experience.&lt;/span&gt;&lt;/p&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&nbsp;&lt;/p&gt;&lt;p style=&quot;text-align:justify;&quot;&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:11pt;&quot;&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;&lt;i&gt;&lt;strong&gt;ISTQB Certified Tester Foundation Level Specialist.&lt;/strong&gt;&lt;/i&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;&lt;i&gt;&lt;strong&gt;ISO 9126&lt;/strong&gt;&lt;/i&gt; quality management&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;background-color:transparent;color:#000000;font-size:13pt;&quot;&gt;&lt;i&gt;&lt;strong&gt;ISO 25010&lt;/strong&gt;&lt;/i&gt; quality management&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/body&gt;&lt;/html&gt;

The Basic Concepts Of Performance Test - Time Behavior

Performance Test

<html><body><h2>1. What is API Testing?</h2>First, we need to know about API. API stands for Application Programming Interface. That’s all. Then, you may ask: what is its real meaning? So, let's go with Application Programming first. Application Programming usually has 3 layers: User Interface, Business Logic, and Data Storage. Did you notice it, the “interface” word? “Interface” here means something simple like “A way that can be used to interact with something”. User Interface means “A way that User can use to interact with the Application”.And the “Application Programming Interface” means: “A way that Application Programming can use to interact with the Application/System ”. It is not for a specific User to use, just for the interaction between Machine to Machine, Service to Service or System to System, so we can call API is the middleware for the communication.With this information, let's go to “What is API Testing?”API Testing is not only similar to other kinds of Software testing: to ensure that the API is matched with the expected behavior (functionality), but also to test the non-functional aspect of the API which can affect the entire system (performance, reliability, security). API Testing is the most crucial part of the software development life cycle, so no doubt that this is the most challenging part. But, it is just a piece of cake if you understand it clearly and have a good plan to do it. Let’s see.<h2>2. Definition of Done for API Testing</h2>Most of the time, testing a single API can be done with 3 simple steps: <ul><li>Step 1: Send the request: to the targeted server URL with the desired parameter</li><li>Step 2: Get the Response from the targeted server</li><li>Step 3: Validate the Response: as expected from the test case</li></ul>But as usual, we need to define the scope and the test case for API Testing first. So, to make sure that an API is tested thoroughly, we need to focus on the test case and the steps above, especially for step 3: Validate the Response.DoD for API Testing can be split into 2 parts:<h3>Functional Testing:</h3>First of all, we need to make sure the API works correctly and matches all the requirements. Things that can be listed are:<ul><li>API is available to use</li><li>Response codes are correct: for Failed or for Success case</li><li>Response body output is correct: for the Success case</li><li>The error message is correct: for the Failed case</li><li>Make sure that only the right person with the correct permission can use the API.</li></ul>If the API passed these tests, we can say that the feature related to this issue will work correctly without any mismatch in the behavior.<h3>Non-functional Testing:</h3>If the API had already passed the functional testing, why do we need this kind of test?“A feature works correctly doesn’t mean that it is a correct feature”. With this thinking, we found out that there are a lot more aspects that we need to cover before marking an API is Done:<ul><li>Response time: some systems require correctness and can be slow, but some require fast response instead.</li><li>Security: the API needs to match with security rules in the system, without exposing new security issues</li><li>Reliable: for the high load of usage, if needed.</li><li>And more.</li></ul>Each System will have its own DoD, but above are the core general items for API Testing. <h2>3. Benefits of good API Testing Plan/Strategy</h2>Everything will work, at least, when you have a good plan. But, having a good plan for API testing requires you to have enough knowledge of your system and a good mindset.The result of a good API testing plan are:<ul><li>Increase the speed of validating the API.</li><li>Collaboration between teams better (Team works on API and Team consumes API), without waiting for a long time to test.</li><li>Increase productivity of the whole team.</li><li>Easier to create the smoke test for the system, with the correct test case.</li><li>Easier to convert to an Automation test case without spending more effort on re-writing the test case</li><li>With good test case collections, changing the requirements is not a big deal because we always know where we need to change on our API test case.</li><li>Unleash the true power of the QA/QC team to try more on “how to make it better/quicker” instead of doing the same testing thing over and over again.</li></ul><h2>4. Best Practices</h2>To ensure that you are doing API Testing in the right way, here are some best practices that you can apply:<ol><li>Design the test case correctly to ensure coverage, by using all possible API input combinations.</li><li>Organize test cases by category.</li><li>Test the happy case with the expected result first. After that, test for the failure case.</li><li>For the Failure case, make sure the API and system fail gracefully.</li><li>Keep the test case as isolated as possible, by reducing the dynamic variables in the test case.</li><li>Prioritize the API call to test the API quickly, and for easier to do the smoke test on it.</li><li>To make the testing run smoothly, create a plan for the API/Testcase call sequence.</li><li>Do the Load Test on this API and on other APIs to see how well the system handles stressful situations.</li><li>Apply the Automation if possible, besides the Manual test.</li></ol><h2>5. Tools for API Testing</h2>Calling API is easier said than done. It requires a lot of skill to manually call the API directly. Fortunately, we have a lot of tools that help us to call and test the API with familiar user interfaces, like:<ul><li><a href="https://www.postman.com">Postman</a>: a tool for manual and automation API testing with an easy-to-use UI.</li><li><a href="https://www.soapui.org">SoapUI</a>: the ultimate tool for testing SOAP, REST API. Supported Web Service testing.</li><li><a href="https://jmeter.apache.org">JMeter</a>: a tool for load test API, that also supports functional tests.</li><li><a href="https://katalon.com">Katalon</a>: a tool for automation test the UI (E2E test), but still can be used to do the API test.</li></ul><h2>6. Conclusion</h2>API Testing allows developers to start testing early in the development cycle before the UI is ready. It helps to eliminate a lot of issues before the integration step happens and helps QA/QC access the thing that they can not explicitly access through the UI or through other services. Understanding API Testing is the crucial step in keeping your system more reliable and more stable, ensuring the success of our system in the future. </body></html>

Nowadays, API is not a new thing in software development, and in the software testing area, we called the process of testing API is “API Testing”. But do you want to go deep dive into what, why, and how API testing should work? If YES is the answer, go right into the post

&lt;html&gt;&lt;body&gt;&lt;h2&gt;&lt;span style=&quot;font-size:22px;&quot;&gt;1. What is API Testing?&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;First, we need to know about API. API stands for Application Programming Interface. That&rsquo;s all.&nbsp;Then, you may ask: what is its real meaning? So, let's go with Application Programming first.&nbsp;Application Programming usually has 3 layers: User Interface, Business Logic, and Data Storage.&nbsp;Did you notice it, the &ldquo;interface&rdquo; word? &ldquo;Interface&rdquo; here means something simple like &ldquo;A way that can be used to interact with something&rdquo;. User Interface means &ldquo;A way that User can use to interact with the Application&rdquo;.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;And the &ldquo;Application Programming Interface&rdquo; means: &ldquo;A way that Application Programming can use to interact with the Application/System &rdquo;. It is not for a specific User to use, just for the interaction between Machine to Machine, Service to Service or System to System, so we can call API is the middleware for the communication.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;With this information, let's go to &ldquo;&lt;strong&gt;What is API Testing?&lt;/strong&gt;&rdquo;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;API Testing is not only similar to other kinds of Software testing: to ensure that the API is matched with the expected behavior (functionality), but also to test the non-functional aspect of the API which can affect the entire system (performance, reliability, security).&nbsp;API Testing is the most crucial part of the software development life cycle, so no doubt that this is the most challenging part. But, it is just a piece of cake if you understand it clearly and have a good plan to do it. Let&rsquo;s see.&lt;/span&gt;&lt;/p&gt;&lt;h2&gt;&lt;span style=&quot;color:#000000;font-size:22px;&quot;&gt;2. Definition of Done for API Testing&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Most of the time, testing a single API can be done with 3 simple steps:&nbsp;&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Step 1: Send the request: to the targeted server URL with the desired parameter&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Step 2: Get the Response from the targeted server&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Step 3: Validate the Response: as expected from the test case&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;But as usual, we need to define the scope and the test case for API Testing first. So, to make sure that an API is tested thoroughly, we need to focus on the test case and the steps above, especially for step 3: Validate the Response.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;DoD for API Testing can be split into 2 parts:&lt;/span&gt;&lt;/p&gt;&lt;h3&gt;&lt;span style=&quot;color:#434343;font-size:13.999999999999998pt;&quot;&gt;Functional Testing:&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;First of all, we need to make sure the API works correctly and matches all the requirements. Things that can be listed are:&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;API is available to use&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Response codes are correct: for Failed or for Success case&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Response body output is correct: for the Success case&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;The error message is correct: for the Failed case&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Make sure that only the right person with the correct permission can use the API.&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;If the API passed these tests, we can say that the feature related to this issue will work correctly without any mismatch in the behavior.&lt;/span&gt;&lt;/p&gt;&lt;h3&gt;&lt;span style=&quot;color:#434343;font-size:13.999999999999998pt;&quot;&gt;Non-functional Testing:&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;If the API had already passed the functional testing, why do we need this kind of test?&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;&ldquo;A feature works correctly doesn&rsquo;t mean that it is a correct feature&rdquo;. With this thinking, we found out that there are a lot more aspects that we need to cover before marking an API is Done:&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Response time: some systems require correctness and can be slow, but some require fast response instead.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Security: the API needs to match with security rules in the system, without exposing new security issues&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Reliable: for the high load of usage, if needed.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;And more.&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Each System will have its own DoD, but above are the core general items for API Testing.&nbsp;&lt;/span&gt;&lt;/p&gt;&lt;h2&gt;&lt;span style=&quot;color:#000000;font-size:22px;&quot;&gt;3. Benefits of good API Testing Plan/Strategy&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Everything will work, at least, when you have a good plan. But, having a good plan for API testing requires you to have enough knowledge of your system and a good mindset.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;The result of a good API testing plan are:&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Increase the speed of validating the API.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Collaboration between teams better (Team works on API and Team consumes API), without waiting for a long time to test.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Increase productivity of the whole team.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Easier to create the smoke test for the system, with the correct test case.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Easier to convert to an Automation test case without spending more effort on re-writing the test case&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;With good test case collections, changing the requirements is not a big deal because we always know where we need to change on our API test case.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Unleash the true power of the QA/QC team to try more on &ldquo;how to make it better/quicker&rdquo; instead of doing the same testing thing over and over again.&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;h2&gt;&lt;span style=&quot;color:#000000;font-size:22px;&quot;&gt;4. Best Practices&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;To ensure that you are doing API Testing in the right way, here are some best practices that you can apply:&lt;/span&gt;&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Design the test case correctly to ensure coverage, by using all possible API input combinations.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Organize test cases by category.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Test the happy case with the expected result first. After that, test for the failure case.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;For the Failure case, make sure the API and system fail gracefully.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Keep the test case as isolated as possible, by reducing the dynamic variables in the test case.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Prioritize the API call to test the API quickly, and for easier to do the smoke test on it.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;To make the testing run smoothly, create a plan for the API/Testcase call sequence.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Do the Load Test on this API and on other APIs to see how well the system handles stressful situations.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Apply the Automation if possible, besides the Manual test.&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;&lt;h2&gt;&lt;span style=&quot;color:#000000;font-size:22px;&quot;&gt;5. Tools for API Testing&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;Calling API is easier said than done. It requires a lot of skill to manually call the API directly. Fortunately, we have a lot of tools that help us to call and test the API with familiar user interfaces, like:&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href=&quot;https://www.postman.com&quot;&gt;&lt;span style=&quot;color:#1155cc;font-size:11pt;&quot;&gt;&lt;u&gt;Postman&lt;/u&gt;&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;: a tool for manual and automation API testing with an easy-to-use UI.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://www.soapui.org&quot;&gt;&lt;span style=&quot;color:#1155cc;font-size:11pt;&quot;&gt;&lt;u&gt;SoapUI&lt;/u&gt;&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;: the ultimate tool for testing SOAP, REST API. Supported Web Service testing.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://jmeter.apache.org&quot;&gt;&lt;span style=&quot;color:#1155cc;font-size:11pt;&quot;&gt;&lt;u&gt;JMeter&lt;/u&gt;&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;: a tool for load test API, that also supports functional tests.&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://katalon.com&quot;&gt;&lt;span style=&quot;color:#1155cc;font-size:11pt;&quot;&gt;&lt;u&gt;Katalon&lt;/u&gt;&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;: a tool for automation test the UI (E2E test), but still can be used to do the API test.&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;h2&gt;&lt;span style=&quot;color:#000000;font-size:22px;&quot;&gt;6. Conclusion&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;span style=&quot;color:#000000;font-size:11pt;&quot;&gt;API Testing allows developers to start testing early in the development cycle before the UI is ready. It helps to eliminate a lot of issues before the integration step happens and helps QA/QC access the thing that they can not explicitly access through the UI or through other services. Understanding API Testing is the crucial step in keeping your system more reliable and more stable, ensuring the success of our system in the future.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&nbsp;&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;

API Testing in Software Development

API Testing

Senior Developer

Trung Tran

Senior AI Engineer

Phong Le

Business Analyst

Duong Dat Thanh

Middle Developer

Nguyễn Nhật Minh

Duy Le

Long Nguyen

In the previous section (part 2), I provided an overview of how to set up a working environment using Docker containers and build a Product Service. In this section (part 3), we will shift our focus to building Customer Service using .NET, Minimal API, and PostgreSQL.

Giới thiệu tổng quan về microservice, lợi ích khi xây dựng dự án sử dụng kiến trúc microservice, các nguyên lý khi xây dựng microservice, điểm mạnh điểm yếu của microservices, đồng thời giới thiệu series thực chiến xây dựng hệ thống microservices.

Tổng quan về Microservices (Phần 1)

Cài đặt môi trường làm việc cho dự án microservices với docker, xây dựng cấu trúc ban đầu cho dự án, triển khai logging và product service, containerize cho product.service.

Thực chiến xây dựng kiến trúc dự án Microservices và triển khai Product Service (phần 2)

Build Customer service (.NET, Minimal API, and PostgreSQL)

Microservices

If you have been writing c# for a while, you must have used String (string and String can be used interchangeably because string is just an alias of String) and StringBuilder class for sure. However, underneath the simple ‘+’ operator is a huge amount of work which was designed for good intention but also could degrade performance drastically if used naively. The StringBuilder class  was crafted in order to overcome one of those problems. Do you know what these problems are and what was resolved? 
Let’s find out in this post!

How string works in c#

<html><body><h2 style="text-align:justify;">1. Cải thiện tốc độ tải trang đi cùng với  3 “Tăng”</h2><h3 style="text-align:justify;">Tăng trải nghiệm người dùng</h3>Nếu so sánh giữa sàn S và sàn L, dù sàn L có nhiều chương trình khuyến mãi hơn, nhưng khảo sát cho thấy số người sử dụng sàn S vẫn chiếm ưu thế. Lý do chính là do giao diện website của sàn S được thiết kế dễ sử dụng, tốc độ truy cập nhanh và có tính linh hoạt. Điều này cho thấy rằng việc tập trung vào trải nghiệm người dùng là rất quan trọng trong việc xây dựng một website.Hiện nay, việc trải nghiệm người dùng là một yếu tố cực kỳ quan trọng trong lĩnh vực thiết kế website. Khách hàng không muốn phải chờ đợi quá lâu để có thể xem được nội dung hoàn chỉnh của một trang web. Trong thời đại kỹ thuật số, người dùng có rất nhiều sự lựa chọn, và họ khó có thể chấp nhận trang web chậm hoặc không có trải nghiệm tốt. Do đó, tập trung vào trải nghiệm người dùng là một yếu tố quan trọng để xây dựng một trang web thành công. Nếu một trang web được thiết kế mà không tập trung vào trải nghiệm người dùng, nó sẽ khó có thể phát triển được và khách hàng sẽ không quay lại. Vì vậy, việc tập trung vào tối ưu hóa trang web để có trải nghiệm người dùng tốt là cần thiết và không thể bỏ qua. <h3 style="text-align:justify;">Tăng thứ hạng website</h3>Tốc độ tải trang chậm là một trong những nguyên nhân dẫn đến việc website của bạn có xếp hạng thấp hơn so với các trang web của đối thủ trên các công cụ tìm kiếm. Khi truy cập vào một trang web, người dùng thường không kiên nhẫn và sẵn sàng bấm nút "Quay lại trang tìm kiếm" để xem một trang web khác nếu trang web hiện tại tải quá chậm. Điều này sẽ làm cho Google đánh giá trang web này không có ích cho người dùng, dẫn đến việc xếp hạng của trang web bị giảm. Ngoài ra, tốc độ tải trang chậm cũng ảnh hưởng đến điểm số của trang web trên PageSpeed Insights, do đó việc đạt được xếp hạng cao là điều khó khăn. <h3 style="text-align:justify;">Tăng lợi ích của chủ sở hữu website</h3>Tốc độ tải trang web chậm không chỉ làm giảm trải nghiệm của người dùng mà còn ảnh hưởng đến thứ hạng của website trên các công cụ tìm kiếm. Điều này dẫn đến việc website không tương tác, kinh doanh không thuận lợi và thương hiệu ít tiếp cận được với khách hàng. Vì vậy, để đạt được hiệu quả kinh doanh tốt, việc sở hữu một website mượt mà là rất cần thiết. Có thể thấy rằng WP Rocket giải quyết hầu hết các vấn đề được đặt ra bởi PageSpeed Insights một cách dễ dàng, giúp website dễ tiếp cận với người dùng hơn. Do đó, chủ sở hữu website có thể giải quyết các vấn đề trước đó để website đạt được "3 Tăng": tăng trải nghiệm người dùng, tăng thứ hạng của website và tăng lợi ích cho chủ sở hữu website. <h2 style="text-align:justify;">2. WP Rocket là gì</h2>WP Rocket là một trong những plugin cache hiệu quả nhất cho WordPress. Không chỉ giúp tăng tốc độ trang web, WP Rocket còn giải quyết hầu hết các vấn đề được đưa ra bởi PageSpeed Insights. Việc cài đặt và cấu hình WP Rocket cũng rất đơn giản. Vì những lý do này, WP Rocket xứng đáng là một trong những plugin cache hàng đầu mà bạn nên thử sử dụng. <h2 style="text-align:justify;">3. Tính năng nổi bật của WP Rocket</h2>Sau đây mình sẽ đi qua một số tính năng mà mình đã dùng và thấy nổi bật của WP Rocket, ngoài những tính năng nổi bật này, bạn còn có thể tìm hiểu nhiều thêm nữa ở phần Tutorial của chính plugin này sau khi cài đặt, hoặc ở website chính thức của plugin này nhé!<h3 style="text-align:justify;">Cache</h3>Cache - hay còn được gọi là bộ nhớ đệm - là một khu vực lưu trữ dữ liệu tạm thời trên một thiết bị. Khi được sử dụng đúng cách, tính năng cache có thể giúp tăng tốc độ tải trang và giảm tải cho máy chủ.<ul><li>Để kích hoạt tính năng cache cho thiết bị di động hoặc người dùng đã đăng nhập vào trang web WordPress, bạn có thể chọn Enable caching for mobile devices hoặc Enable caching for logged-in WordPress users.</li><li>Ngoài ra, bạn cũng có thể thiết lập tự động xóa toàn bộ cache trang web trong một khoảng thời gian nhất định bằng cách nhập giá trị vào ô Specify time after which the global cache is cleared (0 = unlimited). Nếu bạn nhập giá trị bằng 0 thì tính năng này sẽ bị tắt.</li></ul> <img src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-B0iBOyq5I5w69rVD5l3tQywRW66zURwaNVMjRURJ.png"> <h3 style="text-align:justify;">File Optimization</h3>Ở bước này, bạn có thể thoải mái kiểm thử các tính năng trong tab. Nếu website xuất hiện lỗi giao diện, chỉ cần tắt tính năng mà bạn vừa kích hoạt và xóa cache đi là mọi thứ sẽ trở về như cũ.Sau đây một số tính năng hữu ích:<ul><li>Nén file css và file js: Tính năng Minify CSS/JS files giúp tự động nén các file css và js giúp giảm thời gian tải trang.</li><li>Gộp file css và file js: Tính năng Combine CSS/JS files giúp gộp chung các file CSS/JS lại thành một. Lưu ý tính năng này không nên bật nếu trang web của bạn có hỗ trợ HTTP/2. Ngoài ra, còn có Excluded CSS/JS Files giúp người dùng có thể loại trừ được những files CSS và JS mà họ không muốn gộp khi sử dụng tính năng Combine CSS/JS files.</li><li>Trì hoãn tải tệp JavaScript: Tính năng Delay JavaScript execution giúp trì hoãn tải tệp JavaScript cho đến khi người dùng tương tác (cuộn, nhấp,...) trên trang web từ đó cải thiện hiệu suất đáng kể. Ngoài ra, còn có tùy chọn Excluded JavaScript Files để người dùng có thể chỉ định các URL hoặc từ khóa của tệp JavaScript không cần phải trì hoãn khi sử dụng tính năng Delay JavaScript execution.</li></ul><img src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-gFnekDuPk9jZX6XJk6WpV7MUafo5LYKA2aCZ4zz5.png"> <h3 style="text-align:justify;">Media</h3><ul><li>Tính năng lazyload cho ảnh, iframes và video</li></ul>Tính năng Enable for images/iframes and videos giúp giảm thời gian tải trang bằng cách sử dụng lazy load cho ảnh, iframe và video.Replace YouTube iframe with preview image giúp cải thiện tốc độ tải trang đáng kể cho các trang web chứa nhiều video YouTube bằng cách thay thế khung phát trực tiếp YouTube bằng các hình ảnh xem trước. <img src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-WC95jfIOIqEPVvts8sjBssTwvEHe1V8eoEl87KzQ.png"> <h3 style="text-align:justify;">Tools</h3><ul><li>Import/Export cài đặt</li></ul>Tính năng Import/Export settings giúp bạn dễ dàng sao chép cài đặt từ một trang web sang một trang khác. Điều này tiết kiệm thời gian và công sức nếu bạn cần áp dụng các cài đặt tương tự cho nhiều trang web khác nhau.<img src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-9ovdESbv7qeYg4ymlGLk6KoNj81mw3C4X3LP7cxO.png"> <h3 style="text-align:justify;">Tutorials</h3>Đối với những ai đang tìm kiếm một giải pháp để tối ưu hóa trang web của mình, WP Rocket có thể là một lựa chọn tuyệt vời. Điều đặc biệt về WP Rocket là tính năng giúp tiết kiệm thời gian đáng kể trong việc tìm hiểu cách tối ưu hóa trang web. Bên cạnh đó, WP Rocket cung cấp các video hướng dẫn và demo chi tiết để người dùng có thể dễ dàng thực hiện cài đặt và tối ưu hóa trang web của mình.<img src="https://api.careers.saigontechnology.com/storage/ck-editor/CKEDITOR-hLj5Ays8zFFJrq2689J2VhapOLpdifs9A2UXdCB4.png"> <h2 style="text-align:justify;">4. Ưu nhược điểm của WP Rocket</h2><ul><li>Ưu điểm:<ul><li>Hỗ trợ tối ưu hóa website một cách nhanh chóng và hiệu quả: WP Rocket có khả năng giúp bạn khắc phục các lỗi mà PageSpeed Insights phát hiện một cách đơn giản và dễ dàng.</li><li>Sử dụng đơn giản: Bạn không cần phải là một chuyên gia về mã lệnh để có thể sử dụng plugin này.</li><li>Hỗ trợ liên kết với nhiều Add-on: WP Rocket có khả năng liên kết và hỗ trợ các Add-on khác để giúp bạn theo dõi website của mình dễ dàng hơn.</li></ul></li><li>Nhược điểm</li><li>Phí dịch vụ: WP Rocket là một dịch vụ trả phí.</li><li>Không hỗ trợ hình ảnh dạng .webp: WP Rocket không hỗ trợ tối ưu hóa hình ảnh dạng .webp.</li><li>Chỉ hỗ trợ cho website Wordpress: WP Rocket chỉ hỗ trợ cho website được xây dựng trên nền tảng Wordpress.</li></ul> <h2 style="text-align:justify;">5. Kết luận</h2>WP Rocket là một công cụ caching rất hữu ích để cải thiện tốc độ website của bạn. Nó được thiết kế để giảm thời gian tải trang bằng cách lưu trữ các phiên bản trang web đã được tạo trước đó và phục vụ chúng cho những người truy cập sau đó.Tuy nhiên, trong quá trình sử dụng WP Rocket, cần lưu ý một số điểm quan trọng để tránh lỗi và đạt được kết quả tốt nhất cho website của mình. Theo như đã ghi chú ở trên, có vài điều kiện cần phải tuân thủ:<ul><li>Cần phải cài đặt WP Rocket trên một website đã được cập nhật lên phiên bản mới nhất của Wordpress.</li><li>Nên sử dụng WP Rocket trên một website đã được cài đặt HTTPS để đảm bảo an toàn cho người dùng.</li><li>Nên sử dụng WP Rocket trên một website đã được cài đặt SSL để đảm bảo an toàn cho người dùng.</li><li>Không nên sử dụng WP Rocket trên một website đã sử dụng plugin caching khác, vì điều này có thể gây ra xung đột và làm cho website của bạn phát sinh lỗi hoặc hoạt động chậm hơn.</li></ul>Hy vọng những thông tin trên sẽ giúp bạn sử dụng WP Rocket hiệu quả hơn và cải thiện tốc độ website Wordpress của riêng mình. </body></html>

Trong thời đại số hóa hiện nay, website là công cụ quan trọng để quảng bá hình ảnh công ty. Tuy nhiên, việc website có tốc độ chậm sẽ làm giảm trải nghiệm người dùng và ảnh hưởng tới hiệu quả kinh doanh của doanh nghiệp. Với WP Rocket, doanh nghiệp có thể mang đến cho người dùng trải nghiệm tốt hơn.

Blog where we tell stories and share IT knowledge