1. What is Agile Testing?
Agile Testing is a practice that a QA follows in a dynamic environment where testing requirements keep changing according to customer needs. It is done parallel to the development activity where the testing team receives frequent small codes from the development team for testing.
2. What is the difference between burn-up and burn-down chart?
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.
3. Define the roles in Scrum?
There are mainly three roles that a Scrum team have:
- 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.
- Scrum Master – who works with the scrum team to make sure each sprint gets complete on time. Scrum master ensures proper workflow to the team.
- Scrum Team – Each member of the team should be self-organized, dedicated and responsible for the high quality of the work.
4. What is Product Backlog & Sprint Backlog?
- The product backlog is maintained by the project owner which contains every feature and requirement of the product.
- Sprint backlog can be treated as a subset of product backlog which contains features and requirements related to that particular sprint only.
5. Define Velocity in Agile?
Velocity is a metric that is calculated by the addition of all efforts estimates associated with user stories completed in an iteration. It predicts how much work Agile can complete in a sprint and how much time will require to complete a project.
6. Explain the difference between the traditional Waterfall model and Agile testing?
- Agile testing is done parallel to the development activity whereas in the 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 the waterfall model testing is done on the whole application.
7. Explain Pair Programming and its benefits?
Pair programming is a technique in which two programmer works as a team in which one programmer writes code and other one reviews that code. They both can switch their roles.
Benefits:
- Improved code quality: As the second partner reviews the code simultaneously, it reduces the chances of mistake.
- Knowledge transfer is easy: One experience partner can teach another partner about the techniques and codes.
8. What is refactoring?
Modification of the code without changing its functionality to improve the performance is called refactoring.
9. Explain the Iterative and Incremental Development in Agile?
Iterative Development: Software is developed and delivered to the 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 the 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 developed in parts or increments. In each increment, a portion of the complete requirement is delivered.
10. How do you deal when requirements change frequently?
This question is to test the analytical capability of the candidate. The answer can be-
Work with the PO to understand the exact requirement to update test cases. Also, understand the risk of changing the requirement. Apart from this one should be able to write a generic test plan and test cases. Don’t go for the automation until requirements are finalized.
11. What is a test stub?
A small code which mimics a specific component in the system and can replace it. Its output is the same as the component it replaces.
12. What qualities should a good Agile tester have?
- An agile tester should be able to understand the requirements quickly.
- An agile tester should know Agile concepts and principals.
- As requirements keep changing, he should understand the risk involved in it.
- An agile tester should be able to prioritize the work based on the requirements.
- Communication is a must for an Agile tester as it requires a lot of communication with developers and business associates.
13. What is the difference between Epic, User stories & Tasks?
User Stories: User Stories defines the actual business requirement. Generally created by the Business owner.
- Task: To accomplish the business requirements development team create tasks.
- Epic: A group of related user stories is called an Epic.
14. What is a Taskboard in Agile?
Taskboard is a dashboard which shows the progress of the project. It contains:
- User Story: which has the actual business requirement.
- To Do: Tasks that can be worked on.
- In Progress: Tasks in progress.
- To Verify: Tasks pending for verification or testing
- Done: Completed tasks.
15. What is Test Driven Development (TDD)?
It is Test-first development technique in which we add a test first before we write complete production code. Next, we run the test and based on the result refactor the code to fulfill the test requirement.
16. How QA can add value to an agile team?
QA can provide 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.
17. What is Scrum ban?
It is a software development model which is a 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.
18. What is the Application Binary Interface?
Application Binary Interface or ABI defines an interface for compiled application programs or we can say it describes the low-level interface between an application and the operating system.
19. What is Zero sprint in Agile?
It can be defined as pre-step to the first sprint. Activities like setting development environment, preparing backlog, etc need to be done before starting of the first sprint and can be treated as Sprint zero.
20. What is Spike?
There may be some technical issues or design problem in the project which needs to be resolved first. To provide the solution of this problem “Spikes” are created. Spikes are of two types- Functional and Technical.
AGILE TESTING Questions pdf free download::
21. Name some Agile quality strategies.
Some Agile quality strategies are-
- Re-factoring
- Small feedback cycles
- Dynamic code analysis
- Iteration
22. What is the importance of daily stand up a meeting?
Daily stand up meeting is essential for any team in which-
- The team discusses how much work has been completed.
- What are the plans to resolve technical issues?
- What steps need to done to complete the projects etc.
23. What is a tracer bullet?
- It can be defined as a 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.
24. How the velocity of the sprint is measured?
- 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
25. What is Agile manifesto?
Agile manifesto defines an iterative and people-centric approach to software development. It has basically 4 key values and 12 principals.
26. Define what are the Tools that can be useful for screenshots while working on Agile projects?
While working on Agile projects you can use tools like
- BugDigger
- BugShooting
- qTrace
- Snagit
- Bonfire
- Usersnap
27. Define what are the advantages of maintaining consistent iteration length throughout the project?
The advantages are
- It helps the team to objectively measure progress
- It provides a consistent means of measuring team velocity
- It helps to establish a consistent pattern of delivery
28. If a timeboxed plan needs to be reprioritized who should re-prioritize it?
If a timeboxed plan needs to be reprioritized it should include the whole team, product owner, and developers.
29. Define what a burndown chart should highlight?
The burn-down chart shows the remaining work to complete before the timebox (iteration) ends.
30. Define what is the difference between Scrum and Agile?
Scrum: In the scrum, a sprint is a basic unit of development. Each sprint is followed by a planning meeting, where the tasks for the sprint are identified and estimated. During each sprint, the team creates a finished portion of a product
Agile: In Agile, each iteration involves a team working through a full software development cycle, including planning, design, coding, requirement analysis, unit testing, and acceptance testing when a product is demonstrated to stakeholders
In simple words, Agile is the practice and scrum is the process of following this practice.
31. Define what are the challenges involved in AGILE software development?
Challenges involved in Agile Software development includes
- It requires more testing and customers involvement
- It impacts management more than developers
- Each feature needs to be completed before moving on to the next
- All the code has to work fine to ensure the application is in a working state
- More planning is required
32. When not to use Agile?
Before using Agile methodology, you must ask the following questions
- Is functionality split-able
- Is customer available
- Are requirements flexible
- Is it really time constrained
- Is team skilled enough
33. Explain how can you implement Scrum in an easy way to your project?
These are the tips which can be helpful to implement Scrum in your project
Get your backlog in order
Get an idea of the size of your product backlog items
Clarify sprint requirement and duration to complete the sprint backlog
Calculate the team sprint budget and then break requirements into tasks
Collaborate workspace- a center of all team discussion, which includes plans, roadmaps, key dates, sketches of functionality, issues, log, status reports, etc.
Sprint- Make sure you complete one feature at a time before moving on to the next. A sprint should not be abort unless if there is no other option
Attend a daily stand-up meeting: In the meeting, you need to mention, what has been achieved since the last meeting, what will they achieve before the next meeting and is anything holding up their progress
Use burndown chart to track daily progress. From the burndown chart, you can estimate whether you are on track, or you are running behind
Complete each features well before moving on to the next
At the end of the sprint- hold a sprint review meeting, Define what is achieved or delivered in the sprint.
34. What does it mean by product roadmap?
A product roadmap is referred for the holistic view of product features that create the product vision.