MENU
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?
Suggested Answer: D
Get Premium CTAL-ATT Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
18 comments · newest first
YU
Yuriko
11 months ago
I’m surprised this isn’t more straightforward. Why complicate it?
LI
Linn
11 months ago
Wait, isn’t D just making it too easy?
TO
Torie
11 months ago
C sounds interesting! But why would you want to make it fail?
LO
Lorrie
11 months ago
Nah, I’d go with B. Need to implement the logic first.
BR
Brande
11 months ago
I think option A is the best choice. More tests = better coverage!
FE
Felton
12 months ago
I think we should focus on making the current test pass before moving on to other cases, just to ensure our base case is solid.
CO
Corrie
12 months ago
I feel like I saw a similar question where we had to make a test fail first to see if our logic was correct. That could be a good approach.
PA
Pansy
12 months ago
I'm not entirely sure, but I think we might need to implement the logic for the leap year calculation before adding more tests.
EL
Eloisa
1 year ago
I remember we discussed how important it is to cover all edge cases in our tests, so maybe I should write additional test cases first.
RO
Ronnie
1 year ago
I'm feeling pretty confident about this one. The requirements are clear, and the test case is a good starting point. I think I'll follow the test-driven development approach and write some more comprehensive test cases before diving into the implementation.
RO
Rory
1 year ago
This seems pretty straightforward to me. I'll just start by writing the code to make the existing test case pass, and then build out the implementation from there. No need to overcomplicate things.
SA
Sage
1 year ago
Okay, I think I've got a good strategy here. I'll start by writing a test case that checks for a year that's not a leap year, like 1997. That way I can make sure the implementation is handling all the edge cases correctly.
DA
Daniela
1 year ago
I'm a bit confused about the requirements here. The question mentions a class that calculates leap years, but I don't see any code for that class. Should I start by writing the implementation first, or focus on the test cases?
JU
Justa
1 year ago
Hmm, this looks like a good opportunity to practice test-driven development. I think I'll start by writing some more test cases to cover the different scenarios for leap years, like years divisible by 100 and 400.
GL
Glory
1 year ago
Option B looks promising, as it includes the "interfaces" and "interface" components in the URI, which seem relevant to the question.
PA
Paz
1 year ago
This seems like a pretty straightforward customer success question. I think the key is to focus on what the next logical step would be after the customer has finalized their solution planning and is about to deploy.
AH
Ahmed
1 year ago
Hmm, I'm a bit unsure about this one. There are a few different Prisma Cloud documentation options mentioned. I'll need to carefully review each one to determine which one is most relevant for the specific task of querying user permissions.
ER
Erinn
1 year ago
This looks like a straightforward question about multicast configuration. I'm pretty confident I can identify the correct statement based on my understanding of the networking concepts.