Agile Testing

Agile testing is a software testing paradigm which follows the principles of agile software development.

Q.1 What are the Agile Software Development Principles?

1. The highest priority is to satisfy the customer by delivering business-critical software on a timely and consistent basis.

2. Be open to altering requirements, especially if they emerge late in the development process.

3. Consistently provide working software

4. Throughout the project, business people and developers must collaborate in a transparent manner on a daily basis.

5. Create projects that revolve around people that are passionate about what they're doing.

6. Face-to-face communication is the best method of communication.

7. Working software is the major indicator of progress.

8. Ability to keep a steady pace

9. Consistent focus on technological quality

10. Simplicity is crucial — the art of minimising the amount of effort that isn't done.

11. Self-organizing teams 

12. The team considers how to become more effective at regular intervals, then tunes and adapts its behaviour accordingly.

Q.2 What are the primary Scrum roles?

There are three primary roles in Scrum:

  • Product Owner: The Client is usually represented by the Product Owner, who serves as a point of contact for the Client. The person in charge of prioritising the Product Backlogs that the Scrum Team should complete and release.
  • Scrum Master: A Scrum Master helps the Scrum Development Team by acting as a facilitator. Clarifies questions and keeps the team organised by removing distractions and teaching the team how to use scrum, all while focusing on the return on investment (ROI). In charge of the sprint's management. Developers and QAs make up the Scrum Development Team. Who is in charge of product development? The effort estimation for completing a Product Backlog Item is decided by the Scrum development team.
  • Scrum Team: A cross-functional, self-organizing group of committed individuals (Group of Product Owners, Business Analysts, Developers, and Quality Assurance Analysts). A scrum team should have a size of 7 plus or minus 2 people (i.e, between 5 to 9 members in a team).
Q.3 What strategy do you use when requirements are always changing?
Changes in requirements are feasible with Agile methodology. It's not like other traditional approaches, which lock down requirements during the requirement phase. Every team member should be prepared to deal with project changes. The team should collaborate closely with the Product Owner to understand the breadth of the requirement change and to negotiate keeping the change to a bare minimum or adopting it in the following sprint. To meet the timeframes, the Test Team could adjust the Test Plan and Test Cases based on the requirement modifications. The team should be aware of the risk associated with the requirement change and have a contingency plan in place. It's advisable to wait until the specifications are finalised before automating the procedure.
Q.4 What distinguishes Agile Testing from other software development models?
Testing is not a phase in Agile Methodology like it is in other traditional methods. It is an Agile activity that runs concurrently with development. When opposed to traditional models, Agile methods have a shorter testing window. In Agile, the testing team focuses on minor features, whereas in traditional models, the testing team focuses on the entire programme after construction.
Q.5 What is the difference between a Product Backlog and a Sprint Backlog?
Product Backlog: A Product Backlog is a repository where the Product Owner stores and maintains a list of Product Backlog Items. The Product Owner prioritises the Product Backlog Items as high or low, and the Product Backlog can be re-prioritized at any time. The sprint backlog is a collection of user stories that the scrum development team has agreed to complete during the current sprint (Committed Product Backlog items). The product backlog is a subset of it.
Q.6 When are we going to implement the Agile Scrum Methodology?

i. When the client's needs are unclear;

ii. When the client demands rapid delivery

iii. When the customer does not provide all of the criteria at the same time.

Q.7 How would you define sprint?
The project is broken into Sprints in Scrum. Each Sprint has its own timetable (2 weeks to 1 month). During the Sprint Planning Meeting, a Scrum Team will agree on this timetable. User Stories are divided into several sections in this section. Every Sprint should culminate in a possibly shippable product.
Q.8 What is the distinction between a Burn-up chart and a Burn-down chart?
Burn Down Charts show whether or not a project is on track. Burn-up and burn-down charts are graphs that show how far a project has progressed. Burn-up charts show how much work has been performed in a project, whereas Burn-down charts show how much work is still left to be done.
Q.9 What is a Product Burndown Chart, and how does it work?
A graph depicting the number of Product Backlog Items (User Stories) that have been implemented or have not been implemented.
Q.10 What is a Sprint Burndown Chart, and what does it mean?
A graph depicting how many Sprints the Scrum Team completed or did not complete.
Q.11 What is a Burndown Chart for a Release?
A graph depicting the list of pending releases that the Scrum Team has planned.
Q.12 What is a Burndown Chart for Defects?
A graph depicting the number of problems found and rectified.
Q.13 What are the drawbacks of the agile method?

The following are some of the disadvantages of employing the agile model:

  • It is difficult to forecast. When confronted with a major project, estimating the quantity of effort required becomes more difficult.
  • If the customer's parameters are not correctly grasped, the project's final product will fall short of the customer's expectations. Customer dissatisfaction results as a result of this.
  • Sometimes it's impossible to devote enough time to a project's design and documentation.
  • In general, higher authorities are in charge of making high-level decisions.
  • Members of the team with little or no experience are not involved in decision-making, and hence do not have the opportunity to expand their knowledge.
Q.14 What are some examples of roadblocks?

Impediments occur in a variety of shapes and sizes. Some of the roadblocks are listed below.

  • Unavailability of resources (Team member who is ill)
  • Insufficient management support
  • Concerns about business
  • Incompetence
  • Problems with technology and operations
  • Even external factors such as the weather are taken into account.
Q.15 In Scrum, what is an impediment?
The challenges that the scrum team must overcome are known as impediments. Impediment is any barrier that prevents the team from getting work done and slows velocity. The Scrum Master is in charge of clearing roadblocks.
Q.16 What is the definition of Velocity?
Velocity is a crucial statistic that is calculated at the end of each sprint by adding all effort estimates linked with completed user stories. It estimates how much work an agile software development team can perform in a sprint and how long a project will take to complete. In calculating velocity, points from partially completed or incomplete user stories should be ignored.
Q.17 What is the purpose of a Sprint Planning Meeting?
The Sprint Planning Meeting, which is attended by the complete Scrum Team, is the first phase in Scrum. The Product Owner chooses Product Backlog Items (User Stories) from the Product Backlog in this step. The most significant User Stories are at the top of the list, followed by the least important User Stories. The Scrum Development Team makes decisions and estimates effort.
Q.18 What is the purpose of a Sprint Review Meeting?
The Scrum Development Team gives a demonstration of a possibly shippable product at the Sprint Review Meeting. The Product Owner indicates which items have been accomplished and which have not. Based on stakeholder feedback, the Product Owner adds additional items to the product backlog.
Q.19 What is a Sprint Retrospective Meeting, and what does it entail?
After the Sprint Review Meeting, the Scrum Team reconvenes and documents the lessons learned from the previous sprint, such as "What went well," and "What may be better." It aids the Scrum Team in avoiding errors in subsequent Sprints.
Q.20 What is Agile Testing?

Agile testing can be defined as a type of software testing process which that sticks to agile principles of software development.

Agile testing follows the iterative approach of agile software development which involves continuing and incremental development as per input from both customers and testing team. The focus of development is associated with customer requirements only and is time-boxed.

Q.21 What is Agile Testing example?

Agile testing example, for understanding Agile testing, can be the custom and personalized development of personal items like clothing which is as per requirements and iterations are done by team to satisfy the customer. Agile is an iterative approach for time-boxed incremental development of software.

As in the example illustration, customer requirement is the main driving force and at each stage of development it directs the development. Hence, in agile testing example, those features or functions are tested as per customer requirement and follows the incremental approach in software testing with iterative approach.

Q.22 How would you differentiate between Agile and Agile Testing?
Agile is a set of principles which are a guidance for incremental development of software. Agile approach is more customer-aligned and focused with incremental development and release. Agile testing on other hand, follows the agile software development for testing the increment which has been developed. Agile testing also complies with Agile principles.
Q.23 What is Agile testing and why is it important?

Agile testing refers to the testing of software that has been developed incrementally with an iterative approach. Agile testing follows Agile principles.

  • Agile testing is important, as agile-based software development is the new practice that has been widely accepted and being followed especially in new-age startup companies.
  • Agile focuses on iterative development with the iterative approach in a time-boxed manner, to fulfil the end-user need in a collaborative manner with achievable and acceptable deliverables.
  • Agile testing helps in achieving the goal of agile software development by testing at every step in the unit and integration testing level. Hence, forth agile testing is important.
Q.24 What is Agile SDLC?

Agile SDLC refers to the SDLC or software development life cycle of the agile framework. Agile is a set of principles which are a guidance for incremental development of software. Agile approach is more customer-aligned and focused with incremental development and release.

Agile focuses on incremental development with iterative approach but in a time-boxed manner.

Q.25 What is epic in agile?
Epic in agile refers to a major milestone being achieved. An epic can be a feature or functionality that a customer requires. Epic is described in user stories under Agile approach and usually involves multiple sprints for completion.
Q.26 How does Agile work?
Agile work based on the basic principles. Agile works by incremental development with iterative approach but in a time-boxed manner. Epic is defined as per customer requirement and user stories are developed for their achievement. Regular sprints or meeting are conducted for project progress assessment.
Q.27 What is QA in Agile?

QA in Agile refers to Quality Assurance which is essential part of software development process to ensure the quality of finished product as per provided requirement. QA in Agile is wholesome concept of ensuring quality from design stage and maintaining the quality level till delivery of finished product.

Agile testing is usually a part of QA in Agile.

Q.28 What is a sprint in Agile?
A sprint in Agile is a fixed time span (usually 2 – 4 weeks) of completion of a iteration in Agile. A release is broken into fixed time span and is called as a sprint.
Q.29 What is agile in simple words?
Agile in simple words is an approach to software development focusing on developing incrementally with iterative approach as per Agile principles. Customer requirement is broken into small parts as per functionalities needed which is developed, tested and after customer acceptance, it is finalized.
Q.30 What are the 12 Principles of Agile?

The 12 Principles of Agile are

  • Satisfy customer - Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Be Flexible - Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  • Working software - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Team work - Business people and developers must work together daily throughout the project.
  • Motivation - Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • Personal conversation - The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • Primary measure - Working software is the primary measure of progress.
  • Maintain pace - Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Design and technical excellence - Continuous attention to technical excellence and good design enhances agility.
  • Simplicity -  Simplicity--the art of maximizing the amount of work not done--is essential.
  • Teams - The best architectures, requirements, and designs emerge from self-organizing teams.
  • Regular interaction - At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Q.31 Is Scrum and agile the same?
Scrum and agile are not the same. Agile refers to guiding principles and values whereas Scrum is type of agile implementation for software development.
Q.32 Is SDLC waterfall or agile?
SDLC waterfall or agile, SDLC refers to software development life cycle or the phases in which software is developed. SDLC can be waterfall or Agile. Waterfall is sequential software development or in phases whereas Agile is an incremental development but in time-boxed manner with iterative approach. Agile focuses on flexibility, quick completion, and satisfying requirement
Q.33 Is SDLC a waterfall?
SDLC a waterfall, SDLC refers to software development life cycle being considered. Waterfall is sequential software development or in phases. Hence, SDLC is not waterfall only.
Q.34 What is difference between SDLC and agile?
SDLC refers to software development life cycle or the phases in which software is developed. SDLC can be waterfall or Agile. Agile is an incremental development but in time-boxed manner with iterative approach.
Q.35 What is Agile Testing explain with example?

Agile testing with example can be illustrated by considering personalized development and delivery of a luxury item. A luxury item is personalized or as per the taste of customer and having regular feedback and acceptance, from customer during product development. Agile refers to guiding principles for an incremental development but in time-boxed manner with iterative approach.

Agile testing also complies with Agile principles and continuous tests during development.

Q.36 What is Agile methodology in testing?
Agile methodology in testing means testing as per Agile principles which involves continuous testing as per continuous development or delivery of software during software development life cycle. Testing and development takes place simultaneously.
Q.37 What is Agile methodology beginner?
Agile methodology beginner, is described as set of methods and practices as per Agile manifesto. Agile methodology is an approach to software development focusing on developing incrementally with iterative approach as per Agile principles.
Q.38 What is Agile QA?
Agile QA or Quality Assurance is the process to ensure quality excellence during Agile development. QA in Agile is wholesome concept of ensuring quality from design stage and maintaining the quality level till delivery of finished product.
Q.39 Is kanban an agile?
Kanban is an agile process but may not be iterative. Kanban means label or ticket which indicates the present state and action to be done. Kanban board is used having several columns for different states to indicate different states of progress and next action to be taken.
Q.40 Why Agile is used?
Agile is used for software development and is the new practice which has been widely accepted and being followed especially in new age startup companies. Agile focuses on iterative development with iterative approach in time-boxed manner, to fulfill the end user need in a collaborative manner with achievable and acceptable deliverables.
Q.41 Which testing certification is best?

The best testing certification is on Agile testing. Agile focuses on iterative development with iterative approach in time-boxed manner, to fulfill the end user need in a collaborative manner with achievable and acceptable deliverables.

Vskills provides following deliverables for Agile testing certification

- Online video based, e-learning LMS

- Hard copy to candidates residing in India

- Practice tests for assessing your knowledge

- Government certification

- Vast alumni strength working in reputed software companies like Accenture, Cognizant, IBM, TCS, etc

Q.42 What are the certifications for testing?

There are various testing certification available.

You should select testing certification by answering following questions

- Does Hard copy or e-learning is provided?

- Practice test for assessing oneself is given?

- Are video demonstrations provided?

- What is the alumni strength

Vskills provides above deliverables and you can register for agile testing at link -https://www.vskills.in/certification/testing/agile-testing-certification

Q.43 Is automation testing a good career?

Is automation testing a good career? Yes, automation testing is the next upcoming testing domain which has gained prominence and widespread usage.

Automation tools like Selenium is a good option to get a good career with good prospects.

On popular job websites like Monster, LinkedIn, Indeed, etc have huge opening s for automation testing professionals.

Everywhere automation is gaining ground and in software testing, automation testing takes care of most of the repetitive tasks of software application testing.

Companies need professionals trained in automation testing to lower costs and time to test. Also, due to web and mobile applications, consumer demand is changing, needing quicker application development and testing. Thus, needing automation testing.

Q.44 Is there any certification for automation testing?
Yes, there are many certifications on automation testing.
Q.45 How long does it take to learn software testing?

It takes usually two to three months to learn software testing.

The time duration to learn software testing varies from few days to months, depending upon how much time you can dedicate for learning software testing and your skill of related concepts.

Q.46 Is software testing a good job?

Yes, software testing a good job. Job websites across the globe has many openings for software testing professionals.

New technologies in software testing like RPA, automation testing has good demand among IT companies across the globe.

Q.47 Is QA a good career?
Yes, QA a good career. QA or Quality Assurance is the process to ensure quality excellence during software development. QA is responsible to ensure quality excellence across the software development processes and is senior management profile with high growth opportunities.
Q.48 Does software testing require coding?
Software testing does not require coding as it may involve manual testing which may not involve coding. But, with new technologies in software testing like RPA and automation testing, may require coding to be done by software testing professionals.
Q.49 Is there any certification for agile testing?

Yes, agile testing certification is at link - https://www.vskills.in/certification/testing/agile-testing-certification


Vskills offers following deliverables

-          Online video based, e-learning LMS

-          Hard copy to candidates residing in India

-          Practice tests for assessing your knowledge

-          Government certification

-          Vast alumni strength working in reputed software companies like Accenture, Cognizant, IBM, TCS, etc

Q.50 Is there any certification for automation testing?
Yes, good link to practice agile testing skills is at link - https://www.vskills.in/practice/agile-testing-questions
Get Govt. Certified Take Test