Which statement is TRUE in respect to exploratory testing in Agile projects?

Testers having good knowledge of the system should perform exploratory testing.

The Independent Test team should be engaged in exploratory testing

Users engaged in Alpha testing should perform exploratory testing

Automated tests should be used for exploratory testing.

Out of the following which statements best reflects one of the values of the Agile Manifesto?

Working software allows the customer to provide rapid feedback to the developer.

Developers should use unit testing tools to support the testing process.

Business representatives should provide a backlog of user stories and their estimates to the team.

Adopting plans to change adds no real value to Agile project.

Out of the following which statements about Test Driven Development (TDD) is FALSE?

The result of Test Driven Development are test classes used by the developer to develop test cases

Test Driven Development is a ”test first” approach to develop reusable automated tests.

The Test Driven Development cycle is continuously used until the software product is released.

Test Driven Development helps to document the code for future maintenance efforts.

Out of the following which statements about Acceptance Test-Driven Development is FALSE?

Acceptance Test-Driven Development allows a developer to focus on testing the code based on the expected behavior of the software.

Tests are created once the user story is analyzed, discussed and written by the Agile team.

Acceptance Test-Driven Development defines acceptance criteria and tests In the creation of the user stories.

Acceptance Test-Driven Development is a test-first approach, test cases are created prior to implementing the user story.

Out of the following which statements about Test Driven Development (TDD) is FALSE?

Test-Driven Development allows the developer to collaborate with other stakeholders, including testers, to define accurate unit tests focused on business needs.

The Test-Driven Development process starts with a developer adding a test that captures the concept of the desired function of a small piece of code.

In Test-Driven Development, developers write the code and run the test in a tight loop until the test passes.

In Test-Driven Development, developers refactor the code after the test is passed, re-running the test to ensure it continues to pass against the refactored code.

The term “velocity” refers to Out of the following which?

A Velocity chart shows the sum of estimates of the work delivered across iterations; this may be used while selecting the stories for the next iteration

A Velocity chart shows the degree to which the source code of a program is tested by a particular test. This may be used to show the code coverage

A Velocity chart shows the count of the number of defects discovered during a given period. This may be used as criteria for stopping the testing.

A Velocity chart shows the number of source code changes per iteration; this may be used to know the code coverage

What does the term ‘Test Pyramid’ refer to and illustrate situations for?

The number of automated unit tests is higher than the number of automated tests for higher test levels.

The team’s testing workload increases from sprint to sprint.

The backlog size, and thus the number of tests, decreases.

The number of automated tests in place increases from sprint to sprint.

The concept of the Test Pyramid is based on Out of the following which testing principles?

Exhaustive testing is impossible.

Before beginning the first iteration of a project the team is discussing the test strategy for automation. Out of the following which is true with respect to Test Pyramid?

The team should aim to automate most of the unit/component tests during the sprints.

The team should aim to automate most of the usability tests during the sprints.

The team should aim to automate most of the exploratory tests during the sprints.

The team should aim to automate most of the user story tests during the sprints.

What does the term ‘Test Pyramid’ refer to in Agile projects?

The number of automated tests are greater at the unit level and decrease at the higher levels.

It is used to help the team understand the testing coverage for the user story/feature.

It can help the team determine how much testing time will be required for each user story.

It can help the team to find the impacted automated tests due to changes in a feature.

Out of the following which statements about Behaviour-Driven Development is FALSE?

In Behaviour-Driven Development, automated test cases are created before coding starts.

Behaviour-Driven Development allows a developer to focus on testing the code based on the expected behavior of the software.

Behaviour-Driven Development allows the developer to collaborate with other stakeholders, including testers, to define accurate unit tests focused on business needs.

The result of Behaviour-Driven Development is test classes used by the developers to develop the test cases.

At the beginning of the 5th iteration of a project, a new requirement was introduced to support a new type of browser. The tester realizes that the existing test automation framework and scripts will not support the new type of browser. What is the best course of action for the tester on this team to take?

The tester will notify the team of the issue. A risk analysis is done, and the team decides that regression testing must be performed on the new type of browser in addition to the other supported browsers. The tester will update the sprint plan by adding tasks to modify the framework and scripts to support the new type of browser.

The tester should notify the team that they are planning on working extra hours throughout the next 2 sprints in order to update the existing test automation framework and scripts to support the new type of browser so as not to disturb the existing sprint plan.

The tester does some research and concludes that the risk is low that any new defects would be introduced in the new type of browser that have not already been found in other supported browsers. The tester continues with the existing sprint plan and makes no changes to test automation framework or scripts

The tester will stop what they are doing, design specific tests for compatibility testing of the new type of browser, and communicate with the team that any other testing work for the sprint will have to be pushed to the next iteration.

Consider the following user story: “As the president, any data I upload should not be viewable by any other user of the system”. In the first poker planning session, the following story points were given based on risk, effort, complexity, and proper extent of testing: Customers: 5 Developers: 5 Testers: 20 What is the best outcome following this planning session?

The team should hold a conversation to understand why the testers felt this user story was significantly more work. Another round of the planning poker session should occur following that discussion.

Because the customer’s and developer’s size estimates match, the team can be confident that this estimate is good and should move onto the next user story.

Because the customer owns the system in the end, the customers’ estimates should be taken as correct when there is a conflict.

The poker planning sessions should continue until all estimated story points are an exact match between customers, developers, and testers.

Consider the following user story: “The social networking application should now check for the user age and only the users of age 18 or above should be able to register” And the associated test cases: Test Case 1: Check the Save Method 0 saves the user age to the database. Test Case 2: Verify an existing user is able to access the social networking site. Test Case 3: A registered user is able to delete their social networking site account. Which TWO test quadrants would the above test cases be part of?

Q1 unit level, technology facing & Q3 system or user acceptance level, business facing

Q1 unit level, technology facing & Q2 system level, business facing

Q3 system or user acceptance level, business facing & Q4 system or operation acceptance level, technology facing

Q2 system level, business facing & Q4 system or operation acceptance level, technology facing

The Agile Manifesto has 4 statements of values. Match the agile value (1-4) with its traditional counterpart (i-iv). 1) Customer collaboration over. 2) Responding to change over. 3) Individuals and interactions over. 4) Working software over. i) Processes and tools. ii) Following a plan. iii) Contract negotiation. iv) Comprehensive documentation.

1 – iii, 2 – ii, 3 – i, 4 – iv

1 – iii, 2 – iv, 3 – ii, 4 – i

1 – iv, 2 – ii, 3 – i, 4 – iii

1 – ii, 2 – iii, 3 – iv, 4 – i

Given the following user stories: “As a bank teller, I can easily navigate through the system menu and links, and find the information I am looking for” “For all users, the system must display all queries in less than 2 seconds, 90% of the time” And the associated test cases: TC1: Login as the bank teller. Enter customer ID. Verify that the customer transaction history is easy to find and that navigating through the menus is intuitive. TC2: Login as bank teller: Enter customer Name. Verify that the customer accounts are easy to find and that navigating through the menus is intuitive. TC3: Simulate expected traffic on the system and validate the time for customer transaction history to display is less than 2 seconds. Which TWO test quadrants would the above test cases be part of?

Q3 system or user acceptance level, business facing & Q4 system or operation acceptance level, technology facing

Q1 unit level, technology facing & Q2 system level, business facing

Q2 system level, business facing & Q3 system or user acceptance level, business facing

Q2 system level, business facing & Q4 system or operation acceptance level, technology facing

Match the testing quadrants on the left (1-4) with its correct test type on the right (i-iv). 1. Q1 2. Q2 3. Q3 4. Q4 i) Story test. ii) Recovery test. iii) Beta test. iv) unit test.

1 – iv, 2 – i, 3 – iii, 4 – ii

1 – iii, 2 – iv, 3 – ii, 4 – i

1 – iv, 2 – ii, 3 – i, 4 – iii

1 – iv, 2 – iii, 3 – i, 4 – ii

Consider the following user story: “As a bank customer, I can easily view my bank statements for the last 5 years” “For all customers, the system must display all queries in less than 4 seconds, 90% of the time” And the associated test cases: Test Case 1: Login as the bank customer. Verify that the customer transaction history is available for the last 5 years. Test Case 2: Verify in a realistic environment that the customer can view the statement in less than 4 seconds. Which TWO test quadrants would the above test cases be part of?

Q2 system level, business facing & Q4 system or operation acceptance level, technology facing.

Q1 unit level, technology facing & Q2 system level, business facing.

Q2 system level, business facing & Q3 system or user acceptance level, business facing.

Q1 unit level, technology facing & Q4 system or operation acceptance level, technology facing.

In the release planning session the tester is communicating the test ideas using testing quadrants so that the team understands the purpose of all the test types and test levels included in the development lifecycle. Out of the following which tester statements about testing quadrants are true?

Quadrant Q2 are functional tests and Quadrant Q4 are performance tests.

Quadrant Q1 are unit level tests and Quadrant Q4 are functional tests.

Quadrant Q1 are unit level tests and Quadrant Q4 are user acceptance tests.

Quadrant Q3 are performance tests and Quadrant Q4 are functional tests.

In the New Agile team the testers and developers are sitting together but the product owners are based in a different location though they participate in all daily stand-up and planning meetings and retrospectives. Some of the testers are new to the Agile project and they are not able to cope with the changes coming during each iteration. The product owner has found a couple of instances where the testing team has not followed the testing strategy agreed to by the team during test execution. What does organizational and behavioral best practices the team lack?

Co-located, Resilience, Credible

Self-organizing, Empowered, Credible

Self-organizing, Resilience, Committed

Cross-functional, Empowered, Credible

Co-located, Collaborative, Committed

There is a new feature in scope for the current sprint which will result in changes to the existing database tables. The testers on the team realize that this change can introduce bugs and it may require major changes in the existing scripts and the automation framework. What is the best course of action for the testers to take?

The testers will notify the team of the issue. A risk analysis is done and the team decides what regression testing must be performed to find the defects introduced by the new changes. The testers will update the sprint plan by adding tasks to modify the framework and scripts to support the new changes.

The testers will calculate the extra time required and update the team that they have to work extra hours in order to update the existing test scripts and automation framework In the existing sprint plan.

The current testing tasks need to be completed for the sprint. The testers continue with their existing sprint plan and make no changes to the test automation framework or scripts.

The testers will stop what they are doing and start working on the automation framework & script modifications and communicate with the team that any other testing work for the sprint will have to be pushed to the next iteration.

Agile team is doing the quality risk analysis for the following user stories selected from the backlog items In an iteration planning session. Match the stories with their respective quality risk based on the information below: User Story 1: A program to calculate account interest information for the financial end of year report. User Story 2: A program to display search results in less than 3 secs. User Story 3: A program to work on different operating systems.

User Story 1: Functional, User Story 2: performance, User Story 3: Compatibility

User Story 1: Security, User Story 2: Functional, User Story 3: Recoverability

User Story 1: Security, User Story 2: performance, User Story 3: Compatibility

User Story 1: Functional, User Story 2: performance, User Story 3: Recoverability

Agile team is doing the quality risk analysis for three user stories selected from the backlog during an iteration planning session. Match the stories with their respective quality risk based on the information below: User Story 1: Program to calculate the account interest information for the financial end of year report. User Story 2: Program to store the customer sensitive information. User Story 3: A front-end screen for the system used by senior citizens.

User Story 1: Functional, User Story 2: Security, User Story 3: Usability

User Story 1: Security, User Story 2: Functional, User Story 3: Usability

User Story 1: Usability, User Story 2: Security, User Story 3: Functional

User Story 1: Functional, User Story 2: Usability, User Story 3: Security

In the quality risk analysis session, of iteration planning, the Agile team identified the quality risk for each story and the level of risk based on the impact and likelihood of defects # User story 1 (Functional): Likelihood: high, Impact: high # User story 2 (Security): Likelihood: low, Impact: medium # User story 3 (Performance): Likelihood: high, Impact: medium # User story 4 (Functional): Likelihood: low, Impact: low # User story 5 (Recoverability): Likelihood: low, Impact: medium How can the team mitigate these risks during the iteration? Select TWO options.

The tasks associated with user story 1 should be started first.

The tasks associated with user story 4 should be started last.

The tasks associated with user story 3 should be started first.

The tasks associated with user story 2 should be started last.

The tasks associated with user story 5 should be started last.

Given the following results from a product risk analysis that occurred at the beginning of an iteration: # User story 1 (Performance): Likelihood: high, Impact: high # User story 2 (Security): Likelihood: high, Impact: high # User story 3 (Functional): Likelihood: medium, Impact: high # User story 4 (Functional): Likelihood: high, Impact: medium # User story 5 (Compatibility): Likelihood: low, Impact: low # User story 6 (Recoverability): Likelihood: low, Impact: low Which out of the following TWO describes best what the team should do with this information? Select TWO options.

Move onto planning poker session to estimate effort for user stories, and determine what can be done in the current iteration, and what needs to be added to the backlog.

The team should collaborate on effective ways to mitigate the high likelihood, high impact risks

Remove user stories 5 and 6 from the current iteration and move to a later iteration.

Because of the number of high likelihood, high impact risks slotted for this iteration, the team has no choice but to extend the timeframe of the iteration by 2 weeks.

The team should plan to complete all items in the current sprint, but save the lower risk items for the end of the sprint, and only test these items if there is time.

ISTQB Agile Tester Extension Exam Crash Course Part 3

Professional Development

•

40 Qs

Similar activities

health and safety revision 25-26

Professional Development

•

43 Qs

Vocabulary 1

Professional Development

•

40 Qs

Revision EM

12th Grade - Professional Development

•

40 Qs

Annual Quiz Time Division

Professional Development

•

35 Qs

Bài kiểm tra cuối khóa Ngành Thịnh Hưng Học

Professional Development

•

40 Qs

Domestic Gas Legislation Quiz

Professional Development

•

42 Qs

215 Week 11 Review

Professional Development

•

36 Qs

space

5th Grade - Professional Development

•

37 Qs

ISTQB Agile Tester Extension Exam Crash Course Part 3

Quiz

•

Science

•

Professional Development

•

Practice Problem

•

Medium

Hiếu Bồ

Used 12+ times

FREE Resource

40 questions

Show all answers

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

In Agile projects, there is a greater need for testers to understand and be competent in white box testing. Which out of the following TWO reasons best indicate why this is a more important skill on Agile projects than on traditional projects?

i. Agile team is cross-functional so all members can help in each other’s task. This also enables them to help developers.
ii. In Test Driven Development testers have to write the unit test first so the developers can write the code.
iii. Agile testing relies more on white box testing than black box testing.
iv.Testers can improve the program logic by pair programming.
v. In Agile projects, testers often work closely with developers for automation of unit tests and review of the code.

i & ii

ii & v

iv & v

i & v

Answer explanation

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Out of the following which are necessary skills for a Tester working on agile projects?

i. Competent in test automation.
ii. Competent in alpha/ beta testing.
iii. Competent in experience-based testing.
iv. Competent in unit testing.

i, ii and iii

i, ii, iii and iv

i and iii

i, iii and iv

Answer explanation

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Why is test automation a more necessary skill on Agile projects for Testers than on traditional projects? Select TWO reasons from following statements.

i. Features can change in future iterations. Automated tests are necessary to reduce the regression risk due to rapid changes.
ii. All feature validation testing should be done in the same iteration. In practice, that can only be realized by automated tests.
iii. Regression testing is a parallel process occurring throughout the iteration. This can only be achieved by automating the tests.
iv. All tests for the iteration are required to be finished in the iteration. This is not possible without Automation tests.
v. Agile testing relies more on white box testing than black box testing.

i & ii

ii & v

iv & v

i and iii

Answer explanation

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Out of the following which is NOT a typical task performed by the tester within Agile team?

To automate tests and maintain them.

To mentor and coach other team members.

To produce and update burndown charts.

To participate in code analyzing activities.

Answer explanation

In agile team scrum master typically updates the burndown charts and not the tester.

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Out of the following which is NOT a test related organization risk which Agile organizations may encounter?

Testers work so closely to developers that they lose the appropriate tester mindset.

Testers become tolerant about inefficient, ineffective, or low-quality practices within the team.

Testers cannot keep pace with the incoming changes in time-constrained iterations.

Testers spend more time on Automation related activities rather than on testing.

Answer explanation

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Which one of the following is a test related organization risk that Agile organizations may encounter?

Testers work so closely with developers that they lose the appropriate tester mindset.

Testers managing the test environment and the test data.

Testers providing feedback on process quality.

Testers helping the team on non-testing activities.

Answer explanation

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Which out of the following TWO are activities for the Tester on Agile projects but not necessarily on traditional projects?

i. Testers provide feedback on process quality.
ii. Understand, implement and update the test strategy.
iii. Actively collaborate with developers and business stakeholders.
iv. Testers provide feedback on product quality.
v. Automate and maintain Automation tests.

i & iii

iii & v

i & v

ii and iv

Answer explanation

Access all questions and much more by creating a free account

Create resources

Host any resource

Get auto-graded reports

Continue with Google

Continue with Email

Continue with Classlink

Continue with Clever

or continue with

Microsoft

Apple

Others

Already have an account?

Similar Resources on Wayground

36 questions

Specialist Appliance

Quiz

•

Professional Development

35 questions

18th December review

Quiz

•

Professional Development

36 questions

Quality_control

Quiz

•

Professional Development

35 questions

Philippine Electrical Code (PEC-1A)

Quiz

•

Professional Development

35 questions

lumbar and sacral plexus

Quiz

•

Professional Development

35 questions

GSC Spaghetti Pantry

Quiz

•

Professional Development

42 questions

Inteligencias múltiples tema 1

Quiz

•

Professional Development

40 questions

Kuis RT 14 2023

Quiz

•

Professional Development

Popular Resources on Wayground

15 questions

Fractions on a Number Line

Quiz

•

3rd Grade

20 questions

Equivalent Fractions

Quiz

•

3rd Grade

25 questions

Multiplication Facts

Quiz

•

5th Grade

54 questions

Analyzing Line Graphs & Tables

Quiz

•

4th Grade

$fractions$

22 questions

fractions

Quiz

•

3rd Grade

20 questions

Main Idea and Details

Quiz

•

5th Grade

20 questions

Context Clues

Quiz

•

6th Grade

15 questions

Equivalent Fractions

Quiz

•

4th Grade

Discover more resources for Science

20 questions

Black History Month Trivia Game #1

Quiz

•

Professional Development

100 questions

Screening Test Customer Service

Quiz

•

Professional Development

20 questions

90s Cartoons

Quiz

•

Professional Development

10 questions

Reading a ruler in Inches

Quiz

•

4th Grade - Professio...

16 questions

Parallel, Perpendicular, and Intersecting Lines

Quiz

•

KG - Professional Dev...

12 questions

Valentines Day Trivia

Quiz

•

Professional Development

ISTQB Agile Tester Extension Exam Crash Course Part 3

40 questions

Out of the following which are necessary skills for a Tester working on agile projects?
<p>
i. Competent in test automation.
ii. Competent in alpha/ beta testing.
iii. Competent in experience-based testing.
iv. Competent in unit testing.

Out of the following which is NOT a typical task performed by the tester within Agile team?

In agile team scrum master typically updates the burndown charts and not the tester.

Out of the following which is NOT a test related organization risk which Agile organizations may encounter?

Which one of the following is a test related organization risk that Agile organizations may encounter?

Out of the following which is NOT a typical task performed by the tester on Agile project?

Out of the following which is NOT a typical task performed by the tester on Agile project?

Access all questions and much more by creating a free account

Similar Resources on Wayground

Popular Resources on Wayground

Discover more resources for Science

ISTQB Agile Tester Extension Exam Crash Course Part 3

40 questions

Out of the following which are necessary skills for a Tester working on agile projects?<p> i. Competent in test automation. ii. Competent in alpha/ beta testing. iii. Competent in experience-based testing. iv. Competent in unit testing.

Out of the following which is NOT a typical task performed by the tester within Agile team?

In agile team scrum master typically updates the burndown charts and not the tester.

Out of the following which is NOT a test related organization risk which Agile organizations may encounter?

Which one of the following is a test related organization risk that Agile organizations may encounter?

Out of the following which is NOT a typical task performed by the tester on Agile project?

Out of the following which is NOT a typical task performed by the tester on Agile project?

Access all questions and much more by creating a free account

Similar Resources on Wayground

Popular Resources on Wayground

Discover more resources for Science

Out of the following which are necessary skills for a Tester working on agile projects?
<p>
i. Competent in test automation.
ii. Competent in alpha/ beta testing.
iii. Competent in experience-based testing.
iv. Competent in unit testing.