ISTQB Foundation Level Agile Tester - Extension. Chapter 3

Reviewed by Editorial Team

The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.

Learn about Our Editorial Process

| By Kozakinvestment

Kozakinvestment

Community Contributor

Quizzes Created: 1 | Total Attempts: 276

| Attempts: 276

Quiz Flashcard

Questions

Feedback

During the Quiz End of Quiz

Difficulty

Sequential Easy First Hard First

1/62 Questions

Which of the following is TRUE about Test-First Development?
- Primarily unit level and code focused, helping the developer with a clearly defined expected result
- Helps to create better user stories
- Creates classes which can be used by developers to create automated test
- Helps to create reusable test for regression test suite.

About This Quiz

This quiz covers key concepts in agile testing methodologies such as Test-First Development, Test-Driven Development, Acceptance Test-Driven Development, and Behavior-Driven Development, essential for ISTQB Foundation Level Agile Tester - Extension.

Quiz Preview

2.

Which one is FALSE about Test-Driver Development ?
- Always automated and used in continuous integration.
- Primarily unit level and code focused
- Number of test cases increases with every new piece of code
- Helps with creating user stories
Correct Answer

A. Helps with creating user stories

Explanation

Test-Driven Development (TDD) is a software development approach where tests are written before the actual code. The given statement that TDD helps with creating user stories is false. TDD is primarily focused on unit level and code, ensuring that the code meets the defined requirements. It is not directly involved in creating user stories, which are typically part of the requirements gathering and analysis phase in Agile methodologies. TDD is automated and used in continuous integration to ensure that new code changes do not break existing functionality. The number of test cases may increase with every new piece of code to cover different scenarios and ensure comprehensive testing.

Rate this question:
3.

Which one is TRUE about Acceptance Test Driven development?
- Generate code that developers can use to create automated test cases
- Creates reusable test cases for regression suite
- Gained its popularity for XP programming approach
- All of them are true.
Correct Answer

A. Creates reusable test cases for regression suite

Explanation

Acceptance Test Driven Development (ATDD) is a software development approach where test cases are created before the code is developed. These test cases are based on the acceptance criteria defined by the stakeholders. One of the benefits of ATDD is that it creates reusable test cases for the regression suite. These test cases can be used to ensure that the software continues to function correctly after future changes or updates. Therefore, the statement "creates reusable test cases for regression suite" is true for Acceptance Test Driven Development.

Rate this question:
4.

Which one is false about acceptance-test driven development?
- Created during user story development, thus helping to create better user stories
- Helps stakeholder to understand how the software should behave
- Helps to define what the team needs to implement expected behavior
- Gives developer clearly defined expected result to code on.
- Helps to create reusable test cases for regression test suite.
Correct Answer

A. Gives developer clearly defined expected result to code on.

Explanation

Acceptance-test driven development (ATDD) is a software development approach where acceptance tests are created before the development of the software. These tests define the expected behavior of the software and help stakeholders understand how the software should behave. ATDD also helps to create better user stories by involving stakeholders in the development process. Additionally, ATDD helps to define what the team needs to implement in terms of expected behavior and creates reusable test cases for the regression test suite. However, it does not give the developer a clearly defined expected result to code on, as the developer still needs to write the code to meet the defined acceptance criteria.

Rate this question:
5.

Which of the following best describe Behavior Driven development ? i. tests are automated and included in continuous integration framework ii. tool generated code is used by developer to create automated test. iii. tests the expected behavior of the software, thus is easy for stakeholders to understand. iv. helps developer to collaborate in order to define accurate unit tests. v. creates reusable test cases for regression test suite.
- I,iii,iv
- Ii,iii,iv
- I,ii,iii
- I,iii,iv
Correct Answer

A. Ii,iii,iv

Explanation

Behavior Driven Development (BDD) is an approach that combines software development and testing. It focuses on testing the expected behavior of the software, making it easier for stakeholders to understand. BDD also encourages collaboration between developers to define accurate unit tests, helping to ensure the quality of the software. In BDD, tool-generated code is used by developers to create automated tests, which can be included in a continuous integration framework for automation. Therefore, the best description of BDD is that it involves ii, iii, and iv.

Rate this question:
6.

Which of the following methods are based on the testing principle of early testing and QA activities ? i. Making test cases before start coding (e.g. TDD,Acceptance test driven Development, BDD) ii. Test Pyramid technique, having a large number of tests at the bottom of the pyramid iii. Test quadrant approach , matching appropriate test types to corresponding test level.
- I only
- I, ii, and iii
- Ii and iii
- I and ii
Correct Answer

A. I and ii

Explanation

The correct answer is i and ii because both methods mentioned in options i and ii are based on the testing principle of early testing and QA activities. In option i, making test cases before start coding (e.g. TDD, Acceptance test driven Development, BDD) emphasizes the importance of writing tests before writing the actual code, ensuring that the code meets the desired requirements. In option ii, the Test Pyramid technique suggests having a large number of tests at the bottom of the pyramid, which represents unit tests, enabling early detection of bugs and issues. Therefore, both options i and ii align with the principle of early testing and QA activities.

Rate this question:
7.

What can be an effective use of testing Quadrants ?
- Ensure that all important test level and test types are included into the development lifecyle.
- Risk analysis for all application test types in various test level
- Making sure non-functional product quality is also considered alongside functional.
- Ensure that acceptance test are created before deploying build to test environment
Correct Answer

A. Ensure that all important test level and test types are included into the development lifecyle.

Explanation

The effective use of testing Quadrants ensures that all important test levels and test types are included in the development lifecycle. This means that the testing process is comprehensive and covers all necessary aspects of the software being developed. By using testing Quadrants, the development team can identify and address any potential gaps or weaknesses in the testing strategy, ensuring that the software is thoroughly tested and meets the required quality standards.

Rate this question:
8.

User Story: " When I execute the add function from line 2234 to 2270, there should not be any exception." TC1: compile and execute the integrated build and check the execution does not exceeds 3 seconds TC2: Run the unit test made before coding this section, within a tight loop until it passes Which quadrants matches the test cases developed above
- Q1 and Q2
- Q1 and Q4
- Q3 and Q4
- Q1 and Q4
Correct Answer

A. Q1 and Q4

Explanation

The test cases mentioned in the user story involve checking the execution time and running unit tests. These test cases fall into Quadrant 1 (Q1) and Quadrant 4 (Q4) of the Agile Testing Quadrants. Q1 focuses on tests that support the development process, such as unit tests, while Q4 focuses on tests that evaluate non-functional requirements, such as performance testing. Therefore, the correct answer is Q1 and Q4.

Rate this question:
9.

User Story: " When crashes, the system should restart to the latest known stable configuration. Moreover, having tested at user's location, the system should pass the acceptance test. " Which test quadrants are used to test the above user stories ?
- Q1+Q2
- Q1+Q2+Q3
- Q3+Q4
- Q1+Q4
Correct Answer

A. Q3+Q4

Explanation

disaster recovery + beta testing = Q4 and Q3

Rate this question:
10.

User story: " We need to archive data every month;therefore, we need to migrate data to our archival database from production database. In addition to this, because our application is very memory intensive, efficient use of memory is vital." Which test quadrant(s) is/are needed to test the user story?
- Q3 Only
- Q4 only
- Q1 and Q3
- Q2 only
Correct Answer

A. Q4 only

Explanation

The user story states that efficient use of memory is vital for the application. This requirement falls under the technical risks and performance category, which is covered in Quadrant 4 (Q4) of the Agile Testing Quadrants. Therefore, testing in Q4 is needed to ensure that the memory usage is optimized during the data migration process.

Rate this question:
11.

User story: " In our production environment, we are running other middleware and production web application. Sometimes they are run within the same web application server. User stories must be tested and any ambiguity must be resolved." Which Quadrants are used to test the user story ?
- Q1 and Q2
- Q3 and Q4
- Q2 and Q4
- Q3 and Q4
Correct Answer

A. Q2 and Q4

Explanation

The user story mentions that there are other middleware and production web applications running in the same web application server. This indicates that there may be dependencies and interactions between the user story and these existing components. Quadrant 2 (Technology Facing, Supporting) is used to test the user story against these existing components to ensure compatibility and integration. Quadrant 4 (Business Facing, Supporting) is used to test the user story against the production web application to ensure that it meets the business requirements and resolves any ambiguity. Therefore, the correct answer is Q2 and Q4.

Rate this question:
12.

In a release consisting of 8 iterations, during 5th iteration, two testers quit the team and joined another company. A major functionality was being developed and needed thorough testing. [ this is a situation from a Scrum team ] What are the best course of action for the team ?
- Higher specialized testing experts to get the testing done by end of the release
- Scrum team is cross functional. All the members should leverage on different skills they bring in.
- Move the major item to next iteration when stafffing issue is solved.
- Make the remaining testers to work hard to get the testing task done by end of the iteration.
Correct Answer

A. Scrum team is cross functional. All the members should leverage on different skills they bring in.

Explanation

In this situation, the best course of action for the team is to leverage the cross-functional nature of the Scrum team. Since two testers have quit, it may not be feasible to hire specialized testing experts at this point. Moving the major item to the next iteration when the staffing issue is resolved may delay the release. Instead, the remaining testers should work together and leverage their different skills to ensure thorough testing is done by the end of the iteration. This approach allows the team to adapt and collaborate effectively, ensuring the completion of the major functionality.

Rate this question:
13.

In the middle of 5th iteration, a scrum team found that more automated tests are needed for regression suite. How the scrum team will make decisions regarding automated test cases?
- Scrum masters makes technical decision regarding testing and test design.
- Work with existing automate test cases and automate remaining cases in next iteration.
- Testers should autoamte the test cases anyway because it can be reusable
- Must include the testers and decision regarding test design and implementation is made collaboratively
Correct Answer

A. Must include the testers and decision regarding test design and implementation is made collaboratively

Explanation

The correct answer is that the scrum team must include the testers and make decisions regarding test design and implementation collaboratively. This means that the team as a whole, including the testers, will discuss and decide on how to approach the automation of test cases. This ensures that the testers' expertise and insights are taken into account and that the decisions made are agreed upon by the entire team.

Rate this question:
14.

Stakeholders and customer representatives are very skeptical regarding the effectiveness of the tests designed for their system. They want to make sure that at the end of the iterations, the released software must be stable, robust, and meet their functional needs. What would be testers contribution to satisfy customer regarding the testing approach?
- Apply more white box testing than black box testing
- Design the tests so that there is mix of black box and white box test cases
- Provide information to the stakeholders regarding the testing process
- Do more user acceptance tests than any other tests.
Correct Answer

A. Provide information to the stakeholders regarding the testing process

Explanation

Testers can contribute to satisfying customers regarding the testing approach by providing information to the stakeholders regarding the testing process. By keeping the stakeholders informed about the testing activities, progress, and results, testers can help build trust and confidence in the effectiveness of the tests. This transparency allows stakeholders to understand the steps being taken to ensure that the released software is stable, robust, and meets their functional needs.

Rate this question:
15.

While creating functional test cases, a tester found out that not all information necessary are available in the available documentation. What the tester would do to create test cases ? Assume this tester is a part of Scrum team.
- Continue developing test cases based on the available information
- Acquire necessary information actively without relying on what is available
- Consult with the Scrum master to decide what to do with it.
- Postpone those test cases for later iterations.
Correct Answer

A. Acquire necessary information actively without relying on what is available

Explanation

The tester, being a part of the Scrum team, would actively acquire the necessary information instead of relying solely on what is available in the documentation. This proactive approach ensures that the test cases are comprehensive and cover all the required aspects. By actively seeking the required information, the tester can gather a complete understanding of the functionality being tested and create effective test cases. This approach aligns with the agile principles of collaboration, continuous improvement, and adaptability.

Rate this question:

1
16.

To maintain visibility, what a tester can setup during Spring zero ? i. create task board ii. create burndown charts. iii. specify the definition of done iv. Define when to continue or stop testing before delivery
- I,ii,iii
- Ii,iii,iv
- I,ii,iv
- I,iii,iv
Correct Answer

A. I,iii,iv

Explanation

Burn down chart is created by Scrum Master, not tester.

Rate this question:
17.

In a project following Scrum, business stakeholders likes to know test progress and product quality as development proceeds through iterations. What is the role of a tester in Spring zero to enable producing such reports
- Define test metrics to measure test process,test progress and product quality
- Execute alpha test and beta test with customer representative
- Do customer survey or test process and product quality.
- Involve customers in daily standup meetings.
Correct Answer

A. Define test metrics to measure test process,test progress and product quality

Explanation

The role of a tester in Scrum is to define test metrics that can measure the test process, test progress, and product quality. These metrics will provide insights into the effectiveness of the testing activities and the overall quality of the product. By establishing these metrics, the tester can generate reports that will inform the business stakeholders about the progress and quality of the product as it goes through iterations. This allows the stakeholders to have visibility into the testing process and make informed decisions based on the test metrics provided.

Rate this question:
18.

In order provide information regarding the test process to stakeholders, testers would like to identify which test session to peroform, show test strategies and describe test data. Which of the following tool/approach they can use to do that? i, Incremental design ii. Pair programming. iii. task board iv. Mind Mapping.
- Iii only
- I and iv
- Iv only
- Iii and iv
Correct Answer

A. Iv only

Explanation

Testers can use the approach of Mind Mapping to provide information regarding the test process to stakeholders. Mind Mapping is a visual tool that helps in organizing and presenting information in a structured and easily understandable manner. It allows testers to identify the test session, show test strategies, and describe test data effectively. Therefore, the correct answer is "iv only."

Rate this question:
19.

An Agile team has done all the necessary tasks to identify quality risks, categorize risks and assess risk level, estimate efforts according to risk level and selected strategy to mitigate risks. In the middle of the iteration, customer came up with a set of new requirements and changes to user stories selected for the current iteration. What should the team do in terms of keeping risk low?
- Since the changes came in the middle of the iteration, postpone change to next iteration
- Re assess risk by identifying new risk, the risk level and the mitigation strategy
- If new requirements are high risk items, only then can they be included in current iteration
- Stop the selected tasks for the iteration and start working on the new changes to finish it by end of iteration
Correct Answer

A. Re assess risk by identifying new risk, the risk level and the mitigation strategy

Explanation

In order to keep the risk low, the team should reassess the risks by identifying any new risks that may arise from the changes in requirements. They should also evaluate the risk level associated with these new requirements and determine the appropriate mitigation strategy. This ensures that the team remains proactive in managing risks and can make informed decisions about incorporating the changes into the current iteration.

Rate this question:
20.

User story: When a user search for books in the system, it should not take more than 3 seconds. The search functionality should be easy to use. In case the web server crashes, the system should be back within 2 minutes. Any new functionality should be modularized and added to existing build module by module. The web application should not interfare with other web application running under the same container. Categorize all the risk factors for the above user stories.
- Performance, usability, recovery, scalability, interoperability
- Performance, usability, functionality, interoperability,scenario
- Usability, functionality, process flow, prototyping, scalability
- Load and stress, security, memory management, disaster, interoperability.
Correct Answer

A. Performance, usability, recovery, scalability, interoperability

Explanation

The risk factors for the given user stories include performance, usability, recovery, scalability, and interoperability. These factors are important in ensuring that the system meets the user's expectations in terms of search speed, ease of use, system availability in case of crashes, ability to handle increasing load, and compatibility with other web applications running under the same container.

Rate this question:
21.

While doing quality risk analysis for an Agile project , the team has done the following actions as part of the analysis process: 1. Gather all team members, 2. list all product backlog item 3. Asses risk level for all risk items 4. estiamte test effort according to risk level 5 select strategy to mitigate risk. What is missing from the above process?
- Survey customer regarding the risks
- Hire outside consultant to do expert based risk analysis
- Idenitfy quality risk associated with the backlog items.
- Nothing is missing from the stated process.
Correct Answer

A. Idenitfy quality risk associated with the backlog items.

Explanation

The missing element from the given process is to identify the quality risks associated with the backlog items. The team has gathered all team members, listed all product backlog items, assessed the risk level for all risk items, estimated test effort according to risk level, and selected a strategy to mitigate risk. However, they have not specifically identified the quality risks associated with the backlog items. This step is crucial in order to fully understand and address any potential risks to the quality of the project.

Rate this question:
22.

Which is true about risk mitigating process taken during iteration? i. high risk items are done first ii. low risk items are done last iii. planning poker session can be done to decide which risk item to mitigate when. iv. Scrum master decides what is the best option to mitigate risks.
- I, ii, iii
- I and ii
- Iii and iv
- I and iv
Correct Answer

A. I and ii

Explanation

During the risk mitigating process taken during an iteration, it is true that high-risk items are done first (i) and low-risk items are done last (ii). This approach allows the team to address the most critical risks early on, reducing the potential impact on the project. Additionally, it ensures that lower-risk items are tackled towards the end, minimizing the chances of any significant disruptions. The answer does not include (iii) or (iv), as planning poker sessions can be used to prioritize tasks but not specifically for risk mitigation, and the Scrum master does not solely decide the best option to mitigate risks as it is a collaborative effort.

Rate this question:
23.

During a release planning session, the agile team is breaking down stories into smaller stories for better understanding. In order to do that, they need to measure how many story points are there. What strategy they can follow to effectively find story points for a particular story?
- Planning poker session or any consensus based strategy.
- Rely on the understanding of the business representative to measure story points
- Product owner is responsible to find out story points.
- It is developer's responsibility since they'll be developing story points.
Correct Answer

A. Planning poker session or any consensus based strategy.

Explanation

During a release planning session, the agile team can effectively find story points for a particular story by using a planning poker session or any consensus-based strategy. This involves the team members collectively estimating the effort required for each story and coming to a consensus on the story points. This approach ensures that multiple perspectives are considered and helps in better understanding and breaking down the stories into smaller ones. It promotes collaboration and involvement of the entire team in the estimation process, leading to more accurate and reliable story point measurements.

Rate this question:
24.

Some functionalities are introduced to existing application. These new functionality may affect previous functionality. The context is changed also for some new business domain introduced to the application. Possibility is there for some old defects to re appear in the new added functionality. Which of the following would provide relevant information as test basis? i. Experience from previous project. ii. Code, architecture and design. iii. User profile, system configuration etc. iii. customer survey iv. Information on defects from current and previous defects v. Industry Standard Guideline.
- I,ii,iii
- Iii,iv,v
- I,iii,iv
- I,iv,v
Correct Answer

A. I,iii,iv

Explanation

The correct answer is i, iii, and iv. Experience from previous projects would provide relevant information as it can help identify potential issues and defects that may reappear in the new functionality. User profile, system configuration, and other contextual information are also important as they can help determine if the new functionality would work effectively in different scenarios. Information on defects from current and previous projects is crucial as it can help identify any existing issues that may affect the new functionality.

Rate this question:
25.

During iteration planning of 5th iteration, the team saw that the same kind of bugs from iteration 3 and 4 might come up as the selected features are similar to those from iteration 3 and 4. Which of the following would ease the creation of test cases in iteration 5 ?
- Existing application's feature, functions and requirements
- A defect taxonomy of categorization of defects
- Quality risk
- Industry standard documentation.
Correct Answer

A. A defect taxonomy of categorization of defects

Explanation

A defect taxonomy of categorization of defects would ease the creation of test cases in iteration 5 because it provides a systematic way to classify and categorize different types of defects. This taxonomy helps the team to identify and prioritize the types of defects that are likely to occur based on the similarities with previous iterations. By having a clear understanding of the types of defects that are likely to occur, the team can create targeted test cases that focus on those specific areas, improving the efficiency and effectiveness of the testing process.

Rate this question:
26.

Testers in an agile project are developing use case testing as a part of black box testing strategy. Which of the following test basis would likely to help testers to device use case test cases?
- System configuration
- User behavior
- Information on defect from previous and present projects
- A categorization of defect taxonomy.
Correct Answer

A. User behavior

Explanation

User behavior would likely help testers to devise use case test cases because understanding how users interact with the system and the actions they perform can help identify the different scenarios and paths that need to be tested. By considering user behavior, testers can ensure that the use case test cases cover a wide range of realistic user interactions and validate that the system functions correctly in various user scenarios.

Rate this question:
27.

Which of the followings are example of testable acceptance criteria? i. The user interface should look nice ii. The web application should be functional in the major browsers: firefox, chrome, safari and IE iii. A user cannot purchase until his/her email address has been verified. iv. Most of the testers should perform their own exploratory testing on the system. v. Login operation should never exceeds 0.5 second.
- I,ii,v
- I,iii,v
- Ii,iii,iv
- Ii,iii,v
Correct Answer

A. Ii,iii,v
28.

Which of the followings are NOT examples of testable acceptance criteria. i. team should use both equivalence partitioning and use case to design test cases. ii. The application should be easy to navigate and intuitive. iii. No major faults are found after testing. iv. the size of the executable files should not be too big v. No faults are found after testing.
- I,iii,v
- Ii,iii,iv
- I,iii,iv
- I,iv,v
Correct Answer

A. I,iii,iv

Explanation

Testable acceptance criteria are those that can be objectively measured or verified through testing. Option i is not testable because it states a method or approach to designing test cases, rather than a specific criteria that can be tested. Option iii is not testable because it states a desired outcome (no major faults found), but does not provide specific criteria or metrics for determining what constitutes a major fault. Option iv is not testable because it does not provide specific criteria or metrics for determining what is considered "too big" for the size of the executable files.

Rate this question:
29.

Which of the following are testable acceptance criteria ? i. The final executable archive file should be less than 1GB. ii. the executable web application file should be able to be ran in all open source web container. iii. The web container must be open source. iv. the market data (external) must come from New York Stick Exchange Only. v. Unless the user is an administrator, no one should be able to change user's date of birth.
- I,iii,iv,iv
- I,ii,iii,
- Ii only
- I,ii,iii,iv,v
Correct Answer

A. I,iii,iv,iv

Explanation

The given acceptance criteria that are testable are:
i. The final executable archive file should be less than 1GB.
iii. The web container must be open source.
iv. The market data (external) must come from New York Stick Exchange Only.

These criteria can be tested because they are specific and measurable. The first criterion can be tested by checking the size of the executable archive file after it is created. The third criterion can be tested by verifying if the web container used is open source. The fourth criterion can be tested by ensuring that the market data used is sourced only from the New York Stick Exchange.

Rate this question:
30.

Before releasing the software, at the end of all the iterations, all the coverage dimensions have been measured, reported and satisfied; the consequence of remaining risk is understood and within accepted level; and the cost would surpass the expected gain from this release. What would be the best option for the team ?
- Calculated total expected should always be lower than total cost. so reduce cost before release or increase sell
- The finishing date can be considered as a major reason to use as release criteria
- Since there are still quality risk left, more testing should be done to mitigate ALL risk , then release it
- None of the above is valid options for this agile team.
Correct Answer

A. Calculated total expected should always be lower than total cost. so reduce cost before release or increase sell

Explanation

The given answer is the best option for the team because it suggests that the calculated total expected should always be lower than the total cost. This means that the team should either reduce the cost before release or increase the selling price in order to ensure that the expected gain from the release outweighs the cost. This approach ensures that the team is making a profitable decision and considering the financial aspect of the release.

Rate this question:
31.

User Story: " As a student, I should be able to retake any course with a grade point of C+ or lower. " Among the following test cases, which ones are relevant test cases? i. Select a course with grade above C+ and try to register. The system should prevent from registering. ii. Select a course with grade below C+. The registration process should take no more than 1 second. iii. with ten thousand students, registering one course should not take more than 3 seconds. iv. Select a course with grade point C+ or lower. Student should be able to register for the course. v. An Administrator can select a course with grade point C+ or lower for a student. The admin should be able to register that course for this student.
- I,iii,v
- I,ii,iii
- I,iv,v
- I and iv only
Correct Answer

A. I and iv only

Explanation

Test case i is relevant because it checks if the system prevents a student from registering for a course with a grade above C+. This is important to ensure that the system correctly enforces the requirement.

Test case iv is relevant because it checks if a student is able to register for a course with a grade point of C+ or lower. This is the main requirement stated in the user story, so it is crucial to verify that it is working correctly.

Test case ii is not relevant because it does not directly test the requirement mentioned in the user story.

Test case iii is not relevant because it focuses on performance rather than the functionality of allowing students to retake a course.

Test case v is not relevant because it involves an administrator, which is not mentioned in the user story.

Rate this question:
32.

An Agile team would like to implement Acceptance test first development. This is the workflow that they follow to implement that. Create user story->make test cases from user stories-> execute both positive and negative tests-> verify tests-> solve bugs->integrate. However, while testing, they found out that there were some misunderstanding in the user stories;therefore, the tests cases that followed did not reflect what the user originally wanted. What the team should have had done ?
- They should have let business representative only to write user stories.
- Since developers do the coding, they should have written the user stories
- Conduct specification workshop where storeis are analyzed, discussed and written collaboratively
- Acceptance Test Driven development is not suitable for all type of project.
Correct Answer

A. Conduct specification workshop where storeis are analyzed, discussed and written collaboratively

Explanation

The team should have conducted a specification workshop where the user stories are analyzed, discussed, and written collaboratively. This would have allowed the team to clarify any misunderstandings in the user stories and ensure that the test cases accurately reflect what the user originally wanted. By involving all stakeholders, including the business representative and developers, in the specification workshop, the team can ensure a shared understanding and prevent further issues with misunderstood requirements.

Rate this question:
33.

User Story: " When 50000 users use the system simultaneously, the response time should be less than 1 second. TC1: Simulate the condition with 70000 users. Check the response time and it should be more than 1 second. TC2: Simulate the condition with 50000 users. Check the response time and it should be less than 1 second. TC3: Simulate the condition with 40000 users. Check the response time and it should be well below 1 second. Which test case is suitable for testing the user story?
- TC1 only
- TC2 only
- TC2 and TC3
- TC1 , TC2 and TC3
Correct Answer

A. TC1 only

Explanation

While doing acceptance testing, we should use negative test cases to test non-functional user stories.

Rate this question:
34.

User Story: " As a manager, I am the only person who is able to see employee's salary." TC1: Login as manager, search for employee's profile and verify that salary is displayed. TC2: Login as administrator, search for employees profile and verify that the salary is displayed. TC3: Login as employee, search for another employee's profile and verify that the salary is NOT displayed. TC4: Login as employee, search for his own profile and verify that the salary is displayed Which test cases can we use to verify test cases?
- All of them.
- Except TC2, because it is a negative test case
- TC1
- TC2,TC3,TC4
Correct Answer

A. All of them.

Explanation

We can use both negative and positive test cases to verify acceptance tests.

Rate this question:
35.

User Story: " as an employee, I should be able to print my pay stub." TC1: Login as employee, select the pay stub to print, click on print and verify that the physical copy is ready." TC2:Login as employee, select the pay stub to print , click on print and the printing should be done by 3 minutes. TC3: Login as manager, select the pay stub to print, click on print and verify that the physical copy is ready. Which test case can we use to verify the user story?
- TC1 only
- TC2 and TC3
- TC3 only
- TC1,TC2 and TC3
Correct Answer

A. TC1 only

Explanation

test cases should not add to the story. The story says nothing about performance nor did it say anything about what would happen when a manager wants to print.

Rate this question:
36.

User Story: " The system should calculate grade based on the following criteria. A :93-100 A- :90-93 B+:87-90 B :83-87 B- :80-83" Which black-box testing will be ideal to test above story ?
- Equivalence partitioning
- State Transition Diagram
- Decision table
- User Case test
Correct Answer

A. Equivalence partitioning

Explanation

Equivalence partitioning would be the ideal black-box testing technique to test the given user story. This technique involves dividing the input values into different equivalence classes and selecting representative test cases from each class. In this case, the input values can be divided into different equivalence classes based on the grade ranges mentioned. For example, one equivalence class could be grades between 93-100, another could be grades between 90-93, and so on. By selecting test cases from each equivalence class, we can ensure that the system calculates the grade correctly for different ranges of input values.

Rate this question:
37.

User Story:"When I click on Utilities, the screen should display the following items: calculator, watch,weather and map. Clicking on the watch should bring Alarm screen first." Which black box testing is idea to test above user story?
- 100% statement coverage
- State Transition Diagram/Table
- Decision table
- Equivalence partitioning
Correct Answer

A. State Transition Diagram/Table

Explanation

A State Transition Diagram/Table is ideal to test the given user story because it helps in capturing and visualizing the different states and transitions that the system can go through. In this case, the diagram/table can represent the different screens and their transitions based on user actions. It can help ensure that when the user clicks on Utilities, the correct items (calculator, watch, weather, and map) are displayed, and when the user clicks on the watch, the Alarm screen is shown first. This testing approach can ensure that the system behaves as expected and follows the specified transitions accurately.

Rate this question:
38.

User story: " As a manager, I should be able to add, delete, modify, update and print all employees record." Which blackbox testing is idea to test above user story?
- State trasition testing
- Decision table testing
- User case testing
- Boundary Value tests
Correct Answer

A. User case testing

Explanation

User case testing is the ideal blackbox testing technique to test the given user story. This technique involves creating and executing test cases based on different scenarios or use cases that the manager may encounter while adding, deleting, modifying, updating, and printing employee records. User case testing ensures that the system functions correctly and meets the requirements specified in the user story.

Rate this question:
39.

User Story: " The insurance premium should be calculated according to the following rules: i. if user is a UK resident and over 30 years of age, he will get 30% off of his/her premium. ii. UK resident but below 30 years of age, 10% off of his/her premium. iii. Not a UK resident but over 30 years of age, no discount. Which black box testing strategy is idea to develop test cases for the above user story?
- Decision table
- State transition
- User case
- 100% decision coverage
Correct Answer

A. Decision table

Explanation

The correct answer is decision table because a decision table is a systematic and structured way to capture all possible combinations of conditions and corresponding actions or outcomes. In this user story, there are multiple conditions (UK resident, age over 30) and corresponding discounts, so a decision table would be an ideal strategy to develop test cases and ensure that all possible scenarios are covered.

Rate this question:
40.

An exploratory tester would like to see how the system behaves when it crashes and how fast it recovers from that state. What strategy he/she can follow to do this exploratory test? i Boundary value ii. CRUD(Create, Update, Delete, Read) iii. Interruptions(e.g. on, off, shutdown reboot) iv. Configuration change.
- I,ii,iii
- III only
- Ii,iii,iv
- Iii and iv
Correct Answer

A. III only

Explanation

To test how the system behaves when it crashes and how fast it recovers, an exploratory tester can follow the strategy of testing interruptions. This involves intentionally causing interruptions in the system, such as turning it on and off, shutting it down, or rebooting it. By observing how the system responds to these interruptions and how quickly it recovers, the tester can gain insights into its crash behavior and recovery time. This strategy aligns with option III, which is the correct answer.

Rate this question:
41.

After an unsuccessful exploratory testing session, the testers wanted to figure out the way to make better test cases to find more errors. What the tester should be doing in future to make that happen?
- Use heuristics to design tests
- Asks more relevant, quality questions regarding the system
- Never document anything as it wastes time in case of exploratory testing
- None of the above
Correct Answer

A. Asks more relevant, quality questions regarding the system

Explanation

To make better test cases and find more errors, the tester should focus on asking more relevant and quality questions regarding the system. This will help them gain a deeper understanding of the system and identify potential areas of weakness or vulnerabilities that can be targeted during testing. By asking targeted questions, the tester can create more effective test cases that are designed to uncover potential errors or issues in the system.

Rate this question:
42.

The testing team is performing exploratory testing based on the following information. "When I am logged in as a manager, I should be able to see and edit/update employees' salary." What is the above information correspond to? i. Test Charter ii. Test condition. iii. test cases. iv. test procedure specification.
- I and iii
- I and ii
- Ii and iii
- I and iv
Correct Answer

A. I and ii

Explanation

The given information corresponds to both a test charter and a test condition. A test charter defines the scope and objectives of the testing, while a test condition specifies the specific criteria that need to be met in order to consider a test case as passed. In this case, the information states the objective of being able to see and edit/update employees' salary when logged in as a manager, which can be considered as both the test charter and the test condition.

Rate this question:
43.

Sample test charter: " Only the developer will use this system to submit their code. The purpose of this software is to implement continuous integration and the system is vital to the day to day task of the agile time." Which of the items of test charter are missing from above ? i. Reference, ii. Data iii. Priority iv. Purpose v. Oracle Notes
- Ii,iii,v
- I,iii,iv
- I,ii,v
- I,ii,iii
Correct Answer

A. I,ii,v

Explanation

The given test charter is missing the items of reference, data, and oracle notes. The reference provides information about any documents or resources that are relevant to the testing process. Data refers to the specific inputs or datasets that will be used for testing. Oracle notes are explanations or instructions that help in determining the expected results or behavior of the system.

Rate this question:
44.

Why some agile team opt out for all inclusive tool such as application life-cycle management or task management tool?
- It provides functions such as dashboard, task board and burndown charts
- It can automate continuous integration , which is vital to agile approach
- It can find more bugs than other tools
- None of the above
Correct Answer

A. It provides functions such as dashboard, task board and burndown charts

Explanation

Agile teams may opt for an all-inclusive tool like application life-cycle management or task management tool because it provides functions such as a dashboard, task board, and burndown charts. These features are essential for effective project management and tracking progress in an agile approach. Additionally, these tools can automate continuous integration, which is crucial for maintaining a fast and efficient development process. The statement that the tool can find more bugs than other tools is not a valid reason for opting for an all-inclusive tool, as bug-finding capabilities can vary across different tools.

Rate this question:
45.

Why configuration management tools are important to agile team?
- It can be integrated in continuous integration process
- Due to automation at all levels and importance of managing associated test artifacts
- Quick update of project status
- Helps in efficient interation planning
Correct Answer

A. Due to automation at all levels and importance of managing associated test artifacts

Explanation

Configuration management tools are important to agile teams because they enable automation at all levels and help in managing associated test artifacts. These tools allow for the seamless integration of configuration management into the continuous integration process, ensuring that changes to the project are quickly and efficiently updated. By automating various tasks and processes, these tools aid in efficient iteration planning and ensure that the project status is easily and accurately tracked. Additionally, they play a crucial role in managing and organizing test artifacts, ensuring that they are properly versioned and easily accessible to the team.

Rate this question:
46.

Which of the following is NOT a purpose served by Application life cycle management tool?
- Record user stories along with their development and test tasks.
- Help in efficient iteration planning session
- Create, maintain and share knowledge base
- Automatically calculate a current estimated snapshot of user stories.
Correct Answer

A. Create, maintain and share knowledge base

Explanation

The purpose of an Application life cycle management tool is to record user stories along with their development and test tasks, help in efficient iteration planning sessions, and automatically calculate a current estimated snapshot of user stories. However, creating, maintaining, and sharing a knowledge base is not a purpose served by this tool.

Rate this question:
47.

Which are the main reason to use configuration management tool? i. Traceability ii. Rapid Changed ( e.g. code chum) iii. server availability iv. Reduce communication cost v. test design and analysis
- I and iv
- I,ii and iii
- I and ii
- Ii and v
Correct Answer

A. I and ii

Explanation

The main reasons to use a configuration management tool are traceability and rapid changes. Traceability allows for tracking and managing changes made to the system, ensuring accountability and facilitating troubleshooting. Rapid changes, such as code churn, can be efficiently managed and controlled using a configuration management tool, ensuring smooth development and deployment processes.

Rate this question:
48.

Which tool will be helpful to provide server snapshot in order for the developers to solve bugs?
- Cloud computing and virtualization tool
- Video capturing tool
- Wiki and wiki style dashboard
- Test case management tool
Correct Answer

A. Cloud computing and virtualization tool

Explanation

A cloud computing and virtualization tool can provide a server snapshot, which is a complete copy of the server's current state, including all configurations and data. This snapshot can be used by developers to analyze and debug any issues or bugs that may be present in the server. By having a snapshot of the server, developers can easily replicate the environment and test different scenarios without affecting the live server. This tool allows for efficient troubleshooting and problem-solving, making it helpful for developers in solving bugs.

Rate this question:
49.

Which tool allow business staff and developers to express product behavior using natural language and defined keywords
- Test design tool
- Test execution tool
- Test case management tool
- Virtualization tool
Correct Answer

A. Test execution tool

Explanation

A test execution tool allows business staff and developers to express product behavior using natural language and defined keywords. This tool allows them to write and execute test cases in a way that is easily understandable and accessible to both technical and non-technical team members. It provides a platform for collaboration and communication between different stakeholders involved in the testing process, enabling them to effectively express and validate the desired behavior of the product.

Rate this question:

Quiz Review Timeline (Updated): Mar 20, 2023 +

Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.

Current Version
Mar 20, 2023

Quiz Edited by
ProProfs Editorial Team
Apr 10, 2019

Quiz Created by
Kozakinvestment

ISTQB Foundation Level Agile Tester - Extension. Chapter 3

Which of the following is TRUE about Test-First Development?

Quiz Preview

Which one is FALSE about Test-Driver Development ?

Which one is TRUE about Acceptance Test Driven development?

Which one is false about acceptance-test driven development?

What can be an effective use of testing Quadrants ?

User Story: " When crashes, the system should restart to the latest known stable configuration. Moreover, having tested at user's location, the system should pass the acceptance test. " Which test quadrants are used to test the above user stories ?

User story: " In our production environment, we are running other middleware and production web application. Sometimes they are run within the same web application server. User stories must be tested and any ambiguity must be resolved." Which Quadrants are used to test the user story ?

In a release consisting of 8 iterations, during 5th iteration, two testers quit the team and joined another company. A major functionality was being developed and needed thorough testing. [ this is a situation from a Scrum team ] What are the best course of action for the team ?

In the middle of 5th iteration, a scrum team found that more automated tests are needed for regression suite. How the scrum team will make decisions regarding automated test cases?

While creating functional test cases, a tester found out that not all information necessary are available in the available documentation. What the tester would do to create test cases ? Assume this tester is a part of Scrum team.

To maintain visibility, what a tester can setup during Spring zero ? i. create task board ii. create burndown charts. iii. specify the definition of done iv. Define when to continue or stop testing before delivery

In a project following Scrum, business stakeholders likes to know test progress and product quality as development proceeds through iterations. What is the role of a tester in Spring zero to enable producing such reports

Which is true about risk mitigating process taken during iteration? i. high risk items are done first ii. low risk items are done last iii. planning poker session can be done to decide which risk item to mitigate when. iv. Scrum master decides what is the best option to mitigate risks.

During a release planning session, the agile team is breaking down stories into smaller stories for better understanding. In order to do that, they need to measure how many story points are there. What strategy they can follow to effectively find story points for a particular story?

During iteration planning of 5th iteration, the team saw that the same kind of bugs from iteration 3 and 4 might come up as the selected features are similar to those from iteration 3 and 4. Which of the following would ease the creation of test cases in iteration 5 ?

Testers in an agile project are developing use case testing as a part of black box testing strategy. Which of the following test basis would likely to help testers to device use case test cases?

User Story: " The system should calculate grade based on the following criteria. A :93-100 A- :90-93 B+:87-90 B :83-87 B- :80-83" Which black-box testing will be ideal to test above story ?

User Story:"When I click on Utilities, the screen should display the following items: calculator, watch,weather and map. Clicking on the watch should bring Alarm screen first." Which black box testing is idea to test above user story?

User story: " As a manager, I should be able to add, delete, modify, update and print all employees record." Which blackbox testing is idea to test above user story?

After an unsuccessful exploratory testing session, the testers wanted to figure out the way to make better test cases to find more errors. What the tester should be doing in future to make that happen?

Why some agile team opt out for all inclusive tool such as application life-cycle management or task management tool?

Why configuration management tools are important to agile team?

Which of the following is NOT a purpose served by Application life cycle management tool?

Which are the main reason to use configuration management tool? i. Traceability ii. Rapid Changed ( e.g. code chum) iii. server availability iv. Reduce communication cost v. test design and analysis

Which tool will be helpful to provide server snapshot in order for the developers to solve bugs?

Which tool allow business staff and developers to express product behavior using natural language and defined keywords