|
INTERVIEW QUESTIONS
TESTING
MANUAL TESTING
DETAILS
Question: What is Extreme Programming and what's it got to do with testing?
Answer: Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained' is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before the application is developed. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help develope scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected.
|
|
|
Category |
Manual Testing Interview Questions & Answers -
Exam Mode /
Learning Mode
|
Rating |
(0.3) By 7680 users |
Added on |
9/12/2014 |
Views |
66745 |
Rate it! |
|
|
Question:
What is Extreme Programming and what's it got to do with testing?
Answer:
Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained' is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before the application is developed. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help develope scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected. Source: CoolInterview.com
If you have the better answer, then send it to us. We will display your answer after the approval.
Rules to Post Answers in CoolInterview.com:-
- There should not be any Spelling Mistakes.
- There should not be any Gramatical Errors.
- Answers must not contain any bad words.
- Answers should not be the repeat of same answer, already approved.
- Answer should be complete in itself.
|
|
Related Questions |
View Answer |
|
How is testing affected by object-oriented designs?
|
View Answer
|
|
How can World Wide Web sites be tested?
|
View Answer
|
|
How does a client/server environment affect testing?
|
View Answer
|
|
What if an organization is growing so fast that fixed QA processes are impossible?
|
View Answer
|
|
How can Software QA processes be implemented without stifling productivity?
|
View Answer
|
|
What if the application has functionality that wasn't in the requirements?
|
View Answer
|
|
What if the project is not big enough to justify extensive testing?
|
View Answer
|
|
What if there is not enough time for thorough testing?
|
View Answer
|
|
How can it be known when to stop testing?
|
View Answer
|
|
What if the software is so much bugs it can't really be tested at all?
|
View Answer
|
|
What is 'configuration management'?
|
View Answer
|
|
What should be done after a bug is found?
|
View Answer
|
|
What is a 'test case'?
|
View Answer
|
|
What is a 'test plan'?
|
View Answer
|
|
What steps are needed to develop and run software tests?
|
View Answer
|
|
What's the role of documentation in QA?
|
View Answer
|
|
What makes a good QA or Test manager?
|
View Answer
|
|
What makes a good Software QA engineer?
|
View Answer
|
|
What makes a good test engineer?
|
View Answer
|