When can a QA tester start his job?How can I switch from manual testing to writing automation?Deployment...
How does Leonard in "Memento" remember reading and writing?
False written accusations not made public - is there law to cover this?
After checking in online, how do I know whether I need to go show my passport at airport check-in?
How do you voice extended chords?
Is there a lava-breathing lizard creature (that could be worshipped by a cult) in 5e?
Let's Encrypt and EV certificates for different hosts in the same domain
Which communication protocol is used in AdLib sound card?
Cat is tipping over bed-side lamps during the night
It took me a lot of time to make this, pls like. (YouTube Comments #1)
How to visualize the Riemann-Roch theorem from complex analysis or geometric topology considerations?
Why are all my replica super soldiers young adults or old teenagers?
Why does photorec keep finding files after I have filled the disk free space as root?
Differences between prior distribution and prior predictive distribution?
How would an AI self awareness kill switch work?
Clues on how to solve these types of problems within 2-3 minutes for competitive exams
Has Britain negotiated with any other countries outside the EU in preparation for the exit?
general past possibility with COULD
Is there any risk in sharing info about technologies and products we use with a supplier?
Do "fields" always combine by addition?
How can I play a serial killer in a party of good PCs?
With regard to distributive law of inner product in vector algebra
"on its way" vs. "in its way"
Why did Luke use his left hand to shoot?
Early credit roll before the end of the film
When can a QA tester start his job?
How can I switch from manual testing to writing automation?Deployment Testing - when to performVery basic roles of a testing teamHow to create test plan when there is one website and one testerHow to ensure Quality of the product with test cases?How a Software Tester or Q & A should move ahead in his careerSetting a QA practice in an organisationCan a Manual Tester survive in software industry without learning Automation?Qualification required to become a Software TesterCan we replace everything with automation or do we need manual testing?
According to SDLC Process, testing by QA testers only stars at 'Testing' phase. Is that saying before 'Testing' phase, QA testers have no work to do.
When actually a can tester starts his job ?
Is it possible to start testing works before 'Testing' phase ?
manual-testing
add a comment |
According to SDLC Process, testing by QA testers only stars at 'Testing' phase. Is that saying before 'Testing' phase, QA testers have no work to do.
When actually a can tester starts his job ?
Is it possible to start testing works before 'Testing' phase ?
manual-testing
1
"according to SDLC" - where is this coming from? This sounds like an old book and does not reflect modern agile practices where testing starts before development. Do you work in an organization that considers itself agile?
– Michael Durrant
2 hours ago
@Michael Durrant It's an interview question
– Albin K S
18 mins ago
add a comment |
According to SDLC Process, testing by QA testers only stars at 'Testing' phase. Is that saying before 'Testing' phase, QA testers have no work to do.
When actually a can tester starts his job ?
Is it possible to start testing works before 'Testing' phase ?
manual-testing
According to SDLC Process, testing by QA testers only stars at 'Testing' phase. Is that saying before 'Testing' phase, QA testers have no work to do.
When actually a can tester starts his job ?
Is it possible to start testing works before 'Testing' phase ?
manual-testing
manual-testing
edited 8 mins ago
dzieciou
6,57833371
6,57833371
asked 2 hours ago
Albin K SAlbin K S
356
356
1
"according to SDLC" - where is this coming from? This sounds like an old book and does not reflect modern agile practices where testing starts before development. Do you work in an organization that considers itself agile?
– Michael Durrant
2 hours ago
@Michael Durrant It's an interview question
– Albin K S
18 mins ago
add a comment |
1
"according to SDLC" - where is this coming from? This sounds like an old book and does not reflect modern agile practices where testing starts before development. Do you work in an organization that considers itself agile?
– Michael Durrant
2 hours ago
@Michael Durrant It's an interview question
– Albin K S
18 mins ago
1
1
"according to SDLC" - where is this coming from? This sounds like an old book and does not reflect modern agile practices where testing starts before development. Do you work in an organization that considers itself agile?
– Michael Durrant
2 hours ago
"according to SDLC" - where is this coming from? This sounds like an old book and does not reflect modern agile practices where testing starts before development. Do you work in an organization that considers itself agile?
– Michael Durrant
2 hours ago
@Michael Durrant It's an interview question
– Albin K S
18 mins ago
@Michael Durrant It's an interview question
– Albin K S
18 mins ago
add a comment |
4 Answers
4
active
oldest
votes
Answering your particular question "Is it possible?" I would say "Yes, it is.". There are many aspects that could impact how active QA could be involved on the prior phases. For example:
- Is that an automation QA or manual QA
- How strong soft and hard skills of particular QA engineer are
- How well the job was done from the top bottom phases
- How well is the inter-project communication established
For example on Analysis phase you could work with analysts to gather proper requirements in proper notation that would be suitable for further usage when you will be designing the tests.
On Design phase you could consult your architects or tech leads on how to do your system more testable. Prepare a test strategy and estimate test budget of the project.
On Environments phase you could obviously build or help your devops to build the abstract deployment process, plan how your tests would integrate into CI/CD, plan what environmental properties are to be configured for better fitting testing needs, etc.
I didn't start from System Investigation since on that phase normally they involve very limited engineering participation so that QA are unlikely to be invited.
Disclaimer: Phases description is taken from this Wikipedia article.
add a comment |
The job of testing starts before you write code when you follow
BDD- Behavior Driven Design
and
TDD - Test Driven Design
There are many books on the above topics so I'll avoid trying to explain them in details other than to say "Test first"
add a comment |
I would say it should ideally start, when project starts. Because most of thing in project can, and should be tested in some way. No one in project team is flawless, and bad decisions will probablo cost time or money later.
You can test:
- ideas – participation in meeting will add another point of view, and may make software more testable.
- requirement – they can be ambiguous and thus poorly understood by delveloper
- software
- lot more things, like processes within project team, used technologies,…
Testing is not done only when you sit before computer, and management should count with it. You probably already been thinking about project before someone told you that „'Testing' phase“ started.
You will do better work, when you have better knowledge of tested application.
New contributor
add a comment |
The best time to start is? Now!
Traditionally people view testing as a phase that happens at the end
of development. In agile most have changed it that the chunk of
development done is smaller, but the testing still happens last.
Nothing has fundamentally changed about how testing is done.
...
In contrast in agile, testing is just an activity that needs to
happen, along with coding, documentation and everything else. Thinking
about it like this makes it possible to consider the idea of doing
testing tasks before development work. A great way to visualise this
on a taskboard is that instead of having a separate column for test,
rather just make testing tasks a different colour sticky note.
https://leanpub.com/AgileTesting/read
Other reads for inspiration of pre-post code testing activities:
- https://less.works/less/technical-excellence/thinking-about-testing.html
- Modern Testing Principles
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%2f37995%2fwhen-can-a-qa-tester-start-his-job%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Answering your particular question "Is it possible?" I would say "Yes, it is.". There are many aspects that could impact how active QA could be involved on the prior phases. For example:
- Is that an automation QA or manual QA
- How strong soft and hard skills of particular QA engineer are
- How well the job was done from the top bottom phases
- How well is the inter-project communication established
For example on Analysis phase you could work with analysts to gather proper requirements in proper notation that would be suitable for further usage when you will be designing the tests.
On Design phase you could consult your architects or tech leads on how to do your system more testable. Prepare a test strategy and estimate test budget of the project.
On Environments phase you could obviously build or help your devops to build the abstract deployment process, plan how your tests would integrate into CI/CD, plan what environmental properties are to be configured for better fitting testing needs, etc.
I didn't start from System Investigation since on that phase normally they involve very limited engineering participation so that QA are unlikely to be invited.
Disclaimer: Phases description is taken from this Wikipedia article.
add a comment |
Answering your particular question "Is it possible?" I would say "Yes, it is.". There are many aspects that could impact how active QA could be involved on the prior phases. For example:
- Is that an automation QA or manual QA
- How strong soft and hard skills of particular QA engineer are
- How well the job was done from the top bottom phases
- How well is the inter-project communication established
For example on Analysis phase you could work with analysts to gather proper requirements in proper notation that would be suitable for further usage when you will be designing the tests.
On Design phase you could consult your architects or tech leads on how to do your system more testable. Prepare a test strategy and estimate test budget of the project.
On Environments phase you could obviously build or help your devops to build the abstract deployment process, plan how your tests would integrate into CI/CD, plan what environmental properties are to be configured for better fitting testing needs, etc.
I didn't start from System Investigation since on that phase normally they involve very limited engineering participation so that QA are unlikely to be invited.
Disclaimer: Phases description is taken from this Wikipedia article.
add a comment |
Answering your particular question "Is it possible?" I would say "Yes, it is.". There are many aspects that could impact how active QA could be involved on the prior phases. For example:
- Is that an automation QA or manual QA
- How strong soft and hard skills of particular QA engineer are
- How well the job was done from the top bottom phases
- How well is the inter-project communication established
For example on Analysis phase you could work with analysts to gather proper requirements in proper notation that would be suitable for further usage when you will be designing the tests.
On Design phase you could consult your architects or tech leads on how to do your system more testable. Prepare a test strategy and estimate test budget of the project.
On Environments phase you could obviously build or help your devops to build the abstract deployment process, plan how your tests would integrate into CI/CD, plan what environmental properties are to be configured for better fitting testing needs, etc.
I didn't start from System Investigation since on that phase normally they involve very limited engineering participation so that QA are unlikely to be invited.
Disclaimer: Phases description is taken from this Wikipedia article.
Answering your particular question "Is it possible?" I would say "Yes, it is.". There are many aspects that could impact how active QA could be involved on the prior phases. For example:
- Is that an automation QA or manual QA
- How strong soft and hard skills of particular QA engineer are
- How well the job was done from the top bottom phases
- How well is the inter-project communication established
For example on Analysis phase you could work with analysts to gather proper requirements in proper notation that would be suitable for further usage when you will be designing the tests.
On Design phase you could consult your architects or tech leads on how to do your system more testable. Prepare a test strategy and estimate test budget of the project.
On Environments phase you could obviously build or help your devops to build the abstract deployment process, plan how your tests would integrate into CI/CD, plan what environmental properties are to be configured for better fitting testing needs, etc.
I didn't start from System Investigation since on that phase normally they involve very limited engineering participation so that QA are unlikely to be invited.
Disclaimer: Phases description is taken from this Wikipedia article.
answered 2 hours ago
Alexey R.Alexey R.
7,2971829
7,2971829
add a comment |
add a comment |
The job of testing starts before you write code when you follow
BDD- Behavior Driven Design
and
TDD - Test Driven Design
There are many books on the above topics so I'll avoid trying to explain them in details other than to say "Test first"
add a comment |
The job of testing starts before you write code when you follow
BDD- Behavior Driven Design
and
TDD - Test Driven Design
There are many books on the above topics so I'll avoid trying to explain them in details other than to say "Test first"
add a comment |
The job of testing starts before you write code when you follow
BDD- Behavior Driven Design
and
TDD - Test Driven Design
There are many books on the above topics so I'll avoid trying to explain them in details other than to say "Test first"
The job of testing starts before you write code when you follow
BDD- Behavior Driven Design
and
TDD - Test Driven Design
There are many books on the above topics so I'll avoid trying to explain them in details other than to say "Test first"
answered 2 hours ago
Michael DurrantMichael Durrant
14k22065
14k22065
add a comment |
add a comment |
I would say it should ideally start, when project starts. Because most of thing in project can, and should be tested in some way. No one in project team is flawless, and bad decisions will probablo cost time or money later.
You can test:
- ideas – participation in meeting will add another point of view, and may make software more testable.
- requirement – they can be ambiguous and thus poorly understood by delveloper
- software
- lot more things, like processes within project team, used technologies,…
Testing is not done only when you sit before computer, and management should count with it. You probably already been thinking about project before someone told you that „'Testing' phase“ started.
You will do better work, when you have better knowledge of tested application.
New contributor
add a comment |
I would say it should ideally start, when project starts. Because most of thing in project can, and should be tested in some way. No one in project team is flawless, and bad decisions will probablo cost time or money later.
You can test:
- ideas – participation in meeting will add another point of view, and may make software more testable.
- requirement – they can be ambiguous and thus poorly understood by delveloper
- software
- lot more things, like processes within project team, used technologies,…
Testing is not done only when you sit before computer, and management should count with it. You probably already been thinking about project before someone told you that „'Testing' phase“ started.
You will do better work, when you have better knowledge of tested application.
New contributor
add a comment |
I would say it should ideally start, when project starts. Because most of thing in project can, and should be tested in some way. No one in project team is flawless, and bad decisions will probablo cost time or money later.
You can test:
- ideas – participation in meeting will add another point of view, and may make software more testable.
- requirement – they can be ambiguous and thus poorly understood by delveloper
- software
- lot more things, like processes within project team, used technologies,…
Testing is not done only when you sit before computer, and management should count with it. You probably already been thinking about project before someone told you that „'Testing' phase“ started.
You will do better work, when you have better knowledge of tested application.
New contributor
I would say it should ideally start, when project starts. Because most of thing in project can, and should be tested in some way. No one in project team is flawless, and bad decisions will probablo cost time or money later.
You can test:
- ideas – participation in meeting will add another point of view, and may make software more testable.
- requirement – they can be ambiguous and thus poorly understood by delveloper
- software
- lot more things, like processes within project team, used technologies,…
Testing is not done only when you sit before computer, and management should count with it. You probably already been thinking about project before someone told you that „'Testing' phase“ started.
You will do better work, when you have better knowledge of tested application.
New contributor
edited 42 mins ago
New contributor
answered 50 mins ago
tugotugo
865
865
New contributor
New contributor
add a comment |
add a comment |
The best time to start is? Now!
Traditionally people view testing as a phase that happens at the end
of development. In agile most have changed it that the chunk of
development done is smaller, but the testing still happens last.
Nothing has fundamentally changed about how testing is done.
...
In contrast in agile, testing is just an activity that needs to
happen, along with coding, documentation and everything else. Thinking
about it like this makes it possible to consider the idea of doing
testing tasks before development work. A great way to visualise this
on a taskboard is that instead of having a separate column for test,
rather just make testing tasks a different colour sticky note.
https://leanpub.com/AgileTesting/read
Other reads for inspiration of pre-post code testing activities:
- https://less.works/less/technical-excellence/thinking-about-testing.html
- Modern Testing Principles
add a comment |
The best time to start is? Now!
Traditionally people view testing as a phase that happens at the end
of development. In agile most have changed it that the chunk of
development done is smaller, but the testing still happens last.
Nothing has fundamentally changed about how testing is done.
...
In contrast in agile, testing is just an activity that needs to
happen, along with coding, documentation and everything else. Thinking
about it like this makes it possible to consider the idea of doing
testing tasks before development work. A great way to visualise this
on a taskboard is that instead of having a separate column for test,
rather just make testing tasks a different colour sticky note.
https://leanpub.com/AgileTesting/read
Other reads for inspiration of pre-post code testing activities:
- https://less.works/less/technical-excellence/thinking-about-testing.html
- Modern Testing Principles
add a comment |
The best time to start is? Now!
Traditionally people view testing as a phase that happens at the end
of development. In agile most have changed it that the chunk of
development done is smaller, but the testing still happens last.
Nothing has fundamentally changed about how testing is done.
...
In contrast in agile, testing is just an activity that needs to
happen, along with coding, documentation and everything else. Thinking
about it like this makes it possible to consider the idea of doing
testing tasks before development work. A great way to visualise this
on a taskboard is that instead of having a separate column for test,
rather just make testing tasks a different colour sticky note.
https://leanpub.com/AgileTesting/read
Other reads for inspiration of pre-post code testing activities:
- https://less.works/less/technical-excellence/thinking-about-testing.html
- Modern Testing Principles
The best time to start is? Now!
Traditionally people view testing as a phase that happens at the end
of development. In agile most have changed it that the chunk of
development done is smaller, but the testing still happens last.
Nothing has fundamentally changed about how testing is done.
...
In contrast in agile, testing is just an activity that needs to
happen, along with coding, documentation and everything else. Thinking
about it like this makes it possible to consider the idea of doing
testing tasks before development work. A great way to visualise this
on a taskboard is that instead of having a separate column for test,
rather just make testing tasks a different colour sticky note.
https://leanpub.com/AgileTesting/read
Other reads for inspiration of pre-post code testing activities:
- https://less.works/less/technical-excellence/thinking-about-testing.html
- Modern Testing Principles
answered 40 mins ago
Niels van ReijmersdalNiels van Reijmersdal
20.5k23071
20.5k23071
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%2f37995%2fwhen-can-a-qa-tester-start-his-job%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
1
"according to SDLC" - where is this coming from? This sounds like an old book and does not reflect modern agile practices where testing starts before development. Do you work in an organization that considers itself agile?
– Michael Durrant
2 hours ago
@Michael Durrant It's an interview question
– Albin K S
18 mins ago