Ans. Agile Testing is a practice that a QA follows in a dynamic environment where testing requirements keep changing according to the customer needs. It is done parallel to the development activity where testing team receives frequent small codes from the development team for testing.
Q#2. What is the difference between burn-up and burn-down chart?
Ans. Burn-up and burn-down charts
are used to keep track the progress of the project.
Burn-up charts represent how much work has been completed in any
project whereas Burn-down chart
represents the remaining work in a
project.
Q#3. Define
the roles in Scrum?
Ans. There are mainly three roles
that a Scrum team have:
- Project
Owner – who has the responsibility of
managing product backlog. Works with end users and customers and provide
proper requirement to the team to build the proper product.
- Scrum
Master – who works
with scrum team to make sure each sprint gets complete on time. Scrum
master ensure proper work flow to the team.
- Scrum
Team – Each member in the team should be
self-organized, dedicated and responsible for high quality of the work.
Q#4.
What is Product backlog & Sprint Backlog?
Ans. Product backlog is maintained by the project owner which contains
every feature and requirement of the product.
Sprint backlog can be treated as subset of
product backlog which contains features and requirements related to that
particular sprint only.
Q#5. Explain Velocity in Agile?
Ans. Velocity is a metric that is
calculated by addition of all efforts estimates associated with user stories
completed in a iteration. It predicts how much work Agile can complete in a
sprint and how much time will require to complete a project.
Q#6. Explain the difference between traditional Waterfall model and Agile testing?
Ans. Agile testing is done parallel to
the development activity whereas in traditional waterfall model testing is done
at the end of the development.
As
done in parallel, agile testing is done on small features whereas in waterfall
model testing is done on whole application.
Q#7. Explain Pair Programming and its benefits?
Ans. Pair programming is a
technique in which two programmer works as team in which one programmer writes
code and other one reviews that code. They both can switch their roles.
Benefits:
- Improved code quality: As second
partner reviews the code simultaneously, it reduces the chances of
mistake.
- Knowledge transfer is easy: One
experience partner can teach other partner about the techniques and codes.
Q#8. What is re-factoring?
Ans. Modification of the code
without changing its functionality to improve the performance is called
re-factoring.
Q#9. Explain the Iterative and Incremental Development in Agile?
Ans.
Iterative Development: Software
is developed and delivered to customer and based on the feedback again
developed in cycles or release and sprints. Say in Release 1 software is
developed in 5 sprints and delivered to customer. Now customer wants some
changes, then development team plan for 2nd release which can
be completed in some sprints and so on.
Incremental
Development: Software
is development in parts or increments. In each increment a portion of the
complete requirement is delivered.
Q#10. How do you deal when requirements change frequently?
Ans. This question is to test the analytical
capability of the candidate. Answer can be-
Work
with PO to understand the exact requirement to update test cases. Also
understand the risk in changing the requirement. Apart from this one should be
able to write generic test plan and test cases. Don’t go for the automation
until requirements are finalized.
