assertEquals | An epic testing interface for Python

"I need to return every 3rd element in a tree..." this description screams for the modulo % operator.

If you want to enter an if-condition on every 3rd iteration then you can check this with the following condition: counter % 3 == 0. You don't need to subtract anything at all.

How does % work?

Put simply: The modulo operator returns the result of a division.

Example:

Instead of @MethodSource you can try @CsvSource.
I did this when I needed 3 Integer parameters in one parameterized test.
Here is the signature of my test method:

The method / function you want to test has a hidden dependency: $_SERVER.

Spotting this can also lead to a solution making the code more modular and easier testable.

This works by exposing the previous hidden dependency with an optional parameter:

First, the code in ValidatePassword tries to read the input stream beyond its end, so the scanner initialization needs to be moved out of the loop and a condition in.hasNextLine() needs to be checked.

Also, it's better to use a single reading of the line passWord = in.nextLine(); instead of a pair in.next(); in.nextLine();.

These two fixes should resolve the issue with incorrect loop.

If I read your code correctly, in list implementation you check if it.isBefore(toExclusive) and only then you add it to the list. In sequence implementation you do the same check it.isBefore(toExclusive) and then you add next item to the sequence.

Similar with the first item. In list implementation you check if cron.next(fromInclusive.minusNanos(1)) meets the requirement. In sequence implementation you always add it.

You need to use reverse to build your URL rather than hard coding it. Since you hard coded it, it is getting a 404 since the URL the test tried to post to is incorrect.

I don't know the app_name in your URLs file, you will need to add that to the reverse. For example if it was excercise it would be exercise:generate-edl.

You can add alwaysRun = true in @AfterClass annotation. like @AfterClass(alwaysRun=true).

If your test classes are independent of each other then it is good to use separate session for each test class. In this case you have to write @AfterClass method in each of test class to close individual session.

For this test to make sense, your hi() call should be done calling another service that you stub/mock in your test class. You're not doing that, so this approach won't work.

You wrote "the real method that hi represents does a lot", so it's about time you extract that to another service.

See if this works