You are testing a new feature in the current iteration. The feature is supposed to take the input of a name and return the number of characters in the name. This information is used by another feature that will determine the size needed on a form.
The acceptance criteria state the following
1) a name of up to 30 characters should be accepted
2) standard error processing should be in place to limit user errors
The developers are using TDD and you have asked to see their tests.
This is what they gave you
When you run your manual tests you are finding that when you use the following inputs you get the associated results:
From these results what can you conclude about the TDD process?
- A . The developers are not running the tests prior to releasing the code
- B . The tests cannot be passing
- C . The tests are insufficient and need to include more options
- D . The story needs to be enhanced to include the capabilities that are causing errors
C
Explanation:
The TDD process, as described, seems to lack comprehensive testing that covers all the acceptance criteria. Specifically, the tests provided by the developers do not address the full range of input validation, such as ensuring that names with up to 30 characters are accepted and that standard error processing is in place to limit user errors. This indicates that the tests are insufficient and need to include more options to fully validate the feature against its acceptance criteria. The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria within an Agile team and implementing various Agile test approaches using appropriate techniques12. It also highlights the need for supporting and contributing to test automation activities in an Agile project12, which includes ensuring that all acceptance criteria are met and that tests are sufficiently robust to catch potential errors.
Reference:
ISTQB Advanced Level Agile Technical Tester Syllabus1
ISTQB Advanced Level Agile Technical Tester Learning Objectives2
You have been given the following story
As a shopper
I want to scan my membership card
So that I get all the discounts I’m entitled to receive
Which of the following is the correct use of BDD to design test scenarios?
- A . Given that the shopper scans their card
When they checkout
Then they should receive alt the quantity discounts for everything they have purchased - B . As a store clerk
I want to scan a customer’s card
So that their total includes their discounts - C . Given that I have scanned my card
I expect to receive my discounts
And an itemized list of what I bought - D . Given that a card is scanned
Then discounts should be applied
When the customer checks out
A
Explanation:
The correct use of Behavior-Driven Development (BDD) to design test scenarios involves specifying the behavior in a given-when-then format. This format helps to clarify the conditions under which a particular outcome should occur.
Option A follows this structure correctly:
Given that the shopper scans their card (the precondition), When they checkout (the action),
Then they should receive all the quantity discounts for everything they have purchased (the expected outcome).
This scenario clearly outlines the behavior of the system in response to the user’s actions, which is central to BDD.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria for a given user story using requirements engineering and test techniques, which include the application of BDD in the context of a given user story12.
You have received this BDD test
Given that a customer enters the correct PIN When they request to make a withdrawal And they have enough money in their account Then they will receive the money And a receipt
Which of the following is the user story that best fits this BDD test?
- A . As a customer
I want to deposit money into my account
So that I can collect interest - B . As an ATM
I want to provide services to my customer
So they will be happy - C . As a customer
I want to withdraw money from my account
So that I can buy a present - D . As a bank teller
I want customers to use the ATM
So that I don’t have to deal with them
C
Explanation:
The BDD test scenario provided describes a customer performing a withdrawal transaction after entering the correct PIN and having sufficient funds in their account. The outcome is the customer receiving money and a receipt. This aligns with the user story in option C, which focuses on the customer’s desire to withdraw money for a specific purpose, which is to buy a present. The other options do not match the actions described in the BDD test scenario.
Reference = The answer is verified based on the ISTQB Advanced Level Agile Technical Tester documents which emphasize the importance of aligning BDD scenarios with the corresponding user stories to ensure that the tests reflect the user’s needs and interactions with the system12.
You have been working as a tester in an Agile team You have found that the user stories are being defined by the team but it is still unclear what will be a successful outcome Even after story elaboration you are still unclear as to what a story should do As a result, you’re not really sure what to test or to know when you’ll be done with testing This problem is becoming worse as completed stories are showcased but the product owner is unhappy with the results
You’ve looked into the matter further and the comments from the product owner indicate that features are missing from the stories. The story is functioning correctly within the limited definition of the story but the product owner is expecting more functionality, such as error handling that isn’t being defined in the story
What technique should you implement that would help to further define the product owner’s expectations and alleviate the issues that are arising during the show cases?
- A . TDD by the developers before they begin coding
- B . BDD by the developers when unit tests are being created
- C . ATDD by the team to better define the requirements
- D . A combination of TDD and BDD by the team to improve the pre-build testing
C
Explanation:
Acceptance Test-Driven Development (ATDD) involves the whole team collaboratively discussing acceptance criteria, with examples, and then distilling them into a set of concrete acceptance tests before development begins. It’s a way to get clear on what to build, and it’s done in a way that allows the team to know when a story is complete. ATDD helps to make sure that all the stakeholders have a common understanding of what is being built and what the success criteria are.
Reference = The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of defining testable requirements within an Agile team and creating and implementing various Agile test approaches using appropriate techniques1. It also supports the contribution to test automation activities in an Agile project2, which aligns with the principles of ATDD.
You have been working to define acceptance tests for a story. You think this will help tailor your testing. You have asked the product owner to be involved as well.
You are currently looking at this story:
As a pet owner
I want to purchase food online
So that it can be delivered to my house when I need it
Which of the following is the preferred way to solicit information from the product owner to better understand what will be "acceptable?
- A . Propose the following acceptance criteria
Purchase below the limit for free delivery
Purchase above the limit for free delivery
Request store pickup - B . Explain boundary value analysis to the product owner and have them indicate the appropriate boundaries to test
- C . Work with the product owner to elicit examples of how they would use the software Combine their examples with testing techniques to flesh out the set of acceptance criteria
- D . Create the following acceptance criteria and review them with the product owner
Login
Verify password reset
Verify account details
Update account details
Browse and select food
Add to cart
Remove from cart
Add more items to cart
Select delivery
Remove items from can until delivery is no longer free
Checkout and verify the deliver charge is added
Browse again and select food
Select delivery and verify it is free
Checkout and verify no delivery charge is added
C
Explanation:
Working with the product owner to elicit examples of usage is a key aspect of Agile methodologies. This collaborative approach ensures that the acceptance tests are relevant and based on real-world scenarios that reflect the product owner’s vision. By combining these examples with testing techniques, testers can create a comprehensive set of acceptance criteria that are directly tied to the user’s needs and the functionality of the software. This method aligns with the principles of Agile testing, where communication and collaboration are essential for understanding requirements and creating effective acceptance tests.
Reference: = The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of collaboration between testers and product owners to define testable requirements within an Agile team. It also highlights the need to create and implement various Agile test approaches using appropriate techniques, which include eliciting examples from the product owner12.
You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests tor stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is
As a customer I want to be told how many items I need to purchase, so I can receive free shipping
Which of the following is an appropriate test charter for this story?
- A . Login as a customer buy various goods request free delivery add more items to your cart checkout, verify that your delivery is free
- B . Buy 12 of one item and see if you are advised that you get free shipping
- C . Login as a customer buy an item verify message tells you how many are needed for free delivery add items to your cart until you qualify checkout verify delivery is free
- D . As a supplier verify that when a customer purchases the correct number of goods the system doesn’t add any delivery fees at checkout
C
Explanation:
The appropriate test charter for the user story provided should focus on the customer’s experience and the functionality described in the story. Option C is the most suitable because it covers the entire process from the customer’s perspective: logging in, purchasing an item, receiving information about the requirement for free shipping, adding more items, and then verifying that the delivery is free upon checkout. This test charter effectively tests the acceptance criteria of the user story by ensuring that the system provides the necessary information and applies the free shipping offer correctly when the conditions are met.
Reference: = The ISTQB Advanced Level Agile Technical Tester syllabus outlines the importance of creating test charters that align with user stories and epics using requirements engineering techniques. It emphasizes the need for test charters to be comprehensive and to evaluate the acceptance criteria effectively123.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
You are testing a large e-commerce system for household goods that is being implemented using
Agile methodologies You are currently working on deriving tests for stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is:
As a customer I want to be told when my items will be delivered, so I can plan to be home.
You have been given the following charter that was proposed by another tester for testing this story
Login as a customer, buy enough of each item to qualify for free shipping for each item checkout and verify that no shipping fee has been added.
What is the main flaw in this charter?
- A . It focuses on the delivery company instead of the activities of the user
- B . It does not cover the mam functionality of the user story
- C . The expected results are not defined
- D . The actions of the user are not clearly stated in the charter
B
Explanation:
The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story’s main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story’s objectives12.
There are statements within the loop that should be outside the loop
- A . 1,3,4,5
- B . 7,3,4,6
- C . 2,3,5,6
- D . 1,2,4,6
D
Explanation:
The pseudocode provided for review indicates a password entry system with a lockout mechanism after a certain number of failed attempts.
The issues identified during the code review are:
Variables have not been properly defined with meaningful names – the variables used in the pseudocode are not descriptive, which can make the code difficult to understand and maintain.
There are unused variables defined – the pseudocode includes variables that are declared but not used, which is inefficient and can lead to confusion.
Loop counters are not properly initialized – if a loop counter is used, it must be initialized correctly to ensure the loop functions as intended.
There are statements within the loop that should be outside the loop – certain messages or actions may be repeated unnecessarily within a loop when they should be placed outside to execute only once.
Reference: = ISTQB Advanced Level Agile Technical Tester documents and study resources emphasize the importance of clear, maintainable code, which includes using meaningful variable names, removing unused variables, proper initialization of loop counters, and correct placement of code statements to avoid redundancy and inefficiency in code execution. These principles are essential for agile technical testing to ensure that the code remains robust and adaptable to changes.
Which of the following best describes when the test automation suite should be updated in order to keep up with the development of new/changed software?
- A . At the end of each iteration after the completion of manual testing
- B . At the end of each release during regression testing
- C . At the start of each iteration during planning
- D . During each iteration as the code is received
D
Explanation:
Updating the test automation suite during each iteration as the code is received ensures that the suite evolves with the software. It allows for immediate feedback on the impact of changes, supports continuous integration, and helps in identifying defects early in the development process. This practice is in line with Agile principles, which advocate for continuous testing and integration to improve quality and reduce the time to market1.
Reference = The ISTQB Advanced Level Agile Technical Tester documents outline the importance of maintaining and updating test automation suites in an Agile environment to support continuous integration and delivery, and to ensure that the tests provide adequate coverage throughout the development cycle2.
Which of the following is an example of how continuous testing facilitates continuous delivery?
- A . Automated testing conducted in the delivery environment helps validate that the delivery has been successful
- B . Continuous testing is the process that delivers the code to the test environment
- C . Automated testing removes the need to report defects so the code can move more quickly toward production
- D . Continuous testing supports continuous delivery to production by constantly regression testing the software in the production environment so problems are identified quickly
A
Explanation:
Continuous testing facilitates continuous delivery by ensuring that every change made to the codebase is tested automatically and immediately, which helps in identifying defects as early as possible. Automated testing in the delivery environment is crucial as it validates the success of the delivery process by ensuring that the software operates as expected in the production-like environment before the actual release.
Reference = The ISTQB Advanced Level Agile Technical Tester certification highlights the importance of technical testing skills in Agile development, including test automation approaches and continuous deployment and delivery1234.
As a tester on an Agile team you have been given the following user story to analyze
As a medical professional
I want to see the availability of operating rooms
So I can schedule surgeries as needed
You have talked with the product owner and she expressed some concern over the term "medical professional" You have looked into this and found that doctors want to schedule their surgeries but the hospital administrator does not want them to have this ability
At this point what should you do to try to resolve this issue?
- A . Wait for the team to sort out the requirements and test something else in the meantime
- B . Continue with testing from the perspective of a doctor and trust the procedures to be worked out later regarding who can do what
- C . Work with the BA and the product owner to try to negotiate the differing approaches and come to an agreement
- D . Expand the testing to cover all personas to ensure that everyone can use the application and let the process sort out later when access is allowed to the application
C
Explanation:
When a conflict arises regarding user story requirements, it is essential to engage in active collaboration to resolve the issue. The tester should work with the Business Analyst (BA) and the product owner to clarify and negotiate the requirements. This approach ensures that the user story reflects the needs of all stakeholders and that the acceptance criteria are agreed upon before testing proceeds. It aligns with Agile principles, which emphasize teamwork, customer collaboration, and the ability to respond to change.
Reference: = The ISTQB Advanced Level Agile Technical Tester documents highlight the importance of collaboration and communication within Agile teams to resolve differences and refine requirements. It also underscores the role of the tester in facilitating discussions to ensure that the user stories are well-understood and testable12.
Whose perspective should be used when a user story is created?
- A . User acceptance tester
- B . End user
- C . Stakeholder paying for the project
- D . Automated user software
B
Explanation:
When creating a user story, it is essential to consider the perspective of the end user. This is because user stories are meant to capture the requirements and experiences of the actual users who will interact with the system or product. The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of analyzing user stories and epics using requirements engineering techniques, which include creating and evaluating testable acceptance criteria from the end user’s perspective. This approach ensures that the developed features will meet the real needs and expectations of the users, leading to a more user-centered and valuable product.
Reference = ISTQB Advanced Level Agile Technical Tester documents and Training resources12.
“As the leader of the marketing department, I want to have a content management system so that
my employees can edit and provide quality content to the readers”
Which of the following requirements engineering techniques would be the MOST effective for
identifying and prioritizing user stories for the given Epic?
- A . Storyboarding
- B . Story mapping
- C . Defining Personas
- D . Class Diagrams
- E . Use Cases
B
Explanation:
Story mapping is the most effective requirements engineering technique for identifying and prioritizing user stories related to the epic mentioned. It allows the team to visualize the entire customer journey, which is crucial for a content management system that aims to enhance the content editing and publishing process. By mapping out the user stories, the team can see how they fit into the overall system, prioritize them based on the value they provide to the end-users, and ensure that all necessary functionalities are covered.
Reference: = The ISTQB Advanced Level Agile Technical Tester materials discuss the use of various requirements engineering techniques in an Agile context. Story mapping, in particular, is highlighted as a valuable method for organizing and prioritizing user stories to create a shared understanding among the team members123.
You have to review the following user story that will be developed and tested during the next Sprint:
As a potential conference attendee, I want to be able to register for the conference online, so that registration is simple and paperless.
The following acceptance criteria are also mentioned:
i) Payment can be made via PayPal, Debit or Credit Cards
ii) An acknowledgement email is sent to the attendee after submitting the form
iii) Protection against spam is working as expected
iv) Information from the form is stored in the registrations database
v) All incorrect user inputs are flagged by the system
Which of the following correctly shows which acceptance criteria are testable?
- A . ii, iv, v are testable
- B . i, iii, v are testable
- C . i, ii, iv are testable
- D . iii, iv, v are testable
C
Explanation:
The testable acceptance criteria for the user story are those that can be verified through testing to ensure they meet the user’s needs and the system’s functionality. In this case:
Criterion (i) is testable because you can verify the payment methods.
Criterion (ii) is testable as you can check if the acknowledgement email is sent after form submission.
Criterion (iv) is testable by confirming that the information is stored in the database correctly.
Criteria (iii) and (v), while important, are not explicitly testable from the user story’s perspective without further clarification on how spam protection is measured and what constitutes ‘incorrect’ user inputs.
Reference = The ISTQB Advanced Level Agile Technical Tester materials emphasize the importance of creating testable acceptance criteria that are clear, measurable, and verifiable within the context of the user story12. This ensures that the developed feature meets the user’s requirements and functions as intended2.
Which of the following correctly describes positive characteristic of unit tests?
- A . Unit tests should be independent from system components other than the one to be tested
- B . Unit test can be derived from the given epics and existing code of the test object
- C . While refactoring, the redesign of the unit test to adapt to the changed code is crucial
- D . A unit test should be written against large and complex code structures to get fast and
feedback of the code quality
A
Explanation:
One of the fundamental characteristics of unit tests is that they should be independent of other system components. This means that a unit test should only cover the functionality of a single component or unit of code, without relying on or interacting with external systems or modules. This independence ensures that the tests are focused, reliable, and can be run quickly, providing immediate feedback on the code quality of the unit being tested.
Reference: = The ISTQB Advanced Level Agile Technical Tester documents outline the importance of unit test independence as a key aspect of technical testing in an Agile context. This characteristic is crucial for maintaining the effectiveness and efficiency of the testing process within Agile development cycles1.
A developer has implemented a class that calculates if a given date is a leap year.
The definition for the leap year is given:
Every year that is exactly divisible by four is a leap year, except for years that are exactly divisible by 100, but these centurial years are leap years if they are exactly divisible by 400.
– divisible by 4
– but not by 100
– years divisible by 400 are leap anyway
You have already thought about it and started with the first test class; the test class looks like (pseudo JavaScript used here):
// LeapYear.spec.js
describe(‘Leap year calculator’, () => {
it(‘should consider 1996 as leap’, () => {
expect(LeapYear.isLeap(1996)).toBe(true);
});
});
What would now be your next step to proceed as efficient as possible, to validate the correctness of the class above?
- A . First write additional test classes to test also other relevant aspects of the leap year calculation
- B . First write code that covers other relevant aspects of the leap year calculation
- C . First write code that makes this test case fail
- D . First write code that makes this test case pass
D
Explanation:
In the context of test-driven development (TDD), the next step after writing a failing test is to write the minimum amount of code necessary to make the test pass. This approach encourages simple designs and inspires confidence that the system is functioning as expected. Once the test passes, you can then refactor the code to improve its structure without changing its behavior.
Reference: = The ISTQB Advanced Level Agile Technical Tester syllabus outlines the TDD process as a cycle of writing a failing test, making it pass, and then refactoring the code. This is a fundamental practice in Agile technical testing to ensure that the codebase remains clean and maintainable12.
Which of the following statements about performing exploratory testing with test charters is correct?
- A . In contrast to black-box testing, the expected result is documented after a defect is found and not as part of test design
- B . Test charters are a useful tool to be used for testing when a detailed specification for the system under test is available
- C . The result of performing exploratory testing by using test charters is finding defects and specification defects
- D . Exploratory testing and black-box testing use the same metrics for measuring test coverage
C
Explanation:
The correct statement about performing exploratory testing with test charters is that the result of such testing is finding defects and specification defects. Exploratory testing with test charters is a structured but flexible approach that focuses on learning about the system and designing tests as one explores the system12. It allows testers to uncover not just defects in the code, but also gaps or ambiguities in the specifications or requirements. This approach is particularly useful when there are no detailed specifications available, as it relies on the tester’s skill and intuition to explore the system’s behavior12. Test charters guide the exploratory testing session but do not prescribe specific expected results upfront, as is done in black-box testing. Instead, they provide a mission or objective for the testing session, allowing for a more investigative approach to testing12.
Reference: =
ISTQB Advanced Level Agile Technical Tester Syllabus1
ISTQB Advanced Level Agile Technical Tester Learning Objectives2
Please ensure to refer to the latest ISTQB documents and resources for the most accurate and up-to-date information.
Refactoring of test cases is needed in agile projects for many reasons.
Which of the following statements about the refactoring of test cases is correct?
- A . Refactoring of test cases is done to match and evolve the test cases due to changing functionality. The main benefits include improving the regression test cases and the continued alignment of the tests with the code base and product functionality
- B . Refactoring of test cases is needed because we cannot write and maintain detailed test cases in the short iterations associated with agile. The main benefits include aligning the pace of testing with development and the ability to quickly create new test cases
- C . In general, in the agile world refactoring is a way to clean up test cases by making them shorter. The main benefits include the ability to write test cases quickly, being able to test faster using short test cases, and being able to automate them quickly
- D . Refactoring of test cases is done as a process with the following steps: Identification, Refactor, Re-run, and Identify again. The main benefits include improving the regression test cases and maintaining the alignment of tests with the code base and product functionality
A
Explanation:
Refactoring of test cases in agile projects is primarily done to ensure that the test cases remain relevant and effective as the functionality of the product evolves. This process involves updating and improving the test cases to match the current state of the product’s functionality. The main benefits of this practice include enhancing the quality and effectiveness of regression test cases and ensuring that the tests continue to align with the code base and product functionality. This alignment is crucial for maintaining the integrity of the testing process and ensuring that the tests accurately reflect the product’s requirements and behavior.
Reference: = The ISTQB Advanced Level Agile Technical Tester syllabus and related materials emphasize the importance of refactoring test cases in agile projects. It is highlighted as a necessary activity to adapt to changes in functionality and to maintain the relevance and effectiveness of the test suite1.
An increased proportion of automated test coverage often leads to a greater degree of manual testing that follows reactive strategies, because:
- A . Many of the tests that can be prepared upfront, will be automated which enables the testers to spend more time for execution of manual tests
- B . An increase of the proportion of automated test increases test coverage, and the uncovered areas are to be tested reactively
- C . If the proportion of automated tests increases, manual tests focus on the riskiest areas which are identified reactively
- D . Reactive strategies consider the current context and status of the project and the system under test. To be able to adopt to this status most flexible a greater degree of manual testing is necessary
D
Explanation:
The increase in automated test coverage allows for more frequent and extensive testing of the software, which in turn provides more up-to-date information about the current state of the system. This enables testers to apply reactive strategies effectively, as they can focus manual testing efforts on areas that are most likely to be affected by recent changes or that are identified as high-risk. Reactive strategies are adaptive and context-dependent, making them well-suited for the dynamic and iterative nature of Agile projects.
Reference: = The ISTQB Advanced Level Agile Technical Tester syllabus and study materials emphasize the importance of integrating automated testing within the Agile process to support continuous integration and delivery. It also highlights the need for manual testing to complement automated tests by focusing on areas that require human judgment and exploratory testing skills12.
The challenges described below are of test automation in agile settings or agile projects.
Which is the correctly described one?
- A . Resource’s availability is a challenge in automating tests in agile settings, as they are needed to create, maintain, and execute the test suite
- B . Unit testing automation is the most critical test automation needed in agile and covers most of the testing challenges in agile quality of code and gives good test coverage
- C . Test deployment time is one of the challenges of agile testing, as deploying slow is not possible in short iterations
- D . Test Execution Time is not critical in agile as there are fewer tests written, and they are designed as checklists or high-level tests which reduces the time it takes to execute them
A
Explanation:
In Agile settings, the availability of resources is indeed a challenge for test automation. Agile projects require rapid development and frequent changes, which means that the test suite must be continuously updated and maintained. This requires dedicated resources that can quickly adapt to these changes and ensure that the test automation is effective and up-to-date. Without sufficient resources, the test automation efforts can become a bottleneck, hindering the Agile team’s ability to deliver quality software at speed.
Reference = The ISTQB Advanced Level Agile Technical Tester documents discuss the challenges of test automation in Agile settings, including the need for resources to support test automation activities12. It emphasizes the importance of having a well-maintained test suite that can keep up with the pace of Agile development3.
You are working in a project that developed a product that has reached a stable state and is deployed on different HW configurations all over Europe.
You management decided to use your project as Proof of Concept for adopting CI as a new way of working. The POC was implemented on one set of hardware and was successful.
Which of the following actions is a good next step?
- A . Enable different test configurations in the CI process to test different configurations that are deployed in the market
- B . Speed up test execution by decreasing the amount of User Interface (UI) testing to get faster feedback from the CI tests
- C . Reduce the number of tests in the CI test suite, to improve the benefit of the CI approach
- D . Implement code to dynamically select CI tests, executing only test cases affected by changes
A
Explanation:
The ISTQB Advanced Level Agile Technical Tester syllabus suggests that after a successful proof of concept (POC), it is important to expand the Continuous Integration (CI) process to handle various test configurations. This is especially relevant for a product deployed across different hardware configurations in Europe. By enabling different test configurations in the CI process, you can ensure that the product works correctly on all the hardware configurations it will encounter in the market. This step is crucial for maintaining the quality and reliability of the product in diverse environments.
Reference = ISTQB Advanced Level Agile Technical Tester documents and Training resources12.
Which option correctly states the sequence of tasks to be undertaken when re-factoring test cases? SELECT ONE OPTION
- A . Evaluate, Identification, Analysis. Re-run, Refactor
- B . Analysis, Identification, Re run, Refactor, Evaluate
- C . Identification, Evaluate, Analysis, Refactor, Re-run
- D . Identification, Analysis, Refactor, Re-run, Evaluate
D
Explanation:
The correct sequence when refactoring test cases in an Agile project is to first identify the test cases that need refactoring. Following identification, an analysis is conducted to understand the changes needed. After analysis, the actual refactoring of the test case is done. Once refactored, the test cases are re-run to ensure they work as expected. Finally, an evaluation is performed to confirm that the refactoring has improved the test cases and that they meet the required standards.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of refactoring test cases in Agile projects and provides a practical task-list for refactoring test cases123.
An enhancement to a Social Media application allows for the creation of new Groups. Any number of existing application members can be added to a Group. An attempt to add a non-existent member of the application to a Group will result in an error, as will an attempt to add the same member twice.
Members can be removed from an existing Group. An existing Group can be deleted but only if there are no current members attached to it.
Which one of the following Keyword-driven input tables provides the BEST test coverage of this enhancement?
Remove_Member Group3 @)Member2
Delete.Group Group3
Result
Group created
Member added to Group
Member added to Group
Error – Group not empty
Member removed from group
Member removed from group
Group deleted
Delete.Group Groups Group deleted
SELECT ONE OPTION
- A . Table 4
- B . Table 3
- C . Table 1
- D . Table 2
D
Explanation:
Table 2 provides the best test coverage because it includes tests for adding a non-existent member (Member4), which should result in an error, and it also tests for removing a member and then deleting the group, which is the correct sequence of actions according to the requirements. The other tables either do not test all the required scenarios or have actions in the wrong order (e.g., attempting to delete the group before removing all members).
Reference: = ISTQB Advanced Level Agile Technical Tester documents and Training resources.
Why could test cases need to be refactored in an Agile project?
SELECT ONE OPTION
- A . To maintain bi-directional traceability with the user stories
- B . To increase the breadth of black box coverage
- C . To make them easier to understand and cheaper to modify
- D . To ensure that the tests and code remained aligned
C
Explanation:
In Agile projects, test cases may need to be refactored to improve their clarity and maintainability. This process makes the test cases easier to understand and cheaper to modify, which is essential in Agile environments where changes are frequent and rapid. Refactoring test cases ensures that they remain effective and efficient as the codebase evolves, allowing for quick adjustments in response to new requirements or changes in the system under test.
Reference = The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of refactoring test cases in Agile projects to maintain their effectiveness and efficiency1.
Your Agile team is developing a web-based system that will allow users to browse and buy online from a store’s shopping catalogue. Continuous Integration has been implemented and technically it is working well, running several times per day, but each run is taking almost as much time as the team is prepared to allow. It is clear that after a few more iterations, as the number of tests needed grows with the product, it will be taking too much time.
Which of the four options contains a pair of solutions that will BOTH help to solve this problem?
a. Only include unit and component integration tests in the automated Cl runs.
b. Schedule low priority tests to be the first ones executed in each run, in order to provide rapid build verification.
c. Reduce the extent to which the automated tests go through the user interface, using technical interfaces instead.
d. Reduce the number of Cl cycles run each day.
e. Select a subset of automated tests for the daytime Cl runs, and run as many of the other tests as possible in an overnight cycle.
SELECT ONE OPTION
- A . d and e
- B . b and d
- C . c and e
- D . a and c
C
Explanation:
The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of optimizing Continuous Integration (CI) processes in Agile environments. Option C suggests reducing the extent to which automated tests interact with the user interface and instead using technical interfaces, which is often faster as it bypasses the GUI layer. Additionally, running a subset of tests during the day and the rest overnight can help manage the CI process without overloading the system during peak hours. These strategies align with the best practices for maintaining efficient CI cycles and ensuring that the CI process remains sustainable as the number of tests grows with the product.
Reference = The ISTQB Advanced Level Agile Technical Tester documents and training resources provide guidelines on test automation approaches and continuous deployment and delivery, which are relevant to optimizing CI processes12. Moreover, best practices for continuous testing in Agile suggest prioritizing tests that provide fast feedback and running extensive test suites outside of peak hours3.
Which statement is correct regarding the use of exploratory testing for safety critical systems? SELECT ONE OPTION
- A . It should be used when black-box tests cannot be automated
- B . It is highly recommended for all risk levels
- C . It is not recommended, as manual black-box tests should be used instead
- D . It is highly recommended for low risk levels only
C
Explanation:
Exploratory testing is a type of testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. While exploratory testing can be highly effective in certain contexts, for safety-critical systems, it is generally not recommended. Safety-critical systems require a high degree of assurance and predictability that each component of the system behaves as expected under all circumstances. Manual black-box tests, which are more structured and can be thoroughly planned and documented, are preferred in these scenarios to ensure comprehensive coverage and traceability.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and training materials provide guidance on the appropriate use of different testing techniques in various contexts, including the recommendation of structured manual black-box testing over exploratory testing for safety-critical systems1234.
Which statement is correct regarding the use of exploratory testing for safety critical systems? SELECT ONE OPTION
- A . It should be used when black-box tests cannot be automated
- B . It is highly recommended for all risk levels
- C . It is not recommended, as manual black-box tests should be used instead
- D . It is highly recommended for low risk levels only
C
Explanation:
Exploratory testing is a type of testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. While exploratory testing can be highly effective in certain contexts, for safety-critical systems, it is generally not recommended. Safety-critical systems require a high degree of assurance and predictability that each component of the system behaves as expected under all circumstances. Manual black-box tests, which are more structured and can be thoroughly planned and documented, are preferred in these scenarios to ensure comprehensive coverage and traceability.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and training materials provide guidance on the appropriate use of different testing techniques in various contexts, including the recommendation of structured manual black-box testing over exploratory testing for safety-critical systems1234.
Which statement is correct regarding the use of exploratory testing for safety critical systems? SELECT ONE OPTION
- A . It should be used when black-box tests cannot be automated
- B . It is highly recommended for all risk levels
- C . It is not recommended, as manual black-box tests should be used instead
- D . It is highly recommended for low risk levels only
C
Explanation:
Exploratory testing is a type of testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. While exploratory testing can be highly effective in certain contexts, for safety-critical systems, it is generally not recommended. Safety-critical systems require a high degree of assurance and predictability that each component of the system behaves as expected under all circumstances. Manual black-box tests, which are more structured and can be thoroughly planned and documented, are preferred in these scenarios to ensure comprehensive coverage and traceability.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and training materials provide guidance on the appropriate use of different testing techniques in various contexts, including the recommendation of structured manual black-box testing over exploratory testing for safety-critical systems1234.
Which statement is correct regarding the use of exploratory testing for safety critical systems? SELECT ONE OPTION
- A . It should be used when black-box tests cannot be automated
- B . It is highly recommended for all risk levels
- C . It is not recommended, as manual black-box tests should be used instead
- D . It is highly recommended for low risk levels only
C
Explanation:
Exploratory testing is a type of testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. While exploratory testing can be highly effective in certain contexts, for safety-critical systems, it is generally not recommended. Safety-critical systems require a high degree of assurance and predictability that each component of the system behaves as expected under all circumstances. Manual black-box tests, which are more structured and can be thoroughly planned and documented, are preferred in these scenarios to ensure comprehensive coverage and traceability.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and training materials provide guidance on the appropriate use of different testing techniques in various contexts, including the recommendation of structured manual black-box testing over exploratory testing for safety-critical systems1234.
Which statement is correct regarding the use of exploratory testing for safety critical systems? SELECT ONE OPTION
- A . It should be used when black-box tests cannot be automated
- B . It is highly recommended for all risk levels
- C . It is not recommended, as manual black-box tests should be used instead
- D . It is highly recommended for low risk levels only
C
Explanation:
Exploratory testing is a type of testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. While exploratory testing can be highly effective in certain contexts, for safety-critical systems, it is generally not recommended. Safety-critical systems require a high degree of assurance and predictability that each component of the system behaves as expected under all circumstances. Manual black-box tests, which are more structured and can be thoroughly planned and documented, are preferred in these scenarios to ensure comprehensive coverage and traceability.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and training materials provide guidance on the appropriate use of different testing techniques in various contexts, including the recommendation of structured manual black-box testing over exploratory testing for safety-critical systems1234.
End-to-end response time for any individual request submitted by a user must not exceed 7 seconds.
Applying the INVEST technique to this user story, including its acceptance criteria, which of the following statements is correct?
SELECT ONE OPTION
- A . The Testable and Negotiable criteria of INVEST have not been satisfied
- B . The Testable and Small criteria of INVEST have not been satisfied
- C . The INVEST criteria have all been satisfied by this epic
- D . The Negotiable and Small criteria of INVEST have not been satisfied
D
Explanation:
The user story provided is quite broad and encompasses multiple functionalities, which suggests it is more of an epic than a small, deliverable user story. The INVEST criteria for Agile user stories require that stories be Independent, Negotiable, Valuable, Estimable, Small, and Testable.
In this case:
Independent: This user story seems to have dependencies, as the ability to print the bill, view it in different currencies, and flag items are likely interconnected functionalities.
Negotiable: The user story provides specific solutions rather than outlining the problem to solve, which limits the negotiation on how to implement the solutions.
Valuable: The story does provide value to the hotel guest, which is clear.
Estimable: With the information provided, the development team can likely estimate the effort required.
Small: The story is not small; it covers multiple features that probably cannot be delivered in a single iteration.
Testable: The acceptance criteria are testable, although they are quite detailed and prescriptive.
Reference = The explanation is based on the INVEST criteria as described in Agile methodologies1234. The criteria are used to assess the quality of a user story, ensuring it is well-defined and suitable for Agile development practices. The user story in question does not fully meet the ‘Negotiable’ and ‘Small’ criteria, which is essential for maintaining flexibility and delivering incremental value in Agile projects.
You are ar teviemng the fdbwng Java furxton that deteimates whether a curb*. rput by the user. * Even or Odd Public da»s Oddorfven {
public state void mair^Strcg [ | args) (
Scarcer read – new ScanrerfSystem inje
System out prim (’Pease enter a rxmber’i;
int Number • reader nextfntO,
if(Number^2»»0)
System out prrrtln "your input number ‘Number ♦ * is even ).
else
System out prntirfyour input number ‘Number ♦ * is odd*);
)
}
You are Qj>ded by ’.he following checklist
• All variables must start with a Capital letter
• All output messages must start with a Capita letter
• There must De a comment bne e« pla ning the purpose of the dess How many checklist items Mve been fuelled7
SELECT ONE OPTION
- A . 3
- B . None
- C . 1
- D . 2
C
Explanation:
The Java function provided is intended to determine if a number input by the user is even or odd.
Upon reviewing the code against the checklist provided:
The variable Number does not start with a capital letter, violating the first checklist item.
The output messages do not start with a capital letter, violating the second checklist item.
There is no comment line explaining the purpose of the class, violating the third checklist item.
Therefore, none of the checklist items have been fulfilled.
Reference = The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of adhering to coding standards and best practices, which include proper naming conventions and documentation within the code to enhance readability and maintainability12. These principles are fundamental in organizations using an Agile development approach, as they support continuous integration and delivery, which are key aspects of Agile methodologies1.
Which statement about test automation is TRUE?
SELECT ONE OPTION
- A . Increasing test automation levels may decrease the frequency at which continuous deployments to production can be made
- B . Increasing test automation levels will eliminate the need for manual testing during continuous deployment
- C . Increasing test automation levels to increase the frequency of continuous deployment should always be an objective
- D . Minimizing the test suite by selecting, preparing and running only a subset of tests by using risk analysis should always be an objective
C
Explanation:
Increasing test automation is a key practice in Agile methodologies to support continuous integration and continuous deployment (CI/CD). Automated tests can be run quickly and frequently, which is essential for continuous deployment to be effective. By automating the testing process, teams can ensure that new code changes are tested thoroughly and consistently, leading to more frequent and reliable deployments to production.
Reference = The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of test automation in Agile contexts, particularly in relation to continuous deployment and delivery1. It is highlighted that test automation approaches are fundamental for organizations adopting Agile development practices12345.
You are part of an agile team creating a user story.
Which of the following requirements engineering techniques would you use to provide a visual representation of the system and help to see the ‘overall* story with the functional flow? SELECT ONE OPTION
- A . Personas
- B . Use Cases
- C . Story Mapping
- D . Storyboards
C
Explanation:
Story Mapping is a technique used in Agile development to create a visual representation of the system. It helps the team to understand the ‘overall’ story and the functional flow by arranging user stories along two independent dimensions. This method allows for a more holistic view of the project’s progress and priorities, ensuring that the development process aligns with the user’s needs and the product’s goals.
Reference: = The ISTQB Advanced Level Agile Technical Tester syllabus includes the analysis of user stories and epics using requirements engineering techniques and describes how these techniques can aid testers. Story Mapping is specifically mentioned as a method for managing requirements in an Agile context1.
The following user story has been developed:
As a customer of Alpha Airways who has booked a flight
I want to access the flight reservation
So that I can update the booking details
Which BDD scenario written in Gherkin format correctly applies to this user story? SELECT ONE OPTION
- A . Given that the logged-on user is a customer of Alpha Airways
When that user enters their surname correctly
Then they are able to see all flights currently booked so that they can select which flight they want to update - B . Given that a customer has booked a flight with Alpha Airways
When that customer enters their surname AND enters the flight number for this reservation
Then the booking details for that flight are displayed - C . Given that a customer has booked a flight with Alpha Airways
When that customer enters the correct surname and flight number for this reservation
Then the booking details for that flight are displayed
ELSE an appropriate error message is presented - D . Given that a customer has booked a flight with Alpha Airways
When that customer enters their surname and the flight number OR enters their customer ID and the flight number for this reservation Then they are taken to the booking details for that flight so that they can update the booking details
C
Explanation:
The correct BDD scenario for the given user story is option C, which aligns with the principles of Behavior-Driven Development (BDD) and the Gherkin syntax. This scenario clearly specifies the context (Given), the action (When), and the outcome (Then), along with handling alternate flows (ELSE). It ensures that the customer can access and update their booking details only if they provide both the correct surname and flight number, which is a common practice for verifying a customer’s reservation. This scenario also includes an error handling path, which is essential for a comprehensive test case.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and related materials emphasize the importance of creating testable acceptance criteria for user stories using requirements engineering and test techniques, which include the formulation of BDD scenarios in Gherkin format123.
A new Payroll system calculates the amount of tax that each employee must pay (TaxToPay) on their gross monthly salary (in (), and the net salary (NetSal) that they will receive after that amount of tax has been deducted It also calculates the amounts of tax (TaxPdYTD) and net salary (SalPdYTD) paid in the year to date (YTD) by adding them to the stored amounts from last month (for month 1 these will be zero), inputs Include Employee id (Empid) and Gross Salary this month (GrossSal). Tax Rate is looked up on the key of Employee Id, the amounts of tax and net salary paid in the year to date are looked up on the key of (Employee Id and [month • 1]) except that for month 1 they will be zero.
if both employees were paid the same in month 1 as in the current month 2. for which tax has now to be calculated, which data-driven input and expected output table is correct for this situation?
Table 1
SELECT ONE OPTION
- A . Table 3
- B . Table 1
- C . Table 4
- D . Table 2
C
Explanation:
Table 4 is the correct data-driven input and expected output table for this situation. It correctly calculates the TaxToPay based on the GrossSal and TaxRate, and then determines the NetSal by subtracting TaxToPay from GrossSal. Additionally, it accurately adds the TaxToPay to the previous month’s TaxPdYTD and the NetSal to the previous month’s SalPdYTD, which are both zero for month
A new Payroll system calculates the amount of tax that each employee must pay (TaxToPay) on their gross monthly salary (in (), and the net salary (NetSal) that they will receive after that amount of tax has been deducted It also calculates the amounts of tax (TaxPdYTD) and net salary (SalPdYTD) paid in the year to date (YTD) by adding them to the stored amounts from last month (for month 1 these will be zero), inputs Include Employee id (Empid) and Gross Salary this month (GrossSal). Tax Rate is looked up on the key of Employee Id, the amounts of tax and net salary paid in the year to date are looked up on the key of (Employee Id and [month • 1]) except that for month 1 they will be zero.
if both employees were paid the same in month 1 as in the current month 2. for which tax has now to be calculated, which data-driven input and expected output table is correct for this situation?
Table 1
SELECT ONE OPTION
- A . Table 3
- B . Table 1
- C . Table 4
- D . Table 2
C
Explanation:
Table 4 is the correct data-driven input and expected output table for this situation. It correctly calculates the TaxToPay based on the GrossSal and TaxRate, and then determines the NetSal by subtracting TaxToPay from GrossSal. Additionally, it accurately adds the TaxToPay to the previous month’s TaxPdYTD and the NetSal to the previous month’s SalPdYTD, which are both zero for month
which statement about test approaches is TRUE? SELECT ONE OPTION
- A . Test automation is not suitable when taking a Process-compliant test approach
- B . A Regression-averse test approach requires an ever-growing set of automated regression tests
- C . in a Model-based test approach, tests can be created automatically
- D . When taking a Reactive test approach, Increased test automation will reduce the time available for exploratory testing
C
Explanation:
A Model-based test approach involves creating models that represent the desired behaviors of a system. These models can then be used to generate test cases automatically, which is a key advantage of this approach. It allows for efficient test case generation and can help ensure thorough coverage of the system’s functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester materials discuss various test approaches and emphasize the benefits of model-based testing, including the automatic generation of tests12.
which statement about test approaches is TRUE? SELECT ONE OPTION
- A . Test automation is not suitable when taking a Process-compliant test approach
- B . A Regression-averse test approach requires an ever-growing set of automated regression tests
- C . in a Model-based test approach, tests can be created automatically
- D . When taking a Reactive test approach, Increased test automation will reduce the time available for exploratory testing
C
Explanation:
A Model-based test approach involves creating models that represent the desired behaviors of a system. These models can then be used to generate test cases automatically, which is a key advantage of this approach. It allows for efficient test case generation and can help ensure thorough coverage of the system’s functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester materials discuss various test approaches and emphasize the benefits of model-based testing, including the automatic generation of tests12.
which statement about test approaches is TRUE? SELECT ONE OPTION
- A . Test automation is not suitable when taking a Process-compliant test approach
- B . A Regression-averse test approach requires an ever-growing set of automated regression tests
- C . in a Model-based test approach, tests can be created automatically
- D . When taking a Reactive test approach, Increased test automation will reduce the time available for exploratory testing
C
Explanation:
A Model-based test approach involves creating models that represent the desired behaviors of a system. These models can then be used to generate test cases automatically, which is a key advantage of this approach. It allows for efficient test case generation and can help ensure thorough coverage of the system’s functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester materials discuss various test approaches and emphasize the benefits of model-based testing, including the automatic generation of tests12.
which statement about test approaches is TRUE? SELECT ONE OPTION
- A . Test automation is not suitable when taking a Process-compliant test approach
- B . A Regression-averse test approach requires an ever-growing set of automated regression tests
- C . in a Model-based test approach, tests can be created automatically
- D . When taking a Reactive test approach, Increased test automation will reduce the time available for exploratory testing
C
Explanation:
A Model-based test approach involves creating models that represent the desired behaviors of a system. These models can then be used to generate test cases automatically, which is a key advantage of this approach. It allows for efficient test case generation and can help ensure thorough coverage of the system’s functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester materials discuss various test approaches and emphasize the benefits of model-based testing, including the automatic generation of tests12.
which statement about test approaches is TRUE? SELECT ONE OPTION
- A . Test automation is not suitable when taking a Process-compliant test approach
- B . A Regression-averse test approach requires an ever-growing set of automated regression tests
- C . in a Model-based test approach, tests can be created automatically
- D . When taking a Reactive test approach, Increased test automation will reduce the time available for exploratory testing
C
Explanation:
A Model-based test approach involves creating models that represent the desired behaviors of a system. These models can then be used to generate test cases automatically, which is a key advantage of this approach. It allows for efficient test case generation and can help ensure thorough coverage of the system’s functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester materials discuss various test approaches and emphasize the benefits of model-based testing, including the automatic generation of tests12.
which statement about test approaches is TRUE? SELECT ONE OPTION
- A . Test automation is not suitable when taking a Process-compliant test approach
- B . A Regression-averse test approach requires an ever-growing set of automated regression tests
- C . in a Model-based test approach, tests can be created automatically
- D . When taking a Reactive test approach, Increased test automation will reduce the time available for exploratory testing
C
Explanation:
A Model-based test approach involves creating models that represent the desired behaviors of a system. These models can then be used to generate test cases automatically, which is a key advantage of this approach. It allows for efficient test case generation and can help ensure thorough coverage of the system’s functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester materials discuss various test approaches and emphasize the benefits of model-based testing, including the automatic generation of tests12.
A stub will be needed to test the payment method
Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues’
SELECT ONE OPTION
- A . Diagrams and Story Mapping
- B . Story Mapping and use Cases
- C . Personas and Diagrams
- D . Storyboards and Personas
D
Explanation:
In Agile development, requirements engineering techniques are crucial for understanding and defining user needs and system requirements. The issues identified in the user story suggest the use of Personas and Storyboards. Personas are fictional characters created based on user research to represent different user types within a targeted demographic, attitude, and behavior set. They help in understanding various user needs and experiences, which is reflected in issue 1 and 2. Storyboards, on the other hand, are visual representations of a user’s interaction with the product, providing a narrative of how the product is used. They help in visualizing the process and identifying any missing elements, such as the lack of specified acceptance criteria for the booking process speed (issue 3) and the details on how confirmation is sent (issue 4). The need for a stub to test the payment method (issue 5) also aligns with the storyboard technique, which can help visualize the integration points and dependencies.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus and study resources provide insights into various requirements engineering techniques and their application in Agile environments12. These resources emphasize the importance of understanding user stories and acceptance criteria, which are key to uncovering the issues mentioned34567.
which statement about test automation is TRUE? SELECT ONE OPTION
- A . Test automation will increase the intervals at which continuous deployment to production can be achieved
- B . Test automation levels can be influenced by and can constrain the frequency of code deployments
- C . When continuous deployment is fully implemented there will be no need for manual testing
- D . When continuous deployment is fully implemented it will be necessary to automate only unit and integration tests
B
Explanation:
Test automation is a key component in Agile development, particularly in the context of continuous deployment and delivery. The level of test automation can indeed influence and potentially constrain the frequency of code deployments. This is because the extent and robustness of automated tests determine how quickly and reliably new code can be pushed to production. If the test automation is not comprehensive or reliable, it may require additional manual testing or cause delays in deployment. Conversely, a high level of test automation can support more frequent and confident deployments by ensuring that new changes do not break existing functionality.
Reference = The ISTQB Advanced Level Agile Technical Tester syllabus discusses the importance of test automation in Agile projects, including its impact on continuous deployment and delivery12.