What changes for testers when they are testing in agile environments?
We know that the whole development team is responsible for the quality of the product. If only the testers test, there can be no question of shared responsibility. Of course, the testers in the team still need the ability to add value in their specialty. They bring with them valuable knowledge and skills. Nevertheless, all team members can and should contribute to the quality of the product, for example:
- Developers can decompose the software into small, independently
testable components. - Developers can help automate test cases.
- With their experience and know-how, testers can alert developers to
potential program vulnerabilities or perform risk analysis. So
that it is ensured at an early stage that some errors do not even
occur. - All team members can and should work with the user to ensure early on
that the right thing is being developed.
automated-testing manual-testing test-management test-design scrum
edited 2 days ago
Michael Durrant
14.5k22165
asked 2 days ago
MornonMornon
1168
add a comment |
We know that the whole development team is responsible for the quality of the product. If only the testers test, there can be no question of shared responsibility. Of course, the testers in the team still need the ability to add value in their specialty. They bring with them valuable knowledge and skills. Nevertheless, all team members can and should contribute to the quality of the product, for example:
- Developers can decompose the software into small, independently
testable components. - Developers can help automate test cases.
- With their experience and know-how, testers can alert developers to
potential program vulnerabilities or perform risk analysis. So
that it is ensured at an early stage that some errors do not even
occur. - All team members can and should work with the user to ensure early on
that the right thing is being developed.
automated-testing manual-testing test-management test-design scrum
edited 2 days ago
Michael Durrant
14.5k22165
asked 2 days ago
MornonMornon
1168
2
Sorry, I'm not sure what the question is here.
– Daniel
2 days ago
1
Maybe the question is "What changes for testers when they are testing in agile environments?" and details say 'how do they bring in their particular experience?'
– Michael Durrant
2 days ago
"What changes for testers when they are testing in agile environments?" is correct
– Mornon
2 days ago
add a comment |
We know that the whole development team is responsible for the quality of the product. If only the testers test, there can be no question of shared responsibility. Of course, the testers in the team still need the ability to add value in their specialty. They bring with them valuable knowledge and skills. Nevertheless, all team members can and should contribute to the quality of the product, for example:
- Developers can decompose the software into small, independently
testable components. - Developers can help automate test cases.
- With their experience and know-how, testers can alert developers to
potential program vulnerabilities or perform risk analysis. So
that it is ensured at an early stage that some errors do not even
occur. - All team members can and should work with the user to ensure early on
that the right thing is being developed.
automated-testing manual-testing test-management test-design scrum
edited 2 days ago
Michael Durrant
14.5k22165
asked 2 days ago
MornonMornon
1168
We know that the whole development team is responsible for the quality of the product. If only the testers test, there can be no question of shared responsibility. Of course, the testers in the team still need the ability to add value in their specialty. They bring with them valuable knowledge and skills. Nevertheless, all team members can and should contribute to the quality of the product, for example:
- Developers can decompose the software into small, independently
testable components. - Developers can help automate test cases.
- With their experience and know-how, testers can alert developers to
potential program vulnerabilities or perform risk analysis. So
that it is ensured at an early stage that some errors do not even
occur. - All team members can and should work with the user to ensure early on
that the right thing is being developed.
automated-testing manual-testing test-management test-design scrum
automated-testing manual-testing test-management test-design scrum
edited 2 days ago
Michael Durrant
14.5k22165
asked 2 days ago
MornonMornon
1168
edited 2 days ago
Michael Durrant
14.5k22165
asked 2 days ago
MornonMornon
1168
edited 2 days ago
Michael Durrant
14.5k22165
edited 2 days ago
Michael Durrant
14.5k22165
edited 2 days ago
Michael Durrant
14.5k22165
14.5k22165
asked 2 days ago
MornonMornon
1168
asked 2 days ago
MornonMornon
1168
asked 2 days ago
MornonMornon
1168
1168
2
Sorry, I'm not sure what the question is here.
– Daniel
2 days ago
1
Maybe the question is "What changes for testers when they are testing in agile environments?" and details say 'how do they bring in their particular experience?'
– Michael Durrant
2 days ago
"What changes for testers when they are testing in agile environments?" is correct
– Mornon
2 days ago
add a comment |
2
Sorry, I'm not sure what the question is here.
– Daniel
2 days ago
1
Maybe the question is "What changes for testers when they are testing in agile environments?" and details say 'how do they bring in their particular experience?'
– Michael Durrant
2 days ago
"What changes for testers when they are testing in agile environments?" is correct
– Mornon
2 days ago
2
2
Sorry, I'm not sure what the question is here.
– Daniel
2 days ago
Sorry, I'm not sure what the question is here.
– Daniel
2 days ago
1
1
Maybe the question is "What changes for testers when they are testing in agile environments?" and details say 'how do they bring in their particular experience?'
– Michael Durrant
2 days ago
Maybe the question is "What changes for testers when they are testing in agile environments?" and details say 'how do they bring in their particular experience?'
– Michael Durrant
2 days ago
"What changes for testers when they are testing in agile environments?" is correct
– Mornon
2 days ago
"What changes for testers when they are testing in agile environments?" is correct
– Mornon
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
Classic testing is Quality Assurance
Agile Testing is Quality Engineering
Quality Assurance
Traditionally most testing as done at the end of the development. It asks if the product that has been developed meets the requirements, both explicit and implicit.
Quality Engineering
This field is primarily concerned about automation and automated tests.
It breaks out testing into:
Unit testing
Integrated Testing
Automated UI
Exploratory, Performance & Security
Over time this leads to the following situations:
Classic Testing - the product is built, the developer considers it is working but Quality Assurance has to convince them and others when there are issues. Issues are frequently found late in the process with little time for quality fixes. Fixes are expensive and often affect production. This is common in Command and Control and Waterfall environments.
Agile Testing - the goal is to shift testing left and test as early as possible. Ideally many tests are written first and fail without the application code to support them. Most tests are unit tests written by developers to ensure components work. This makes them executable specifications and when the application code is written that makes them pass, then you are good to go.
edited 2 days ago
João Farias
3,021415
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "244"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsqa.stackexchange.com%2fquestions%2f38391%2fwhat-changes-for-testers-when-they-are-testing-in-agile-environments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Classic testing is Quality Assurance
Agile Testing is Quality Engineering
Quality Assurance
Traditionally most testing as done at the end of the development. It asks if the product that has been developed meets the requirements, both explicit and implicit.
Quality Engineering
This field is primarily concerned about automation and automated tests.
It breaks out testing into:
Unit testing
Integrated Testing
Automated UI
Exploratory, Performance & Security
Over time this leads to the following situations:
Classic Testing - the product is built, the developer considers it is working but Quality Assurance has to convince them and others when there are issues. Issues are frequently found late in the process with little time for quality fixes. Fixes are expensive and often affect production. This is common in Command and Control and Waterfall environments.
Agile Testing - the goal is to shift testing left and test as early as possible. Ideally many tests are written first and fail without the application code to support them. Most tests are unit tests written by developers to ensure components work. This makes them executable specifications and when the application code is written that makes them pass, then you are good to go.
edited 2 days ago
João Farias
3,021415
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
add a comment |
Classic testing is Quality Assurance
Agile Testing is Quality Engineering
Quality Assurance
Traditionally most testing as done at the end of the development. It asks if the product that has been developed meets the requirements, both explicit and implicit.
Quality Engineering
This field is primarily concerned about automation and automated tests.
It breaks out testing into:
Unit testing
Integrated Testing
Automated UI
Exploratory, Performance & Security
Over time this leads to the following situations:
Classic Testing - the product is built, the developer considers it is working but Quality Assurance has to convince them and others when there are issues. Issues are frequently found late in the process with little time for quality fixes. Fixes are expensive and often affect production. This is common in Command and Control and Waterfall environments.
Agile Testing - the goal is to shift testing left and test as early as possible. Ideally many tests are written first and fail without the application code to support them. Most tests are unit tests written by developers to ensure components work. This makes them executable specifications and when the application code is written that makes them pass, then you are good to go.
edited 2 days ago
João Farias
3,021415
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
add a comment |
Classic testing is Quality Assurance
Agile Testing is Quality Engineering
Quality Assurance
Traditionally most testing as done at the end of the development. It asks if the product that has been developed meets the requirements, both explicit and implicit.
Quality Engineering
This field is primarily concerned about automation and automated tests.
It breaks out testing into:
Unit testing
Integrated Testing
Automated UI
Exploratory, Performance & Security
Over time this leads to the following situations:
Classic Testing - the product is built, the developer considers it is working but Quality Assurance has to convince them and others when there are issues. Issues are frequently found late in the process with little time for quality fixes. Fixes are expensive and often affect production. This is common in Command and Control and Waterfall environments.
Agile Testing - the goal is to shift testing left and test as early as possible. Ideally many tests are written first and fail without the application code to support them. Most tests are unit tests written by developers to ensure components work. This makes them executable specifications and when the application code is written that makes them pass, then you are good to go.
edited 2 days ago
João Farias
3,021415
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
Classic testing is Quality Assurance
Agile Testing is Quality Engineering
Quality Assurance
Traditionally most testing as done at the end of the development. It asks if the product that has been developed meets the requirements, both explicit and implicit.
Quality Engineering
This field is primarily concerned about automation and automated tests.
It breaks out testing into:
Unit testing
Integrated Testing
Automated UI
Exploratory, Performance & Security
Over time this leads to the following situations:
Classic Testing - the product is built, the developer considers it is working but Quality Assurance has to convince them and others when there are issues. Issues are frequently found late in the process with little time for quality fixes. Fixes are expensive and often affect production. This is common in Command and Control and Waterfall environments.
Agile Testing - the goal is to shift testing left and test as early as possible. Ideally many tests are written first and fail without the application code to support them. Most tests are unit tests written by developers to ensure components work. This makes them executable specifications and when the application code is written that makes them pass, then you are good to go.
edited 2 days ago
João Farias
3,021415
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
edited 2 days ago
João Farias
3,021415
edited 2 days ago
João Farias
3,021415
edited 2 days ago
João Farias
3,021415
3,021415
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
answered 2 days ago
Michael DurrantMichael Durrant
14.5k22165
14.5k22165
add a comment |
add a comment |
Thanks for contributing an answer to Software Quality Assurance & Testing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsqa.stackexchange.com%2fquestions%2f38391%2fwhat-changes-for-testers-when-they-are-testing-in-agile-environments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Sorry, I'm not sure what the question is here.
– Daniel
2 days ago
1
Maybe the question is "What changes for testers when they are testing in agile environments?" and details say 'how do they bring in their particular experience?'
– Michael Durrant
2 days ago
"What changes for testers when they are testing in agile environments?" is correct
– Mornon
2 days ago