CTAL-ATT Practice Questions
Certified Tester Advanced Level Agile Technical Tester
Last Update 4 days ago
Total Questions : 98
Dive into our fully updated and stable CTAL-ATT practice test platform, featuring all the latest Agile Technical Tester exam questions added this week. Our preparation tool is more than just a iSQI study aid; it's a strategic advantage.
Our free Agile Technical Tester practice questions crafted to reflect the domains and difficulty of the actual exam. The detailed rationales explain the 'why' behind each answer, reinforcing key concepts about CTAL-ATT. Use this test to pinpoint which areas you need to focus your study on.
Consider the following section of pseudocode
Display "You exceeded the number of tries to enter a password. Your account is now locked. Call customer.
For this section of code, which of the following issues should be identified during a code review?
1. Variables have not been properly defined with meaningful names
2. There are unused variables defined
3. Divisors are not tested for zero
4. Loop counters are not properly initialized
5. There are endless loops
6. There are statements within the loop that should be outside the loop
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?
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?
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?
An increased proportion of automated test coverage often leads to a greater degree of manual
testing that follows reactive strategies, because:
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?
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?
