Agile Testing Interview Questions

1) To begin with, either owner or the customer reads the agile user story, and its features are understood by the estimator.

2) Every estimator has planning cards each having a different number on it, like for example 0, 1, 2, 3, 5, 8 and so on. The number on the card stands for the story points or ideal days.

3) The features set by the owner of the product are discussed by the Estimator after selecting the cards based on their estimation.

4) In case a common value is selected, then-then that is the estimate. If it is not the case, then they discuss upon the minimum and maximum value estimation.

5) The above process is repeated until and unless they all reach a general agreement.

•  The focus is on satisfied customers.
•  The code is clean and bug-free.
•  Changes suggested by the customers are always welcomed.
•  The work is done collectively by developers and whole team business persons.
•  The focus is on essence as opposed to lengthy documentation.
•  Face-to-face conversations are emphasized upon.
•  Sustainable development is promoted.

Developers might accidentally execute a bug during the development of the software. When such kinds of bugs generate warnings, result in failed normal executions during testing or even hamper the compilation process- this irregularity is referred to broken build. The priority of the tester in such cases is to bring the development back to the standard stage by quickly resolving the issue with bugs.

1. An agile tester should have a better and quick understanding of the requirements.
2. Agile principals and concepts should be known by the Agile Tester.
3. He should be able to understand the risk involved in the requirements as they always keep changing.
4. Agile tester, based on the requirements, should know how to prioritize the work involved.
5. An agile tester must be able to communicate with the business associates and developers as their work depends upon better communication.

1. User story: The actual business requirement or the user story.
2. To Do: Tasks that can be worked upon.
3. In Progress: Tasks, that is in progress.
4. To Verify: Tasks that are still pending for the testing or verification
5. Done: Tasks that are completed.

Incremental Development: Software development is done mainly in increments or more specifically, parts. In every single increment, a part of the complete requirement is to be delivered.

Iterative Development: Software is known to be delivered after developing it, to the customer. Based on the feedback, the software is again developed in cycles and released in sprints. For example, if in Release 1 after five sprints the software is developed and delivered to the customer. After that, if the customer wants changes to be made, then the development team has to make plans for the second release that will be completed in sprints and so on.

In the traditional Waterfall model, the testing is generally done at the end of development. However, in Agile methodology, the testing is done in parallel with the developmental activity, which means that as the development progresses so does the testing.

While using test driven developments, collaborators of class responsibilities, pair programming, daily stand-up meeting, reviews, continuous integration, time-boxed task board, and more, you will easily know that you are simply using the best- agile development.