Agile Testing Interview Questions and Answers

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 the testing team receives frequent small codes from the development team for testing.

Burn-up and burn-down charts are used to keep track of 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.

There are mainly three roles that a Scrum team have:

  1. Project Owner – who has the responsibility of managing the product backlog. Works with end users and customers and provide proper requirement to the team to build the proper product.
  2. 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.
  3. Scrum Team – Each member in the team should be self-organized, dedicated and responsible for high quality of the work.

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.

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.

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

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:

  1. Improved code quality: As second partner reviews the code simultaneously, it reduces the chances of mistake.
  2. Knowledge transfer is easy: One experience partner can teach other partner about the techniques and codes.

Application Binary Interface or ABI defines an interface for complied application programs or we can say it describes the low level interface between an application and the operating system.

It can be defined as pre step to the first sprint. Activities like setting development environment, preparing backlog etc needs to be done before starting of the first sprint and can be treated as Sprint zero.

There may be some technical issues or design problem in the project which needs to be resolved first. To provide the solution of these problem “Spikes” are created. Spikes are of two types- Functional and Technical.

Some Agile quality strategies are-

  1. Re-factoring
  2. Small feedback cycles
  3. Dynamic code analysis
  4. Iteration

It can be defined as spike with the current architecture or the current set of best practices.

The purpose of a tracer bullet is to examine how an end-to-end process will work and examine feasibility.

Modification of the code without changing its functionality to improve the performance is called re-factoring.

 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.

This question is to test the analytical capability of the candidate.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.

A small code which mimics a specific component in the system and can replace it. Its output is same as the component it replaces.

  1. Agile tester should be able to understand the requirements quickly.
  2. Agile tester should know Agile concepts and principals.
  3. As requirements keep changing, he should understand the risk involve in it.
  4. Agile tester should be able to prioritize the work based on the requirements.
  5. Communication is must for a Agile tester as it requires a lot of communication with developers and business associates.

User Stories:User Stories defines the actual business requirement. Generally created by Business owner.

Task: To accomplish the business requirements development team create tasks.

Epic: A group of related user stories is called an Epic.

Task board is dash board which shows progress of the project. It contains:

  1. User Story: which has the actual business requirement.
  2. To Do: Tasks that can be worked on.
  3. In Progress: Tasks in progress.
  4. To Verify: Tasks pending for verification or testing
  5. Done: Completed tasks

It is Test-first development technique in which we add a test first before we write a complete production code. Next we run the test and based on the result refactor the code to fulfill the test requirement.

QA can provide a value addition by thinking differently about the various scenarios to test a story. They can provide quick feedback to the developers whether new functionality is working fine or not.

It is a software development model which is combination of scrum and kanban. Scrumban is considered for maintenance projects in which there are frequent changes or unexpected user stories. It can reduce the minimum completion time for user stories.

Daily stand up meeting is essential for any team in which-

  1. Team discuss about how much work has been completed.
  2. What are the plans to resolve technical issues.
  3. What steps need to done to complete the projects etc.

Agile manifesto defines an iterative and people-centric approach to software development. It has basically 4 key values and 12 principals.

If capacity is measured as a percentage of a 40 hours weeks then completed story points * team capacity

If capacity is measured in man hours then Completed story points / team capacity

Start the change

Register to become an Instructor

Please login to fill in this form.

  • Your name
  • Your email
  • Your phone number
  • Your message

I’m a Copywriter in a Digital Agency, I was searching for courses that’ll help me broaden my skill set. Before signing up for Rob’s.