<html><body><h2 style="text-align:justify;">I- 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>II- 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;">III- 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>IV- 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;">V- 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.

The Basic Concepts Of Performance Test - Time Behavior

Performance Test

<html><body><h2>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>Definition of Done for API Testing</h2>Most of the time, testing a single API can be done with 3 simple steps: <ul><li style="list-style-type:disc;">Step 1: Send the request: to the targeted server URL with the desired parameter</li><li style="list-style-type:disc;">Step 2: Get the Response from the targeted server</li><li style="list-style-type:disc;">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>1) 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 style="list-style-type:disc;">API is available to use</li><li style="list-style-type:disc;">Response codes are correct: for Failed or for Success case</li><li style="list-style-type:disc;">Response body output is correct: for the Success case</li><li style="list-style-type:disc;">The error message is correct: for the Failed case</li><li style="list-style-type:disc;">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>2) 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 style="list-style-type:disc;">Response time: some systems require correctness and can be slow, but some require fast response instead.</li><li style="list-style-type:disc;">Security: the API needs to match with security rules in the system, without exposing new security issues</li><li style="list-style-type:disc;">Reliable: for the high load of usage, if needed.</li><li style="list-style-type:disc;">And more.</li></ul>Each System will have its own DoD, but above are the core general items for API Testing. <h2> </h2><h2>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 style="list-style-type:disc;">Increase the speed of validating the API.</li><li style="list-style-type:disc;">Collaboration between teams better (Team works on API and Team consumes API), without waiting for a long time to test.</li><li style="list-style-type:disc;">Increase productivity of the whole team.</li><li style="list-style-type:disc;">Easier to create the smoke test for the system, with the correct test case.</li><li style="list-style-type:disc;">Easier to convert to an Automation test case without spending more effort on re-writing the test case</li><li style="list-style-type:disc;">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 style="list-style-type:disc;">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> </h2><h2>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 style="list-style-type:decimal;">Design the test case correctly to ensure coverage, by using all possible API input combinations.</li><li style="list-style-type:decimal;">Organize test cases by category.</li><li style="list-style-type:decimal;">Test the happy case with the expected result first. After that, test for the failure case.</li><li style="list-style-type:decimal;">For the Failure case, make sure the API and system fail gracefully.</li><li style="list-style-type:decimal;">Keep the test case as isolated as possible, by reducing the dynamic variables in the test case.</li><li style="list-style-type:decimal;">Prioritize the API call to test the API quickly, and for easier to do the smoke test on it.</li><li style="list-style-type:decimal;">To make the testing run smoothly, create a plan for the API/Testcase call sequence.</li><li style="list-style-type:decimal;">Do the Load Test on this API and on other APIs to see how well the system handles stressful situations.</li><li style="list-style-type:decimal;">Apply the Automation if possible, besides the Manual test.</li></ol><h2> </h2><h2>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 style="list-style-type:disc;"><a style="text-decoration:none;" href="https://www.postman.com">Postman</a>: a tool for manual and automation API testing with an easy-to-use UI.</li><li style="list-style-type:disc;"><a style="text-decoration:none;" href="https://www.soapui.org">SoapUI</a>: the ultimate tool for testing SOAP, REST API. Supported Web Service testing.</li><li style="list-style-type:disc;"><a style="text-decoration:none;" href="https://jmeter.apache.org">JMeter</a>: a tool for load test API, that also supports functional tests.</li><li style="list-style-type:disc;"><a style="text-decoration:none;" 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> </h2><h2>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

API Testing in Software Development

API Testing

Senior Developer

Trung Tran

Senior AI Engineer

Phong Le

Duy Le

Long Nguyen

Middle Developer

Nguyễn Nhật Minh

Tung Hoang

Are you facing problems with data consistency in a highly concurrent environment? Are you looking for a way to limit and synchronize access to a shared resource across services in a distributed system? Let's see how a distributed lock can help in this situation.

Implement Distributed Lock For a Microservices Software System

The AI, Machine Learning, and Deep Learning definition are becoming viral recently. Let's see how we could apply them to address our problems in the real world, especially in the Computer Vision field for the Image Classification task.

Build Deep Learning model for the Image Classification task (Part1): Pytorch model

Build a Deep Learning model for the Image Classification task in a simple way

Many individuals wish to build their own 3D website but may feel unsure of where to begin and have the confidence it would run smoothly. If you’re searching for a way to build 3d websites as a developer then this article will 100% help you.

Apply 3d content on a webpage using three.js library

Do you know Web 3.0? Have you ever listened to some keywords like Blockchain, Tokens, Smart Contracts, Block, Semantic website and do not really understand them? You want to deeply understand Web 3.0 and its application architecture. Let me explain for you in this blog.

Blog where we tell stories and share IT knowledge