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.

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

<p>

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.

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

<p>

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.

Which tasks are typically expected of a tester within the Agile team?

<p>

i. Decide on user acceptance.

ii. Understanding, implementing and updating the test strategy.

iii. Prepare burndown charts

iv. Configuring, using, and managing test environments and test data.

v. Decide on the priority of the user story.

Which tasks are typically expected of a tester on the Agile project?

<p>

i. Decide on user acceptance.

ii. Design, create and execute appropriate tests.

iii. Schedule defect reports for analysis.

iv. Automate and maintain tests.

v. Improve program logic by pair programming.

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:

<p>

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.

<p>

Which TWO test quadrants would the above test cases be part of?

The Agile Manifesto has 4 statements of values. Match the agile value (1-4) with its traditional counterpart (i-iv).

<p>

1) Customer collaboration over.

2) Responding to change over.

3) Individuals and interactions over.

4) Working software over.

<p>

i) Processes and tools.

ii) Following a plan.

iii) Contract negotiation.

iv) Comprehensive documentation.

Which out of the following TWO statements demonstrate effective use of the testing quadrants?

<p>

1. The testing quadrants model and its variants help to ensure that all important test types and test levels are included in the development lifecycle

2. The tester can use the types of tests described in the testing quadrants as a coverage metric, the more tests covered from each quadrant, the higher the test coverage.

3. The testing quadrants model provides a way to differentiate and describe the types of tests to all stakeholders, including developers, testers, and business representatives.

4. Testing quadrants are used for risk analysis; with the lower level quadrants representing a lower risk to the customer.

5. Testing quadrants can be used to find out whether the story acceptance criteria is testable.

Given the following user stories:

<p>

“As a bank teller, I can easily navigate through the system menu and links, and find the information I am looking for”

<p>

“For all users, the system must display all queries in less than 2 seconds, 90% of the time”

<p>

And the associated test cases:

<p>

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.

<p>

Which TWO test quadrants would the above test cases be part of?

Match the testing quadrants on the left (1-4) with its correct test type on the right (i-iv).

<p>

1. Q1

2. Q2

3. Q3

4. Q4

<p>

i) Story test.

ii) Recovery test.

iii) Beta test.

iv) unit test.

Consider the following user story: “As a bank teller, I would like to be able to view all of my customer’s bank transactions on the screen, so I can answer his/her questions”. Out of the following which can be considered as relevant acceptance test cases?

<p>

i. Login as a bank teller, get the customer’s account balance for all open accounts.

ii. Login as a bank teller, enter a customer account ID, get his transactions history on the screen.

iii. Login as a bank teller, request customer account ID by using name abbreviations, and get his transaction history on the screen.

iv. Login as a bank teller, enter a customer IBAN (international bank account number), get his transaction history on the screen.

v. Login as a Bank Teller, enter a customer Account ID, get the transactions history in less than 3 seconds on screen.

Consider the following user story:

<p>

“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:

<p>

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?

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.

<p>

Out of the following which tester statements about testing quadrants are true?

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.

<p>

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.

<p>

What does organizational and behavioral best practices the team lack?

Review the Agile team descriptions followed by organization and behavioral practices and then answer the question.

<p>

1. Team (A): The team has agreed upon a Test process In the Release planning session but the testers are not following it for some of the testing activities in order to finish all stories included in the sprints.

2. Team (B): The testers actively participate in all daily stand-up and planning meetings but they are not invited to the retrospective meeting happening at the end of each iteration.

3. Team (C): The testers are reporting the testing progress to their Test Manager but the team is not using Agile task board for monitoring the development and testing tasks.

4. Team (D): The testers are new to the Agile methodology and they are not able to keep up with the changes during each iteration.

<p>

I. Transparent

II. Open to Feedback

III. Resilience

IV. Credible

<p>

Match the teams with the organizational and behavioral practices they are lacking?

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.

<p>

What is the best course of action for the testers to take?

Agile team is doing the quality risk analysis for the following user stories selected from the backlog items In an iteration planning session.

<p>

Match the stories with their respective quality risk based on the information below:

<p>

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.

Agile team is doing the quality risk analysis for three user stories selected from the backlog during an iteration planning session. <p>

Match the stories with their respective quality risk based on the information below:

<p>

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.

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

<p>

# 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

<p>

How can the team mitigate these risks during the iteration? Select TWO options.

Given the following results from a product risk analysis that occurred at the beginning of an iteration:

<p>

# 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

<p>

Which out of the following TWO describes best what the team should do with this information? Select TWO options.