Today's article we will learn how the Agile model and software testing methods when using the Agile model will be effective.<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_d594cb3868.png"><h2>1. What is Agile?</h2><ul><li>Agile is an agile software development methodology that focuses on product development in the form of short cycles called "sprints". Agile aims to maximize product value and minimize risks by focusing on adaptability to change and rapid customer response.</li><li>Agile is often applied in software projects but can also be applied in many other areas, from production to marketing and project management.</li></ul><h2>2. Agile criteria:</h2><ul><li>Interaction between people rather than process and tools: Agile focus on interaction and communication among team members first. Regular communication between customers, product managers, and development team members helps ensure a shared understanding of product requirements and helps make decisions faster and more efficient.</li><li>Active software rather than detailed documentation: Agile focuses on developing software that can work instead of detailed documentation. Creating working software versions early makes it possible for customers and development teams to evaluate and provide feedback, thereby optimizing product value.</li><li>Collaborating with customers rather than negotiating contracts: Agile sees customers as part of the product development process. Partnering with customers helps ensure that products are developed that meet actual requirements and respond to customers' changing needs.</li><li>Adaptability to change rather than to a blueprint: Agile allows for changes and adjustments during product development. Rapid adaptation helps ensure that the product can meet new requirements and solve problems that arise during development.</li></ul><h2>3. Rules in Agile:</h2><ul><li>The first priority is to create customer satisfaction by providing valuable products.</li><li>Accept change, even late in the development process. Agile makes the software development process more flexible in terms of changing customer requirements.</li><li>Delivering operational and valuable software products to customers in a short time, by breaking down software products into small pieces and developing them simultaneously.</li><li>Software development team members should cooperate closely to achieve the common goal of the project.</li><li>Build projects around people who contribute directly to the project.</li><li>Create a positive working environment that supports creativity and continuous improvement.</li><li>Focus on providing software products that work according to customer requirements.</li><li>Ensure that the members of the software development team all contribute to the development process and are accountable for the results.</li><li>Adjust the software development process continuously, through periodic evaluation and improvement.</li><li>Use simple and effective methods for software development.</li><li>Encourage direct interaction between members of the software development team.</li><li>Create software products that are sustainable and can adapt to future changes.</li></ul><h2>4. Software testing process in Agile model</h2>a. The software testing phases correspond to the software development phases in the Agile model<ul><li>Planning phase: Test plans are programmed to ensure that customer requirements are fully met. Test plans include functional test plans, performance tests and integration test plans.</li><li>Design phase: Test scenarios are created and test cases are designed. These scenarios are used to ensure that the customer requirements are fully met and that the functionality of the software is tested.</li><li>Development phase: Test cases are executed in parallel with other development steps of the software. Test cases are used to ensure that the software works properly and fully.</li><li>Integration testing phase: Test cases are performed to ensure that the software works properly when integrated with other components of the system.</li><li>Acceptance testing phase: Customer or end user is required to test the product to ensure that it meets their requirements. Acceptance test cases are used to ensure that the software is accepted by the customer.</li></ul>b. Quality assurance activities in segments<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_fde1d78893.png" alt="image.png" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_image_fde1d78893.png 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_image_fde1d78893.png 500w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_image_fde1d78893.png 750w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/large_image_fde1d78893.png 1000w," sizes="100vw"><ul><li>Requirement definition segment: Customer requirements are defined and ensured that they can be measured and achieved. QA needs to constantly interact with customers to understand their requirements and ensure that the software developed meets these requirements.</li><li>Design segment: QA participates in the architectural design of the software. QA will check if the design meets the quality requirements and company standards. If necessary, QA will make suggestions to improve the design.</li><li>Development segment: QA participates in the software development process. QA ensures that the software developed meets the requirements and set quality standards. QA will conduct product testing to ensure that the developed software meets the quality requirements.</li><li>Testing Segment: QA performs software testing. Types of testing include unit testing, integration testing, system testing, and acceptance testing. The results of the testing activities will be used to improve the software.</li><li>Deployment segment: QA ensures that the software is properly deployed and meets the quality standards. QA will check that the implemented system has met the quality requirements and will make suggestions to improve the product in the future.</li></ul> &nbsp;

Agile is an agile software development methodology that focuses on product development in the form of short cycles called "sprints". Agile aims to maximize product value and minimize risks by focusing on adaptability to change and rapid customer response.

What is Agile Model in Software Testing?

What is User Story?
<ul>
<li>As a user, I can view the comments side of individual posts.</li>
<li>As a user, I can edit my personal information.</li>
<li>As a user, I can view the product list.</li>
</ul>
Above are a few examples of user stories. So user stories are often a feature that users can use on the products or projects you make for them. Experience when creating User stories, often try to generate User stories as small as possible.
Example for a bad User story:
<ul>
<li>As a user, I want to make a purchase.</li>
</ul>
We can see that the User story above is too general and covers the buying process. So instead, we should create small User stories as follows:
<ul>
<li>As a user, I want to search for tank tops with keywords.</li>
<li>As a user, I would like to see the list of tank tops.</li>
<li>As a user, I can customize the text on the shirt I’m viewing.</li>
<li>As a user, I can add a shirt to the cart.</li>
<li>As a user, I can conduct checkout.</li>
</ul>
But it is not always possible to create an optimal User story right from the start when the project has just started, and you do not have too much information to make an accurate User story. However, we still have to start planning with high-level tasks/user stories. Or, We cannot make the user story smaller / more detailed.
When we have to subdivide that User story into a subtask, so when dividing, there will be two ways:
<ul>
<li>Horizontal slice
<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/pexels_photo_5696573_661dab1951.jpeg" alt="pexels-photo-5696573.jpeg" /></li>
<li>Vertical slice
<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/pexels_photo_5848119_65ae23822f.jpeg" alt="pexels-photo-5848119.jpeg" /></li>
</ul>
Looking back at the post’s feature image, you can see that the cake is cut vertically. The cake contains many layers. When slicing the birthday cake, you don’t cut it across; you slice it lengthwise. Thus, considering a User story is a whole cake, then Horizontal slice: is to cut the cake by layer, one portion has only one layer, and Vertical slice: is to cut the cake in the usual way, a piece of cake will include all layers.
So what are the advantages of Vertical slice? Talking about the cake, a person who enjoys the longitudinal portion will enjoy the cake’s full flavor, regardless of whether it is big or small. Talking about the User story, when broken down by vertical slice, a subtask is created that will cover all the technical aspects needed to complete that subtask: UI / UX, Database, Backend API, Frontend, etc., so that subtask, when completed, will demo the user, and QA can perform testing efficiently.
In contrast, when dividing User stories by Horizontal slice, a task is just for Database, a task just for UI, a task just for Frontend development. When a task is done, there is almost no way for QA to test that task if they don’t have specialized knowledge about that task (for example, how can the QA test database be designed appropriately?). Horizontal slice has one advantage, I find it easy to create. But it’s challenging about testing, demonstrating later. In short, should divide the cake by slicing vertically, or dividing a User story by vertical slicing will be better for QA, showcase, demo later.
Reference: www.visual-paradigm.com<div id="md2html-converted" style="display:none"></div>

What is User Story?

As a user, I can view the comments side of individual posts.
As a user, I can edit my personal information.
As a user, I can view the product list.

Agile

Contact Us