Scribd
Upload
6 views3 pages

Agile testing

The document outlines the fundamentals of Agile Software Development, emphasizing the Agile Manifesto's values such as prioritizing individuals and interactions, working software, customer collaboration, and responding to change. It details Agile principles, the benefits of a whole-team approach, and the importance of collaboration among testers, developers, and business representatives. Additionally, it introduces Agile testing methods and techniques for assessing quality risks and estimating test effort.

Uploaded by

mohammed jafri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views3 pages

Agile testing

The document outlines the fundamentals of Agile Software Development, emphasizing the Agile Manifesto's values such as prioritizing individuals and interactions, working software, customer collaboration, and responding to change. It details Agile principles, the benefits of a whole-team approach, and the importance of collaboration among testers, developers, and business representatives. Additionally, it introduces Agile testing methods and techniques for assessing quality risks and estimating test effort.

Uploaded by

mohammed jafri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

1 Agile Software Development

3 1.1 The Fundamentals of Agile Software Development


4
5 1.1.1 Agile values/Manifesto
6
7  Individuals and interactions over processes and tools
8  Working software over comprehensive documentation
9  Customer collaboration over contract negotiation
10  Responding to change over following a plan
11
12 Note: The Agile Manifesto argues that although the concepts on the right have value, those on the left have greater value.
13
14 1.1.2 Delivering a working software benefit:
15  significant time-to-market advantage
16  provides an opportunity to give the development team rapid feedback
17  working software is much more useful and valuable than overly detailed documentation to the customer
18  beneficial when the business wishes to innovate in new problem domains
19  working software is beneficial in rapidly changing business environments where the problems and solutions are
20 unclear
21
22 1.1.3 Customer Collaboration benefit:
23  Direct customer collaboration improves the understanding of the customer requirements
24
25 1.1.4 Responding to Change benefit:
26  having flexibility in work practices to embrace change is more important than simply adhering rigidly to a plan.
27
28 1.2 Agile Principles:
29 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
30 2. Welcome changing requirements, even late in development.
31 3. Deliver working software frequently, at intervals of between a few weeks to a few months.
32 4. Business people and developers must work together daily throughout the project.
33 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them.
34 6. The most efficient and effective method of conveying information is face-to-face conversation.
35 7. Working software is the primary measure of progress.
36 8. Agile processes promote sustainable development. Agile team should be able to maintain a constant pace indefinitely
37 9. Continuous attention to technical excellence and good design enhances agility.
38 10. Simplicity—the art of maximizing the amount of work not done—is essential.
39 11. The best architectures, requirements, and designs emerge from self-organizing teams.
40 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior
41 accordingly.
42
43 1.3 Whole-Team Approach: The whole-team approach means involving everyone with the knowledge and skills necessary to
44 ensure project success.

45 The team creation guide line:

46 1. The team should be relatively small; successful teams have been observed with as few as three people and as many as nine.
47 2. the whole team shares the same workspace.

48

49
50 The benefits of a whole-team approach include:
51 1. Enhancing communication and collaboration within the team
52 2. Enabling the various skill sets within the team to be leveraged to the benefit of the project
53 3. Making quality everyone’s responsibility

54 Testers will work closely with both developers and business representatives to ensure that the desired quality levels are
55 achieved. This include:
56 1. supporting and collaborating with business representatives to help them create suitable acceptance tests
57 2. working with developers to agree on the testing strategy
58 3. deciding on test automation approaches
59 4. transfer and extend testing knowledge to other team members and influence the development of the product

60 The power of three: The concept of involving testers, developers, and business representatives in all feature discussions is
61 known as the power of three.

62

63

64

65

66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99 Chapter 3
100 1. Agile Testing Methods:
101
102 1.1. test-driven development

103

104

105 1.2. acceptance test-driven


106

107

108 1.3. behavior-driven development

109

110

111 2. the test pyramids:

112

113 3. the testing quadrants and their relationships with testing levels and testing types:
114
115

116 FA-3.1.4 (K3) For a given Agile project, practice the role of a tester in a Scrum team
117 3.2 Assessing Quality Risks and Estimating Test Effort
118 FA-3.2.1 (K3) Assess quality risks within an Agile project
119 FA-3.2.2 (K3) Estimate testing effort based on iteration content and quality risks
120 3.3 Techniques in Agile Projects
121 FA-3.3.1 (K3) Interpret relevant information to support testing activities
122 FA-3.3.2 (K2) Explain to business stakeholders how to define testable acceptance criteria
123 FA-3.3.3 (K3) Given a user story, write acceptance test-driven development test cases
124 FA-3.3.4 (K3) For both functional and non-functional behavior, write test cases using black box
125 test design techniques based on given user stories
126 FA-3.3.5 (K3) Perform exploratory testing to support the testing of an Agile project
127 3.4 Tools in Agile Projects
128 FA-3.4.1 (K1) Recall different tools available to testers according to their purpose and to
129 activities in Agile projects

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy