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.
Ans: Modification of the code without changing its functionality to improve the performance is called re-factoring.
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.
Ans: A small code which mimics a specific component in the system and can replace it. Its output is same as the component it replaces.
Ans: 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.
Ans: Agile manifesto defines an iterative and people-centric approach to software development. It has basically 4 key values and 12 principals.
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.
Ans:
Ans: Task board is dash board which shows progress of the project. It contains:
Ans: There are mainly three roles that a Scrum team have:
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.
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.
Ans: 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.
Ans: 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.
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:
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.
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.
Ans: 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.
Ans: 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.
Ans: 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.
Ans: 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.
Ans: Some Agile quality strategies are-
Ans: Daily stand up meeting is essential for any team in which-
Ans: 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.
Ans: 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
Ans: When planning a sprint usually, the velocity of the sprint is measured on the basis of professional judgement based on historical data. However, the mathematical formula used to measure the velocity of the sprint are,
For our scenario second method is applicable.
Ans: Epic: A customer described software feature that is itemized in the product backlog is known as epic. Epics are sub-divided into stories
User Stories: From the client perspective user stories are prepared which defines project or business functions, and it is delivered in a particular sprint as expected.
Task: Further down user stories are broken down into different task
Ans:
| RUP | SCRUM |
| – Formal Cycle is defined across four phases, but some workflows can be concurrent | – Each sprint is a complete cycle |
| – Formal project plan, associated with multiple iterations is used. | – No end to end project plan. Each next iteration plan is determined at the end of the current iteration |
| – Scope is predefined ahead of the project start and documented in the scope document. During the project, scope can be revised. | – It uses a project backlog instead of scope scrum |
| – Artifacts include Scope Document, formal functional requirements package, system architecture document, development plan, test scripts, etc. | – Operational software is the only formal artifacts |
| – Recommended for long term, large, enterprise level projects with medium to high complexity | – Recommended for quick enhancements and organization that are not dependent on a deadline |
Ans: When requirement keeps changing, continuously agile tester should take following approach
Ans:
| Scrum | Extreme Programing (XP) |
| – Scrum teams usually have to work in iterations called sprints which usually last up to two weeks to one month long | – XP team works in iteration that last for one or two weeks |
| – Scrum teams do not allow change into their sprints | – XP teams are more flexible and change their iterations |
| – In scrum, the product owner prioritizes the product backlog but the team decides the sequence in which they will develop the backlog items | – XP team work in strict priority order, features developed are prioritized by the customer |
| – Scrum does not prescribe any engineering practices | – XP does prescribe engineering practices |
